home / skills / plurigrid / asi / og

og skill

/skills/og

This skill manages plurigrid fork synchronization and enables time-travel style cherry-picks from the og remote with observability for DuckDB buffers.

npx playbooks add skill plurigrid/asi --skill og

Review the files below or copy the command above to add this skill to your agents.

Files (4)
skill.md
2.4 KB
---
name: og
description: '## Overview'
---

# og - Observational Bridge Time Travel Skill

## Overview

The `og` skill maintains plurigrid fork synchronization while cherry-picking from the original (og) remote. It implements time-travel exercises through an observational bridge pattern for DuckDB buffers tracking ersatz Emacs interactions.

## Core Concepts

### Observational Bridge Type
```
OG Remote ────[cherry-pick]────→ Plurigrid Fork
     ↑                                  │
     │                                  │
  [time-travel]              [DuckDB buffer]
     │                                  │
     └──── CRDT.el sexp state ←────────┘
```

### 3-MATCH Chromatic Identity for Git Operations
- **SEED-WORLD**: Git commit SHA
- **COLOR-WORLD**: Gay.jl color from commit timestamp
- **FINGERPRINT-WORLD**: DuckDB buffer hash

### Tracked Interactions
1. **crdt.el sexp state** - Intermediate collaborative editing state
2. **Gay.jl invocations** - Color generation calls with seed/index
3. **GayMCP rewriting** - Self-modifying protocol operations

## Usage

### Cherry-Pick with Time Travel
```bash
# Fetch from og remote with color tracking
og fetch --track-colors

# Cherry-pick specific commit with DuckDB buffer
og cherry-pick <sha> --buffer-to-duckdb

# Time travel to previous state
og time-travel --to-round <drand_round>
```

### DuckDB Buffer Operations
```sql
-- Query crdt.el interaction history
SELECT * FROM crdt_sexp_buffer
WHERE session_id = current_session()
ORDER BY timestamp DESC;

-- Gay.jl color tracking
SELECT seed, index, hex_color, girard_polarity
FROM gay_color_invocations
WHERE timestamp > now() - interval '1 hour';
```

### Self-Rewriting Protocol
The skill tracks when GayMCP rewrites itself by monitoring:
- Seed state changes
- Color palette mutations
- 3-MATCH triangle verification failures

## Configuration

```json
{
  "og": {
    "remote": "og",
    "branch": "asi-skillz",
    "duckdb_path": "~/.og/time_travel.duckdb",
    "track_gay_jl": true,
    "track_crdt_el": true,
    "drand_beacon": "quicknet"
  }
}
```

## Integration with music-topos

The skill connects to the Blume-Capel ergodic random walk:
- +1 cherry-pick: Accept commit (ferromagnetic)
- -1 cherry-pick: Reject commit (antiferromagnetic)
- 0 cherry-pick: BEAVER - defer decision (vacancy)

Möbius inversion tracks the cumulative cherry-pick decisions.

Overview

This skill maintains plurigrid fork synchronization while cherry-picking changes from the original (og) remote and provides an observational-bridge time-travel workflow. It couples Git operations with DuckDB-backed buffers to track intermediate crdt.el states and deterministic color seeds. The result is replayable, auditable cherry-picks and reversible state navigation for collaborative editing experiments.

How this skill works

The skill fetches from an og remote, records commit metadata and buffer fingerprints in DuckDB, and applies selected commits to a plurigrid fork with color-aware cherry-pick logic. It stores crdt.el sexp state snapshots and Gay.jl color invocation records so you can inspect, verify, and travel back to prior collaborative states. A small self-monitoring protocol flags palette mutations and verification failures to support reproducible rewrites.

When to use it

  • When you need deterministic, auditable cherry-picks across distributed forks.
  • When collaborative crdt.el editing requires replayable historical inspection.
  • When color-seeded operations (Gay.jl) must be tracked and reproduced.
  • When you want to record Git + buffer fingerprints for compliance or debugging.
  • When experimenting with self-rewriting protocols like GayMCP.

Best practices

  • Enable DuckDB buffering for any session where you intend to time-travel or audit edits.
  • Use descriptive seeds and consistent drand rounds to make color-derived operations reproducible.
  • Run verification after cherry-pick to detect 3-MATCH identity mismatches early.
  • Keep track_gay_jl and track_crdt_el enabled for collaborative work; disable only for performance-sensitive fast paths.
  • Archive the DuckDB file alongside release artifacts to preserve historical context.

Example use cases

  • Fetch from an upstream og remote, cherry-pick a specific commit, and replay the crdt.el session to analyze edit conflicts.
  • Track Gay.jl color invocations tied to commits to debug visualized diffs or deterministic UI tests.
  • Time-travel to an earlier crdt.el sexp state to reproduce a bug introduced by a sequence of cherry-picks.
  • Monitor GayMCP for self-rewrites and trigger alerts when palette mutations or triangle verification failures occur.
  • Integrate with a research pipeline that maps cherry-pick decisions to a statistical model (ferromagnetic/antiferromagnetic/vacancy).

FAQ

How does time-travel choose which state to restore?

Time-travel targets DuckDB-recorded snapshots keyed by drand round or commit fingerprint; you select the round or SHA to restore the corresponding crdt.el sexp state.

Will enabling tracking affect performance?

Tracking adds lightweight DuckDB writes and color logging; it is low overhead for typical workflows but can be disabled for high-throughput batching.