Genesis Mesh RFCs

This section holds the Genesis Mesh protocol RFCs. They turn implemented protocol behavior into reviewable, implementable standards documents so a future operator, implementer, standards reviewer, or investor can understand the protocol without reverse-engineering the Python reference implementation.

The program goals, principles, template, and acceptance bar are described in Genesis Mesh RFC Program. The strategic context is in Phase 2 — Ecosystem.

Status of this batch

This is the first RFC batch. Every document is Draft. Each maps to behavior already shipped in the Python reference implementation, and each cites the modules that implement it. Draft status means the description is implementation-informed and reviewable, not that the wording is frozen.

RFC	Title	Status	Primary implementation
RFC-001	Sovereign Identity	Draft	genesis_mesh/models/sovereign.py
RFC-002	Recognition Treaties	Draft	genesis_mesh/trust/treaty.py
RFC-003	Trust Bundles	Draft	genesis_mesh/cli/trust_bundle.py
RFC-004	Revocation Feeds	Draft	genesis_mesh/trust/treaty.py
RFC-005	Capability Manifests	Draft	genesis_mesh/models/discovery.py
RFC-006	Connectome Model	Draft	genesis_mesh/trust/connectome.py
RFC-007	Operator Continuity	Draft	docs/operators/
RFC-008	Managed Operator Role	Draft	docs/development/governance-baseline.md

For the established standards and patterns each RFC generalizes — recorded as design lineage, not as adoption claims — see Prior Art and Design Lineage.

Normative language

The RFCs use MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY as defined in RFC 2119 and RFC 8174. A normative requirement describes behavior an interoperable implementation has to honor. Reference behavior describes how the Python implementation happens to do it and MAY differ between implementations.