Step 1
Define what is critical
Use built-in and custom critical surfaces so enforcement is applied where impact is highest.
For CTOs and founders leading 5-30 engineer teams
The immutable ledger for your org's high-leverage decisions.
Ledger captures decisions at the moment of change and keeps them auditable forever. We enforce where it matters first, starting with PRs in GitHub.
Strict by designAppend-only and tamper-evidentHumans author, AI suggests
Decisions get lost. PRs merge anyway.
- Critical changes ship with no durable record of why they were made.
- Docs tools depend on memory and process discipline instead of enforcement.
- Teams cannot trace how past decisions shaped current product direction.
How it works
Step 2
Author decision entries
Humans record problem, options, rationale, tradeoffs, and constraints with immutable Decision IDs.
Step 3
Enforce at point of impact
Changes touching critical surfaces must reference an active Decision ID before merge.
Trust guarantees, not conventions
Append-only by design
Decisions are never edited or deleted. New facts supersede old ones; history stays intact.
Trust over convenience
Tamper-evident, hash-chained records and derived status prevent silent drift from truth.
AI suggests, humans author
AI may surface decision points and topics. It never writes the decision; your team remains author.
Decision infrastructure first. Integrations are surfaces.
GitHub is where we enforce first, not the product itself. Ledger is the system of record your org runs on.
- Today: code is the first surface. PRs touching critical paths require a Decision ID.
- North star: one goldmine of code, product, and business decisions with seamless capture.
- Direction: a single pane of glass that is queryable, linkable, and shows what decisions changed over time.
FAQ
Is GitHub the only integration in v1?
Yes for enforcement in v1. GitHub is our first capture/enforcement surface, not the product boundary.
Does AI write decisions for us?
No. AI may suggest decision-worthy moments or topics; humans author every decision entry.
How long does setup take?
Most teams can connect GitHub and start enforcing in under 30 minutes.
What is the long-term direction?
Ledger is built to become one goldmine for code, product, and business decisions with seamless capture across multiple surfaces.
Make high-leverage decisions auditable and enforce them where change happens.
Start free, connect GitHub, and make decision capture part of engineering flow.