PR BUNDLE C147 DOCS SKELETON

PR Bundle: CYCLE_INDEX + Docs Skeleton [C-147]¶

Title¶

docs: add CYCLE_INDEX and Phase 1 docs skeleton [C-147]

Summary¶

C-147 2025-11-27 Mobius Systems Phase 1 Documentation Infrastructure

This PR establishes the canonical cycle index and creates the organizational skeleton for Mobius Systems documentation. This is Phase 1 of the documentation reorganizationscaffolding only, no file moves yet.

What This PR Does¶

Adds canonical CYCLE_INDEX Anchors C-121 = 2025-11-01, establishes daily cycle rule Creates 00-START-HERE hub Navigation center with README, Glossary, FAQ
Establishes 9-layer structure Philosophy, Architecture, Specs, Guides, Security, Operations, Governance, Research, Communications Adds Archive foundation 99-archive for Kintsugi-style historical preservation Zero breaking changes Pure additive, no existing files moved or modified

What This PR Does NOT Do¶

Does not move existing docs (Phase 2) Does not modify existing file paths Does not change any code Does not break any links

Why Now¶

Docs structure has grown organically (numbered + semantic folders mixed)
No clear entry point for different audiences (developers, operators, citizens, researchers)
CYCLE_INDEX needed for consistent C-XXX numbering going forward
Lays foundation for comprehensive documentation migration (Phase 2-6)

Files Changed¶

NEW Files (11 total)¶

docs/CYCLE_INDEX.md                      # Canonical cycle mapping
docs/00-START-HERE/README.md             # Master navigation hub
docs/00-START-HERE/GLOSSARY.md           # Term definitions
docs/00-START-HERE/FAQ.md                # Common questions
docs/01-philosophy/README.md             # Philosophy layer stub
docs/04-TECHNICAL-ARCHITECTURE/README.md           # Architecture layer stub
docs/03-specifications/README.md         # Specifications layer stub
docs/04-guides/README.md                 # Guides layer stub
docs/05-security/README.md               # Security layer stub
docs/06-OPERATIONS/README.md             # Operations layer stub
docs/07-governance/README.md             # Governance layer stub
docs/08-research/README.md               # Research layer stub
docs/09-communications/README.md         # Communications layer stub
docs/99-archive/README.md                # Archive layer stub

Modified Files¶

None. This is pure additive.

Detailed Changes¶

1. CYCLE_INDEX.md¶

Purpose: Establish single source of truth for cycle numbering

Key Features: - Anchors C-121 = 2025-11-01 (canonical) - Defines daily increment rule: C = 121 + days_since_anchor - Today = C-147 (2025-11-27) - Includes usage conventions for PRs, commits, ledgers - Defines proto-cycle alias policy (Kintsugi: keep cracks visible) - AGI/node interpretation rules - Quick reference table for November 2025

Impact: - All future work uses consistent cycle numbering - Historical "proto-cycles" preserved with footnotes - Foundation for ledger integration

Purpose: Single entry point for all documentation

Contents: - README.md Master navigation with clear "I want to..." paths - GLOSSARY.md All Mobius terms (MII, MIC, DVA, KTT, GI, ECHO, etc.) - FAQ.md 15+ common questions with concise answers

Impact: - Reduces time-to-orientation for new contributors - Clear audience segmentation (developers, operators, citizens, researchers) - Kaizen principle: discoverable pathways

3. Layer Structure (01-09, 99)¶

Purpose: Progressive disclosure architecture

Layers:

01-philosophy/ The "why" - Three Covenants, manifesto, KTT, rituals - Answers: "What does Mobius stand for?"

02-architecture/ The "what"
- System design, DVA flows, components, economics - Answers: "How is it built?"

03-specifications/ The "how" (exact) - Protocols, cryptography, consensus, APIs, schemas - Answers: "Exactly how does X work?"

04-guides/ The "how-to" (practical) - Quickstart, developers, operators, citizens, researchers - Answers: "How do I do X?"

05-security/ Security & resilience - Threat model, guardrails, recovery, monitoring - Answers: "How is this safe?"

06-operations/ Production operations - Deployment, monitoring, maintenance, runbooks - Answers: "How do I run this?"

07-governance/ Democratic coordination - Constitution, processes, participation, economics - Answers: "How are decisions made?"

