Skip to content

Company Research Map

Purpose

This page is the atlas entrypoint for Ledger's company-focused research set.

Use it to answer a narrow question:

  • when the answer is not yet canon, which company research note should you read next?

This page is: - research navigation - not canon - not implementation authority - not a promotion decision

Truth Boundary

Keep these surfaces distinct:

  • docs/ holds approved canon
  • research/ holds pre-canon working models and stable reference research
  • this MkDocs page is only an orientation layer over those repo surfaces

Working rule: - this page should help you find company research - it should not make research look like approved doctrine

If implementation truth matters, return first to:

If later promotion matters, that remains separate and deferred under:

Company Research Shape

flowchart TD
    A["Company Research"] --> B["Completed operating-model pack"]
    A --> C["Research-system notes"]
    A --> D["Working surfaces"]

    B --> B1["Org chart / reporting"]
    B --> B2["Client services"]
    B --> B3["Delivery"]
    B --> B4["Product studio / internal products"]
    B --> B5["People & capability"]
    B --> B6["Finance & operations"]
    B --> B7["Governance & systems"]
    B --> B8["AI responsibility & approval"]

    C --> C1["Maturity rubric"]
    C --> C2["Artifact taxonomy"]

    D --> D1["README"]
    D --> D2["Research backlog"]
    D --> D3["Open questions"]

Completed Company Operating-Model Pack

The completed bounded company pack under #499 is the main company research set.

Research note What it answers Truth level
SOFTWARE_AGENCY_ORG_CHART_AND_REPORTING_MODEL.md company structure, reporting lines, and matrix posture research
CLIENT_SERVICES_OPERATING_MODEL.md external client-services loop and commercial-to-delivery handoff research
DELIVERY_OPERATING_MODEL_FOR_AGENCY_EXECUTION.md internal delivery execution after handoff into Projects research
PRODUCT_STUDIO_AND_INTERNAL_PRODUCTS_OPERATING_MODEL.md internal products model and product-studio posture research
PEOPLE_AND_CAPABILITY_OPERATING_MODEL.md hiring, capability, allocation, and review posture research
FINANCE_AND_OPERATIONS_ARCHITECTURE_MODEL.md economics, support loops, and operational finance structure research
GOVERNANCE_AND_SYSTEMS_OPERATING_MODEL.md company-level governance and systems posture research
AI_AGENT_RESPONSIBILITY_AND_APPROVAL_MODEL.md AI responsibility classes, approval boundaries, and audit expectations research

Use this pack when:

  • the question is about how the company should operate
  • the answer is not yet approved canon
  • you need one coherent reference set rather than isolated notes

Do not use this pack as direct permission to replace the active shell or the execution-kernel boundary.

Research-System Notes For The Company Stream

These notes help interpret the company research set without changing its truth level.

Research-system note What it answers Truth level
COMPANY_ARCHITECTURE_AND_COMPANY_RESEARCH_RUBRIC.md how company research matures inside research/ research
COMPANY_RESEARCH_ARTIFACT_TAXONOMY.md what standard artifact types the company stream should use research

Use these when:

  • you need to judge maturity without treating research as canon
  • you need to understand what kind of research note you are reading
  • you are opening or reviewing a new bounded company-research slice under #349

Working Surfaces

These repo surfaces help you work the company stream without treating the atlas as authoritative.

Surface Use it for Truth level
research/company/README.md directory boundaries and current note set research
research/company/RESEARCH_BACKLOG.md active and queued company-research slices research
research/company/OPEN_QUESTIONS.md unresolved shaping questions research
Company Architecture atlas bridge between current shell truth and long-term reference architecture atlas
Research Indexes broader research entrypoint across the whole repo atlas

Reading Paths

Use the company research set deliberately.

If you need company operating detail

  1. Start with research/company/README.md.
  2. Read the matching note from the completed company pack.
  3. Use the rubric and taxonomy notes only if you need maturity or artifact framing.

If you need broader architecture framing

  1. Start with Company Architecture.
  2. Drop into the company pack only when the question becomes operating detail.
  3. Return to repo-owned truth when a decision depends on canon.

If you need implementation truth

  1. Start with docs/product/PHASE_1_WORKING_MODEL.md.
  2. Use company research only as reference, not implementation authority.

Working Conclusion

The company research set is now strong enough to navigate as one coherent reference surface.

Use this map to:

  • find the completed company operating-model pack
  • find the research-system notes that interpret that pack
  • keep research clearly separate from canon and implementation truth