Evidence · Signum Causa
The record, demonstrated.
This is what Signum Causa produces, and what Signum Custos later draws on to evidence a control. The claim-to-source drill-down below is the product’s own component, running on this page — not a screenshot of it. Open a claim and the messages it was drawn from unfold with speaker and timestamp. One claim is deliberately ungrounded, and flagged as such.
INC-1002 · #inc-1002-auth-eu
sha256:7cdb…7ef3 · sealed
A. Rahman · sre · 2026-06-05T09:14:00Z
“pool sitting at 100/100, callers queueing”
D. Okafor · platform · 2026-06-05T09:16:12Z
“auth-eu latency tracks pool saturation exactly — every spike lines up”
A. Rahman · sre · 2026-06-05T09:19:40Z
“confirmed: connection pool exhaustion on the EU auth path”
M. Sattar · incident lead · 2026-06-05T09:24:03Z
“resizing the auth pool to 250, rolling now”
D. Okafor · platform · 2026-06-05T09:26:55Z
“250 applied in eu-west-1, queue draining”
Verify it yourself
Do not take our word for the seal.
Press Verify this seal above. Your browser recomputes the SHA-256 of the transcript and compares it with the hash printed on the record — the same mechanism the platform applies to every incident. Alter one character of the embedded data and the check fails.
- Canonical form. Keys sorted at every level, no insignificant whitespace, UTF-8. Two systems hashing the same record agree.
- Chained revisions. Revision n carries revision n−1’s hash, so removing or substituting a revision in the middle is detectable.
- Gaps are not tampering. Pruning under a retention policy is a legitimate operation, and the verifier reports a gap as a gap rather than crying tamper.