Skip to content

Orbitra Ledger Atlas

This site is the first visualization layer for the Orbitra Ledger repository.

It is intentionally narrow:

  • explain the repo shape
  • show where truth lives
  • visualize the operating flow
  • visualize governance control surfaces
  • give operators role-based reading paths
  • map current implementation truth against longer-term architecture work

It is not a replacement for Ledger canon. The source of truth remains in the repository itself:

  • docs/ for approved canon
  • research/ for pre-canon working models
  • records/ for proposals and decisions
  • meta/ for machine-readable control metadata
  • evidence/ for closure proof

What This Site Should Make Easier

  • understand what each top-level surface in Ledger is for
  • navigate the operating-system canon without reading the whole repo first
  • understand which GitHub and metadata surfaces carry live governance truth
  • choose the right docs entrypoint for CTO, implementation, research, or closeout work
  • see how the current Phase 1 shell coexists with the broader company architecture research
  • navigate the company research pack without mistaking it for canon
  • explain Ledger quickly to new operators or agents

First-Cut Map

flowchart TD
    A["Ledger Repo"] --> B["Canon<br/>docs/"]
    A --> C["Research<br/>research/"]
    A --> D["Records<br/>records/"]
    A --> E["Metadata<br/>meta/"]
    A --> F["Evidence<br/>evidence/"]
    A --> G["Governance<br/>governance/"]
    A --> H["Specs<br/>specs/"]
    A --> I["Templates<br/>templates/"]

    B --> B1["Operating system"]
    B --> B2["Strategy"]
    B --> B3["Product"]
    B --> B4["Architecture"]
    B --> B5["Company"]

    C --> C1["Operating-system research"]
    C --> C2["Strategy research"]
    C --> C3["Product drafts"]
    C --> C4["Company research"]

    D --> D1["Decisions"]
    D --> D2["Proposals"]

    E --> E1["Routing"]
    E --> E2["Launch contracts"]
    E --> E3["Lifecycle rules"]

Current Working Position

  • Active implementation shell remains Clients / Projects / Organization
  • Phase 1 execution remains project-centered
  • Broader company architecture lives in the research strategy set
  • Kernel and governance surfaces should not be silently redefined by visualization work

Use the pages in this site as orientation maps, not as canonical replacement text.

Start with:

  1. Repo Atlas
  2. Truth Surfaces
  3. Canon Indexes
  4. Research Indexes
  5. Company Research Map
  6. Records And Control Surfaces
  7. Reading Paths
  8. Operating Flow
  9. Governance Control Map

Then go back to the repo surface that actually owns the truth you need.

For contributor-facing work in Ledger itself, go next to:

  1. Contributor And Local Development
  2. Validation, Standards, And Evidence
  3. Contribution Path

Stronger Sources

When precision matters, leave the atlas layer and use the stronger repo surfaces directly: