The system as approved, kept current.
The living, current, approved state of every system, component and interface. It is the baseline every Change Intention is proposed and audited against.
| Level | Item | State |
|---|---|---|
| System | Payments | Approved |
| Component | Ledger service | Approved |
| Interface | Vault API | Approved |
| Component | Notification worker | Approved |
| Boundary | Card data stays behind the vault | Approved |
| Component | Refund service | In review |
Four kinds of entity, one current picture.
Ledger artifacts describe what actually exists, not what should be true.
Every system in your architecture.
What each system is built from.
How components talk to each other.
The lines drawn between them.
From your repos to an approved baseline.
Connect GitHub. rkito reads your code, Terraform, Helm, Kubernetes manifests and OpenAPI specs.
The scan generates a Change Intention with every component, boundary and interface it found.
Architects update what needs updating and merge. That is your living Architecture Ledger.
From then on the Ledger changes only through an approved Change Intention.
Read before you change, audited at the PR.
See what systems, components and interfaces exist, and which Change Intentions are already active on them.
The audit evaluates each pull request against the Architecture Ledger and your Steering principles.