Skip to content

Contribution Path

How To Work In Ledger

This repo is easiest to contribute to when changes are routed to the correct surface first.

Use Reading Paths when you need a role-specific entrypoint. Use Governance Control Map when you need to understand how issue, PR, and closeout truth fit together. Use Contributor And Local Development when you need the practical contribution, validation, local-dev, and merge-path surfaces in one place.

Surface Selection

If the change is... Use...
approved doctrine docs/
not yet canon research/
durable design proposal records/proposals/
durable accepted decision records/decisions/
machine-readable rule meta/
proof of closure evidence/
reusable format or checklist templates/

Simple Contribution Flow

flowchart TD
    A["Open or confirm governing issue"] --> B["Choose the right repo surface"]
    B --> C["Apply the correct template or model"]
    C --> D["Verify locally"]
    D --> E["Request review / closeout"]

First-Cut Docs Site Rollout

This MkDocs layer should stay narrow in the beginning:

  1. visualize the repo
  2. visualize the operating flow
  3. visualize the architecture boundary
  4. improve discoverability for new operators

It should not yet try to mirror every document in the repository.

Practical Operator Path

For day-to-day Ledger contribution work, use this order:

  1. Contributor And Local Development
  2. Contribution Path
  3. Governance Control Map

That keeps the atlas practical without collapsing the repo into one long operator note.

Stronger Sources

When the contribution path needs repo-owned precision, use: