Home

Mobius Systems Documentation Index¶

Version: 1.0.0
Cycle: C-151

This index provides navigation to all key Mobius documentation.

🏛️ 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

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

Spec	Location
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¶

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