Development

Consensus, authority, and what is still experimental

The frontier — everything here is explicitly tagged, and unfinished consensus is never shown as operational.

Consensus and authority roadmap

C7.2.2 Durable vote-guard + QC bundles — IMPLEMENTED
Caveat: the multi-node harness stalls (height-retry deadlock).
C7.2.3 Durable height/view consensus — SPECIFIED
Protocol-core types landed; liveness closure is design-only.
C7.3 authority Authority certificates — verification IMPLEMENTED, issuance SPECIFIED
Enforcement is test-gated; no issuance path exists yet.
WIP branches 99b9bbc (height-retry gate) and 85ddbfb (issuance / authority-gossip) — isolated, never presented as landed.
Consensus development map — a status record, not an animation of working consensus.

Consensus is one continuous C7.x story: deterministic sortition selects witness panels, panels ratify blocks, and (in design) height/view consensus and authority certificates carry it forward. The live multi-node harness does not yet pass — the height-retry deadlock stalls a run at height 9. Unit tests are green; end-to-end liveness is not.

C7.2.2-design.md, C7.2.3-design.md, C7.3-authority-spec.md

WIP branches WIP

Two isolated branches hold work that must never be presented as landed:

Cells CONCEPTUAL

src/cell/mod.rs holds the Prototype Cell data model — Cell, CellMember, CellRelationship, Experiment, ExperimentReplication, EvidenceRecord, Reflection, and KnowledgeArtifact. These are serializable data structures only: no logic, no consensus or economics wiring. Cells are a design object, not an operational subsystem.

src/cell/mod.rs

Specifications

~/work-mesh-scaling (engine repo)

Conceptual work CONCEPTUAL

These are Institute-layer concepts with no engine correspondence at the current checkpoint. They are not hidden, but they are not operational: