Skip to content

Handbook home

Mobius Substrate Handbook

Intelligence moves. Integrity guides.

Mobius is easier to understand from the problem outward than from the architecture inward.

If this is your first visit, begin with AI Simple in Life. It explains the core loop without requiring knowledge of GI, MIC, quorum mechanics, sentinels, or the deeper runtime.


Start in 5 minutes

1 · Understand the idea

AI Simple in Life →

See → Ask → Measure → Test → Compare → Act → Remember.

2 · Understand Mobius

What is Mobius? →

What the project is, what it is not, and why the architecture exists.

3 · Understand the record

EPICON Philosophy →

Intent, reasoning, scope, evidence, review, and replay.

4 · See the system

Five Surfaces →

Substrate → Terminal → Browser Shell → Civic Protocol Core → HIVE.


Choose your depth

I want to… Start here Then go deeper
Understand the philosophy AI Simple in Life Theoretical Foundations
Understand the architecture Five Surfaces Technical Architecture
Understand EPICON EPICON Philosophy EPICON protocol
Build with Mobius System Overview Implementation
Operate Mobius Mobius Pulse Operations
Study the research Canonical Definitions Research & Publications
Follow the project over time State of the Substrate Cycle Journal in the navigation
Find an old document Full Index Archives

The Mobius reading map

AI SIMPLE IN LIFE
How humans + AI solve problems
EPICON
How intent and reasoning are recorded
WITNESS PROTOCOL
How evidence and claims are checked
OAA
How experience becomes memory
HIVE
How counterfactuals are explored
CIVIC PROTOCOL CORE
How durable records are preserved

The handbook is a renderer of the canon, not a second source of truth. When a handbook page conflicts with current machine state or ratified canon, follow the explicit canonical pointer and preserve the disagreement for correction.


Verify what you read

The handbook can show live proof beside protocol text. For current runtime state, use State of the Substrate and the canonical Terminal endpoints linked there.

Keep the boundary simple:

CANON → LEDGER → UI

No UI-derived truth.


Reference shelf

Use these after you have the basic mental model:


Documentation philosophy

The handbook follows three principles:

  • Kaizen (改善) — small steps, clear pathways, continuous improvement.
  • Kintsugi (金繕い) — keep the cracks visible; superseded material moves to archives rather than disappearing.
  • Custodianship — documentation should outlive any single contributor, model, UI, or deployment.

The goal of the front door is clarity. The goal of the archive is completeness. They do not need to be the same page.


Reorganized C-380 · CI remediation C-381 · 2026-07-23
“We heal as we walk.”