Full index
Mobius Systems Documentation Index¶
Version: 2.0.0
Cycle: C-288
This index provides navigation to all key Mobius documentation.
Public handbook and live proof¶
The site you are reading is the Mobius Handbook (MkDocs). It stays close to the Mobius Civic AI Terminal — the live civic dashboard and API surface.
| Link | Purpose |
|---|---|
| Mobius Civic AI Terminal | Live dashboard (hot truth) |
| Terminal repository | Source for API routes, snapshot, Vault |
| State of the Substrate (C-288) | Current snapshot (C-288) |
| State of the Substrate (C-284) | Historical snapshot (C-284, archived) |
| Handbook hub | Current Mobius handbook entry + map |
| Interactive library | How proof tags and proof chains work |
| Archived Kaizen-OS handbook (2025) | Historical “Kaizen-OS” narrative (superseded framing) |
On many protocol pages, Live cards fetch public JSON from the Terminal. If a card shows “unavailable,” the prose is still canonical; enable CORS on the Terminal for this handbook origin when ready.
Mesh — Mobius Neural Substrate (C-286)¶
Cross-repo integrity mesh: registry, mobius.yaml node declarations, aggregate ledger, hourly aggregation workflow.
| Resource | Purpose |
|---|---|
| mobius.yaml v1 (pulse + ingest) | Declaration contract, lanes, payload vocabulary |
| OAA sovereign memory (MNS) | KV → OAA → Civic Core write path |
| Mesh workflow v1 (HIVE) | Pulse file, jobs fabric, agent PR governance |
| MNS Protocol v1 | Doctrine, analogy, join steps |
| MNS MCP Bridge | mobius.yaml as MCP manifest + discovery |
mesh/mcp-discovery.json | Mesh-wide MCP server index |
.well-known/mcp.json | Stable MCP discovery for agents |
mesh/registry.json | Registered nodes (raw JSON) |
mesh/mobius-yaml-spec.md | mobius.yaml field reference |
mobius.yaml | Substrate self-declaration (sentinel) |
| Decentralization Phase 1–2 (Substrate) | IPFS resolver + mesh-node scope vs Protocol-Core |
| KV storage tier architecture | Five-tier fallback · Upstash → Redis → OAA → Postgres → GitHub |
🏛️ Governance & Authority¶
The canonical authority model for Mobius Systems.
| Document | Purpose |
|---|---|
| Governance Overview | Four invariants, on-chain analogy |
| Consensus Authority Flow | 90-day consensus sequence |
| Roleplay Sandbox Rule | Hard boundary enforcement |
| AVM Specification | Authority Verification Module |
| Companion Attestation Schema | JSON Schema for attestations |
📜 EPICON Specifications¶
Epistemic constraint layer for AI systems.
| Spec | Purpose | Status |
|---|---|---|
| EPICON-01 | Epistemic Justification (CSS + EJ + CCR) | Canonical |
| EPICON-02 | Intent Publication & Divergence Protocol | Canonical |
| EPICON-02 Invariants | Formal invariants (13 rules) | Canonical |
| EJ Schema | JSON Schema for Epistemic Justification | Canonical |
| EVE Daily Closing Seal (C-284) | End-of-day synthesis, daily seal artifacts, hash chain | Draft |
EPICON Specification Family: - EPICON-01: Coherence layer (epistemic justification) - EPICON-02: Visibility layer (intent publication + divergence) - EPICON-03: Collective epistemic consensus (planned) - EPICON-04: Temporal drift analysis (planned)
🔐 Security & Threat Models¶
| Document | Purpose |
|---|---|
| Epistemic Attack Threat Model | 6 attack classes + mitigations |
| Threat Model v0.1 | General security threats |
📚 Conceptual Essays¶
| Essay | Purpose |
|---|---|
| Mobius Is Blockchain for Intent | Conceptual foundation |
| Why Mobius Works | System overview |
| Mobius At a Glance | Quick summary |
🤖 PR Bot Governance¶
The Mobius PR Bot enforces EPICON-02 on all pull requests.
How It Works¶
- Intent Publication Required: Every PR must include an EPICON-02 block
- Scope Enforcement: Changed files must match declared scope
- Time-Bounded Authority: Maximum 90-day window (72h for emergency)
- Intent Evolution: Hash changes require explicit declaration
- Divergence Severity: Scored as low/medium/high for triage
- Transparency Debt: Emergency PRs auto-create follow-up issues
Scope Labels¶
| Scope | Allowed Paths |
|---|---|
docs | docs/, epicon/, README.md |
ci | .github/, ci/, scripts/ |
core | src/, packages/, apps/, services/ |
infra | infra/, deploy/, docker/, monitoring/ |
sentinels | sentinels/ |
labs | labs/ |
specs | specs/, schemas/, configs/ |
Emergency Mode¶
For urgent changes that can't wait for normal consensus:
mode: emergency
emergency_scope: core
issued_at: 2025-12-20T23:00:00Z
expires_at: 2025-12-21T23:00:00Z # ≤72 hours
Emergency mode creates a Transparency Debt issue requiring post-facto justification within 24 hours.
📁 Directory Structure¶
docs/
├── authority/ # AVM, attestation schemas
├── epicon/ # EPICON specifications
├── public/ # Public-facing essays
├── 03-GOVERNANCE-AND-POLICY/
│ └── governance/ # Governance documents
├── 06-OPERATIONS/
│ └── security/ # Threat models
└── INDEX.md # This file
Handbook (interactive library)¶
| Document | Purpose |
|---|---|
| Interactive library (Levels 1–3) | Live proof tiles, proof-chain UI, Next.js shell |
| Proof tags authoring | How to embed <mobius-proof> in MkDocs |
🔗 Related Specifications¶
| Spec | Location |
|---|---|
| Mobius SDK API (BYOK, C-285 draft) | docs/specs/MOBIUS_SDK_API.md |
| MFS (Mobius Fractal Shards) | docs/07-RESEARCH-AND-PUBLICATIONS/specs/MFS_SPEC_v1.md |
| MII (Mobius Integrity Index) | specs/mii_spec_v1.md |
| GI/MII Formal Spec | specs/civic-ledger/RFC-0003-gi-and-mii-formal-spec.md |
🧭 Quick Links¶
- Start Here: 00-START-HERE/README.md
- Handbook hub: 11-SUPPLEMENTARY/handbook/README.md
- FAQ: 00-START-HERE/FAQ.md
- Glossary: 00-START-HERE/GLOSSARY.md
- Charter: 03-GOVERNANCE-AND-POLICY/foundation/CHARTER.md
- Bylaws: 03-GOVERNANCE-AND-POLICY/foundation/BYLAWS.md
Core Principles¶
Authority in Mobius is proven, scoped, time-bounded, and witnessed — never narrated.
Mobius does not prevent divergence. It makes divergence undeniable.
Transparency does not stop bad behavior. It removes the advantage of surprise.
"We heal as we walk." — Mobius Systems