The git branch model
Two ref namespaces encode the collective knowledge protocol:
ma/<elector> — individual positions
Each elector (human or agent) maintains one branch as their working position. Commits here are free — no consensus required. Positions are expected to diverge.
rigpa/<evolution> — settled evolutions
When the sangha synthesizes individual positions into shared understanding, a new
rigpa/<evolution> branch is created. Named for what it represents. This is a stable
checkpoint; elector branches diverge again from here.
The semantic distinction is ontological, not procedural. ma/ is a voice moving
toward recognition. rigpa/ is recognition.
Phase types
| Phase type | What happens | Outputs |
|---|---|---|
| Investigation | Agent explores a question using connectors and calculators | New corpus nodes, catalog edges, open questions |
| Extraction | Structured data pulled from a primary source | Generated nodes linked to catalog entries |
| Synthesis | Existing nodes linked or merged across threads | New edge-bearing nodes, resolved tensions |
| Assessment | Competing hypotheses evaluated against evidence | Hypothesis nodes updated, questions narrowed |