Skip to content

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 typeWhat happensOutputs
InvestigationAgent explores a question using connectors and calculatorsNew corpus nodes, catalog edges, open questions
ExtractionStructured data pulled from a primary sourceGenerated nodes linked to catalog entries
SynthesisExisting nodes linked or merged across threadsNew edge-bearing nodes, resolved tensions
AssessmentCompeting hypotheses evaluated against evidenceHypothesis nodes updated, questions narrowed