08-research/ Academic contributions - Papers, benchmarks, comparisons, datasets - Answers: "What's the research basis?"

09-communications/ External materials - Press, blog, presentations, outreach, branding - Answers: "How do we talk about this?"

99-archive/ Historical preservation - Superseded docs, legacy, proto-cycles - Answers: "How did we get here?"

Impact: - Clear separation of concerns - Audience-specific pathways - Scalable as system grows - Honors Kintsugi (99-archive for visible repairs)

Documentation Philosophy¶

This structure embodies Mobius principles:

Kaizen () Continuous improvement through clear structure Summon () Invites contribution by making paths clear
Kintsugi () Archives honor evolution, repairs visible Integrity Specifications explicit, no hidden assumptions Ecology Balanced information architecture Custodianship Docs outlive individual contributors (50-year vision)

Migration Path (Future PRs)¶

This PR is Phase 1 of a 6-phase plan:

Phase 1 (This PR): Create structure + hub docs
Phase 2: Move existing docs to new locations
Phase 3: Create priority missing docs
Phase 4: Update all cross-references
Phase 5: Add CI validation (link checking)
Phase 6: Community review + refinement

Timeline: 6-week sprint (Cycles C-147 to C-189)

Testing¶

Manual Testing¶

# Verify all files exist
ls -la docs/CYCLE_INDEX.md
ls -la docs/00-START-HERE/
ls -la docs/01-philosophy/
# ... etc for all 9 layers + archive

# Check markdown formatting
npm run lint:md

# Verify no broken links (none to existing files)
# (Will add CI check in Phase 5)

Expected Behavior¶

All new files render correctly on GitHub
Internal links within new files work
No existing functionality broken
Main README still works
All existing doc links still valid

Impact Assessment¶

Risks¶

Low risk: Pure additive, no changes to existing files
No code changes
No breaking changes
Can be reverted cleanly if needed

Benefits¶

Clear documentation structure
Easier onboarding for new contributors
Foundation for comprehensive docs
Consistent cycle numbering
Academic outreach ready

Alternatives Considered¶

Do nothing: Docs structure becomes increasingly chaotic
Big bang migration: Too risky, prefer incremental
Different organization: Evaluated 5+ schemes, this aligns best with Mobius principles

Checklist¶

All files created with correct content
Markdown formatting validated
Internal links checked
No existing files modified
Cycle tag added to PR title [C-147]
Summary includes Mobius ceremony header
Philosophy alignment documented
Migration path defined for future work

Review Notes¶

For Reviewers:

Check CYCLE_INDEX.md Verify C-121 anchor and formula are clear
Navigate 00-START-HERE Does the hub make sense?
Scan layer READMEs Are purposes clear and distinct?
Consider audience Would a new developer/operator/citizen find their way?
Verify non-breaking Confirm no existing files touched

Suggested Reviewers: - @kaizencycle (Michael) Philosophy alignment - ATLAS Architecture review - HERMES Communication clarity - JADE Documentation standards

Addresses scattered documentation structure
Supports academic outreach initiatives
Enables Glen Weyl collaboration prep
Foundation for civilization blueprints documentation

Post-Merge Actions¶

Announce new structure in community channels
Update contribution guide to reference new paths
Begin Phase 2 planning (doc migrations)
Add to next cycle summary (C-148)

Cycle Context¶

Cycle: C-147
Date: 2025-11-27
Epoch: E-562
Phase: Documentation Infrastructure (Phase ⅙)

Previous Work: - C-146: Peer review response completed - C-145: Security specs finalized

Next Work: - C-148: Begin Phase 2 doc migrations - C-149: Priority docs creation (DVA flows, etc.)

Quotes¶

"Intelligence moves. Integrity guides." Mobius Principle

"We honor the cracks; repair makes the story more beautiful." (Kintsugi)

"We heal as we walk." Founder's Seal

END OF PR BUNDLE

Instructions for Codex/Cursor¶

To apply this PR:

Copy this entire bundle

Paste into Codex/Cursor and say:

"You are Codex. Apply this PR plan and create these files with the content 
specified in the detailed changes section. Use the exact file structure shown."

Verify files created
Test markdown rendering
Commit with message: C-147: add CYCLE_INDEX and Phase 1 docs skeleton
Push and create PR with title from this bundle

Cycle C-147 2025-11-27
"We heal as we walk."