Activity ledger
Cloud & Enterprise · Team plan and up
The activity ledger is Splyntra's tamper-evident record of governance activity. Every authorize decision and every agent identity event is written to it, so you always have a verifiable trail of what was decided and what happened.
How the chain works
The ledger is append-only and scoped per organization. Each entry carries:
| Property | Meaning |
|---|---|
seq | A per-org monotonic sequence number. |
prev_hash | The hash of the previous entry in the org's chain. |
hash | This entry's hash, computed over its contents and prev_hash. |
A database UNIQUE(org_id, seq) constraint guarantees no two entries share a sequence
number within an org, and the prev_hash → hash links form a chain: altering or
removing any entry breaks every hash after it. That makes tampering detectable rather than
merely discouraged.
Chain verification
Verifying the chain walks the entries in sequence and recomputes each hash. The result is reported as "Chain verified" when every link is intact, or "Chain broken @ seq N" pointing at the first entry where the recomputed hash diverges. Compliance reports carry a ledger-verified badge that reflects this check — see Compliance.
What is recorded
- Every governance decision — each
allow/deny/needs_approvaloutcome from the authorize flow, including which step produced it. - Every identity event — agent registration, credential issue/rotate/revoke, and trust decisions from agent identity.
Ledger writes are best-effort with respect to the caller: a ledger fault is logged but never blocks or fails the decision it is recording.
Endpoints
| Method | Path | Purpose |
|---|---|---|
GET | /v1/ledger | List ledger entries for the org. |
POST | /v1/ledger | Append an entry. |
Next steps
- Governance overview — the authorize decision flow.
- Compliance — ledger-verified SOC 2 / EU AI Act / NIST reports.