rootPulse — Emergent Version Control

What It Is

rootPulse is not a primal. It is the ACTION domain of the coordination triad — version control that emerges when 🌿🖥️ biomeOS orchestrates the provenance trio ( 🌱🔐 rhizoCrypt + 🪨📖 loamSpine + 🍯🌾 sweetGrass) plus 🪺🔒 NestGate, 🐻🐕 BearDog, and 🎵🐦 Songbird over TOML composition graphs.

Key insight: rootPulse does not reimagine Git by building a new monolith. It reimagines Git by showing that version control is a coordination pattern — one that emerges naturally when you have content-addressed storage, cryptographic signing, immutable history, and semantic attribution.

The Two-Tier Architecture

rootPulse separates two temporal domains that Git conflates:

rhizoCrypt — The Ever-Branching Present

The working tier. Lock-free, ephemeral, a DAG that branches freely:

• Stage changes without blocking
• Branch without coordination
• Multiple writers, no locks
• 10-100x staging performance vs Git

This is the future — everything that might become a commit.

loamSpine — The Immutable Past

The committed tier. Linear, append-only, cryptographically sealed:

• Once committed, never changed
• Signature chain from 🐻🐕 BearDog
• Content-addressed via 🪺🔒 NestGate
• The past — everything that has been proven

Dehydration Protocol

The transition from present to past:

rhizoCrypt DAG (branching, ephemeral, fast)
    -> dehydration (collapse DAG to linear)
    -> loamSpine commit (immutable, signed, attributed)

Git conflates staging, branching, and committing in a single data structure. rootPulse separates them: staging and branching live in the DAG (fast, lock-free), committing lives in the linear chain (slow, deliberate, permanent).

Primal Composition

rootPulse coordinates six primals. None of them know about rootPulse:

The primals are instruments. 🌿🖥️ biomeOS is the conductor. rootPulse is the music that emerges when the conductor reads the score (TOML composition graph).

The 6-Phase Commit

A rootPulse commit is a sequential composition of primal calls:

1. Health check — verify all required primals are available
2. Session — 🌱🔐 rhizoCrypt dehydrates the DAG into a commit candidate
3. Sign — 🐻🐕 BearDog signs the commit via Unix domain socket
4. Store — 🪺🔒 NestGate stores the content-addressed blobs
5. Commit — 🪨📖 loamSpine appends the signed, stored commit to the linear chain
6. Attribute — 🍯🌾 sweetGrass records semantic contribution data

Each phase is a JSON-RPC call. Each phase can fail independently. The composition graph defines the dependency order. 🌿🖥️ biomeOS handles retry and rollback.

Semantic Attribution

Git blame counts lines. 🍯🌾 sweetGrass tracks meaning.

Three attribution layers:

1. Structural — what files, what functions, what lines
2. Semantic — what capability, what design decision, what trade-off
3. Narrative — why this approach, what alternatives were considered

Beyond Version Control

The rootPulse pattern applies wherever provenance matters:

The pattern is the same: create content ( 🌱🔐 rhizoCrypt DAG), prove it ( 🐻🐕 BearDog signing), store it ( 🪺🔒 NestGate CAS), commit it ( 🪨📖 loamSpine chain), attribute it ( 🍯🌾 sweetGrass semantics).

Implementation Status

rootPulse is Git reimagined as a coordination pattern between sovereign, composable primitives. Primals do not know about rootPulse. They provide capabilities. 🌿🖥️ biomeOS composes those capabilities into version control. The music emerges from the instruments — not from a new instrument.