Company Architecture

Current Position

Ledger now carries two truths that must stay distinct:

• current implementation truth
• longer-term company architecture reference truth

Active Implementation Truth

• shell remains Clients / Projects / Organization
• active Phase 1 work remains project-centered
• the shell is still the implementation-facing product truth

Long-Term Reference Truth

The company architecture research set frames Orbitra in five macro layers:

flowchart TD
    A["Foundation Platform"]
    B["Agent Runtime & Control Plane"]
    C["Shared Company Engines"]
    D["Company Value Streams"]
    E["Cross-Cutting Governance & Intelligence"]

    A --> B
    A --> C
    B --> C
    C --> D
    E --> B
    E --> C
    E --> D

Bridge Rule

The long-term architecture is a reference map, not an instruction to replace the current shell immediately.

That means:

• current shell stays operationally frozen for Phase 1
• long-term architecture continues as research and planning truth
• kernel objects stay protected across both layers

What This Site Should Help With

• explain the distinction between shell, kernel, value streams, and overlays
• reduce confusion between current implementation truth and future architecture
• support architecture discussions without destabilizing current delivery work

Related Company Research

When the question moves from broad architecture framing into company operating detail, use:

• Company Research Map
• research/company/README.md
• COMPANY_ARCHITECTURE_AND_COMPANY_RESEARCH_RUBRIC.md
• COMPANY_RESEARCH_ARTIFACT_TAXONOMY.md

Those surfaces are still research or atlas surfaces, not canon.