Index
Technical Specifications¶
This section is the single source of truth for:
- Protocol definitions
- API contracts
- Cryptographic formats
- Consensus mechanisms
- Schemas and manifests
If a question starts with "Exactly how…", the answer should live here.
Contents¶
Recommended structure (to be populated in Phase 2):
protocols/¶
masl.md— Model-Agnostic Sovereignty Layerboarding-protocol.md— How LLMs mount Mobius statedeliberation-proof.md— Thought Broker consensus protocolsupersede-protocol.md— Knowledge evolution mechanismintegrity-propagation.md— How GI flows through the system
cryptography/¶
mii-signature-spec.md— Ed25519 MII signatures (existing)integrity-proofs.md— Cryptographic integrity attestationskey-management.md— How keys are generated and stored
consensus/¶
thought-broker-consensus.md— Multi-agent deliberation (existing)tri-sentinel-review.md— ECHO Layer peer reviewsentinel-voting.md— How sentinels reach decisions
apis/¶
rest-api-reference.md— Complete REST API documentationmobius-mount-endpoint.md—GET /api/mobius/mountspecificationintegrity-check-endpoint.md— Health and GI verificationattestation-api.md— How to submit attestationswebsocket-events.md— Real-time event streaming
schemas/¶
manifests.md—.mobius/file format specificationsbiodna.md— Bio-DNA identity schemavirtue-accords.md— YAML covenant schemacivic-ledger-blocks.md— Block structurelearn-blocks.md— ECHO Layer knowledge blocks
Specification Principles¶
All specifications in this section follow these rules:
- Precision — Exact formats, no ambiguity
- Versioning — Every spec includes version number
- Reference Implementations — Link to canonical code
- Test Cases — Include validation examples
- Backwards Compatibility — Note breaking changes explicitly
Key Specifications¶
MASL (Model-Agnostic Sovereignty Layer)
Enables any LLM to board Mobius by calling /api/mobius/mount, which returns: - .mobius/atlas.manifest.json — System state & integrity - .mobius/biodna.json — Identity DNA - .mobius/virtue_accords.yaml — Moral & civic laws - mii_signature — Cryptographic integrity proof
Deliberation Proof
Cryptographic attestation that multi-agent consensus was achieved under constitutional constraints. Includes: - Sentinel votes - GI scores - Constitutional compliance checks - Timestamp and cycle number
Supersede Protocol
Knowledge evolution system allowing verified improvements to replace outdated information while preserving history (Kintsugi principle).
Specification Status¶
| Spec | Status | Version | Last Updated |
|---|---|---|---|
| MII Signature Spec | ✅ Complete | v1.0 | C-145 |
| Thought Broker Consensus | ✅ Complete | v1.0 | C-146 |
| MASL Protocol | 🚧 In Progress | v0.9 | C-147 |
| Supersede Protocol | 📋 Planned | - | - |
| Tri-Sentinel Review | 📋 Planned | - | - |
Using These Specifications¶
For Implementers:
These specs are contractual — implementations must match exactly.
For Integrators:
Use these to build compatible services or connect external systems.
For Researchers:
These provide formal definitions for academic analysis.
Relationship to Other Sections¶
- See
02-architecture/for high-level design context - See
04-guides/developers/for implementation tutorials - See
08-research/for theoretical foundations
Cycle C-147 • 2025-11-27
"We heal as we walk."