Skip to content

Reading Paths

Purpose

Ledger is easier to use when readers start from the right surface for their role and current scenario.

These are orientation paths, not replacement canon.

Fast Entry Map

flowchart TD
    A["Start here"] --> B["New operator or agent"]
    A --> C["CTO / architecture work"]
    A --> D["Implementation slice"]
    A --> E["Research slice"]
    A --> F["Review and closeout"]

    B --> B1["GLOBAL_FIRST_READ"]
    B1 --> B2["AGENT_STARTUP_PROTOCOL"]
    B2 --> B3["Repo Atlas + Truth Surfaces"]

    C --> C1["Strategy canon"]
    C --> C2["Operating-system models"]
    C --> C3["Architecture research set"]

    D --> D1["GitHub issue"]
    D1 --> D2["task-routing.yaml"]
    D2 --> D3["Operating Flow"]

    E --> E1["GitHub issue"]
    E1 --> E2["Research surface"]
    E2 --> E3["Bridge to canon if needed"]

    F --> F1["Review and closeout playbook"]
    F1 --> F2["Acceptance model"]
    F2 --> F3["Evidence and closeout record"]

Core Paths

New Operator Or Agent

Read in this order:

  1. docs/agents/GLOBAL_FIRST_READ.md
  2. docs/agents/AGENT_STARTUP_PROTOCOL.md
  3. AGENT_ENTRYPOINT.md
  4. meta/agent-authority.yaml
  5. meta/task-routing.yaml
  6. this site's Repo Atlas, Truth Surfaces, Canon Indexes, and Operating Flow

Use this when:

  • you are entering Orbitra fresh
  • you need the default startup path
  • you need to understand what Ledger controls before touching a task

CTO / Architecture Lead

Read in this order:

  1. docs/strategy/ORBITRA_OVERVIEW.md
  2. docs/strategy/VISION_AND_SCOPE.md
  3. docs/product/PHASE_1_WORKING_MODEL.md
  4. docs/operating-system/models/DEVELOPMENT_OPERATING_MODEL_SCOPE.md
  5. docs/operating-system/models/TASK_ROUTING_AND_LIFECYCLE_MODEL.md
  6. records/decisions/ACTIVE_DECISION_LOG.md
  7. research/strategy/

Use this when:

  • a task touches shell, architecture, contract, or cross-repo boundary judgment
  • you need to preserve the current Phase 1 shell while reading longer-term architecture
  • you need to decide whether work belongs in canon, research, records, or metadata

Implementation Slice

Read in this order:

  1. governing GitHub issue
  2. meta/task-routing.yaml
  3. route-required canon from docs/operating-system/
  4. docs/operating-system/models/PULL_REQUEST_EXECUTION_GOVERNANCE_MODEL.md
  5. relevant repo-local technical surfaces

Use this when:

  • the task is bounded execution work
  • you need to know route, lifecycle, and closeout expectations
  • you need to avoid loading the whole repo unnecessarily

Research Slice

Read in this order:

  1. governing GitHub issue
  2. current canon that constrains the question
  3. this site's Research Indexes
  4. relevant research/ surface
  5. records/proposals/ or records/decisions/ when durable boundary or policy context matters

Use this when:

  • the task is research-only
  • the output should not silently become canon
  • you need to separate implementation truth from longer-term reference work

Review And Closeout

Read in this order:

  1. governing issue
  2. linked PR
  3. this site's Records And Control Surfaces
  4. docs/operating-system/playbooks/REVIEW_AND_CLOSEOUT_PLAYBOOK.md
  5. docs/operating-system/models/REVIEW_AND_ACCEPTANCE_MODEL.md
  6. docs/operating-system/templates/REVIEW_AND_ACCEPTANCE_CLOSEOUT_TEMPLATE.md

Use this when:

  • work is entering In Review
  • you need to decide whether Done is legitimate
  • you need the issue, PR, and closeout surfaces to agree

Working Rule

Do not start from the whole repo.

Start from:

  • role
  • task route
  • lifecycle state
  • one relevant reading path

That is what keeps Ledger usable as a control repo instead of a generic document dump.

Stronger Sources

The atlas path is only the orientation layer. For authoritative entry surfaces, use: