EPICON C380 HANDBOOK 001

EPICON-C380-HANDBOOK-001 — Handbook Progressive Disclosure¶

Cycle: C-380 (implementation) · C-381 (CI / Codex remediation)
Date: 2026-07-22
Surface: Handbook / documentation renderer
Status: Proposed

Authority Provenance¶

Authority declared using docs/templates/EPICON_FOUNDER_STANDING.md v0.1

Custodian: Michael Judan (kaizencycle)
Scope: Handbook documentation rendering and navigation only — no runtime authority, ledger, or protocol semantics.
Sunset: When this EPICON is marked active after sentinel review, or superseded by a ratified handbook editorial policy.

Intent publication¶

epicon_id: EPICON_C-380_HANDBOOK_progressive-disclosure_v1
ledger_id: kaizencycle
scope: docs
mode: normal
issued_at: 2026-07-22T16:50:00Z
expires_at: 2026-10-20T16:50:00Z
justification:
  VALUES INVOKED: integrity, transparency, accessibility
  REASONING: Handbook front door exposed constitutional depth before newcomers had a simple mental model. Progressive disclosure preserves canon while improving readability. Renderer remains non-canonical.
  ANCHORS:
    - docs/00-START-HERE/AI_SIMPLE_IN_LIFE.md
    - docs/epicon/EPICON-C380-HANDBOOK-001.md
    - mkdocs.yml
  BOUNDARIES: Docs and MkDocs navigation only; no GI, ledger, or protocol behavior change
  COUNTERFACTUAL: If simplification flattens critical distinctions or implies UI-derived truth, revert front-door commits
counterfactuals:
  - If mkdocs strict build fails, do not merge
  - If readers mistake handbook prose for canonical truth, strengthen CANON → LEDGER → UI banners

Intent¶

Make the Mobius Handbook easier for a first-time human reader to understand without deleting, rewriting, or hiding the deeper canonical and historical record.

Problem observed¶

The handbook had accumulated multiple overlapping entry points and a navigation structure that exposed constitutional, runtime, economic, research, and historical depth before a newcomer had a simple mental model of Mobius.

The MkDocs configuration also contained a stale C-360 current-cycle label while cycle.json reported C-380.

Scope¶

This change is intentionally narrow and additive:

Add AI Simple in Life as a plain-language first-principles chapter.
Rewrite the public handbook front door around progressive disclosure.
Reorganize MkDocs navigation into reader-oriented layers.
Update handbook display metadata from C-360 to C-380.
Add small responsive reading-path cards.
Preserve existing deep documents, archives, protocol pages, proof UI, and reader preferences.

Out of scope¶

No mass file moves.
No archive deletion.
No protocol semantics changed.
No GI, MII, MIC, MFS, Reserve Block, or quorum behavior changed.
No runtime authority moved into the Handbook.
No claim that simulation or handbook rendering is canonical truth.

Canon boundary¶

The Handbook remains a renderer and navigation surface.

CANON → LEDGER → UI

No UI-derived truth.

When handbook prose, runtime state, and ratified canon disagree, the disagreement must remain visible until reconciled. The Handbook does not silently promote itself into the source of truth.

Key doctrine introduced¶

Integrity is structural, not moral¶

In AI Simple in Life, integrity describes whether a decision record remains coherent, attributable, and load-bearing when tested against reality. It is not a virtue score for a person and it is not synonymous with a successful outcome.

Reality remains outside the model¶

AI → REALITY → RESULT → EVIDENCE → AI

HIVE boundary¶

Simulation may alter confidence, expose failure modes, or motivate tests. Simulation does not become observed fact merely because a model produced it.

Risk¶

Primary risk: simplification could accidentally flatten important distinctions or make a plain-language page appear more authoritative than protocol canon.

Mitigation: explicit renderer/canon boundary, links downward into canonical definitions and protocol documents, additive changes only, and no deletion of existing depth.

Rollback¶

Revert the C-380 handbook commits. Existing documentation files and protocol structure remain in place, so rollback does not require data migration.

Review questions¶

ATLAS¶

Does the new navigation accurately reflect the current architecture?
Are any canonical documents hidden behind an inappropriate category?
Does AI Simple in Life make technical claims that exceed current implementation?

JADE¶

Does the front door read naturally to someone who has never heard of Mobius?
Does simplification preserve the distinction between integrity, correctness, morality, and outcome?
Does the handbook retain continuity with Kaizen and Kintsugi documentation principles?

ZEUS¶

Can a reader mistake HIVE simulation for evidence of a real event?
Can a reader mistake a handbook verdict or example for professional engineering, medical, or safety certification?
Are stale-cycle or renderer-as-truth failure modes still possible?

EVE¶

Does the consequence lens remain a harm/failure-mode check rather than a mechanism for scoring citizens?
Is the boundary against surveillance or person-level virtue scoring preserved?

EPICON C380 HANDBOOK 001