Appearance
Ledger
The ledger records each governance decision for a company, in order.
How it works
- Each company has its own sequence of entries.
- Each entry stores the hash of the previous entry and its own hash, computed over canonical JSON.
- The table is append-only for the application role.
- Only these steps write to it: pack sealed, request decided, agent issued, agent suspended and agent revoked. Saving a draft, submitting a request and chat never write to it.
- An optional seal adds an Ed25519 signature from DutyGraph's server key. Without the key, the screen says "Unsealed: hash-linked".
Verify chain
Verify chain re-computes every hash. When every entry matches, it shows "Chain intact: N records match their hashes." An evidence export includes the ledger slice and the entry before it, so an auditor can re-check the chain without access to DutyGraph.
Integrity, not truth
A hash-linked record shows that the entries were not changed after they were written. It does not show that the business claims inside them are true.
- "Chain intact" means the recorded decisions are as they were written. It does not mean each decision was right.
- An issue entry records that IAM approved the issue. It does not show that the access was provisioned in a business system.
- A Task Card cited in a decision shows which work the request named. It does not prove the work needed each scope.
- A seal shows the entry was written with DutyGraph's server key. It does not vouch for the content.
Words we use
| We say | We do not say |
|---|---|
| recorded, hash-linked | signed, verified, certified |
| sealed by DutyGraph's server key | compliant |
| checked at the DutyGraph gateway | enforced in the business system |
INFO
Status. Built: the ledger, Verify chain and the optional seal. Planned: a standalone verifier script that ships with each export.
Source: gitbook/product/governance/ledger.md in the DutyGraph repository.