Cairn

./provenance — sealed

Every change an agent makes, recorded as a stone on the path.

Query the chain six months later and the answer is still there. A causal provenance graph for every agent decision.

“Why did the AI change that file? Nobody knows.” — until now.

the chain

14:22:51 UTCUser intent
inbound: “add SSO to the auth module”
intent.parsermodel: haiku-3.5constraints: 0

Resolved a free-text request into a scoped engineering goal.

14:22:58 UTCPlan
PLAN.md + 4-step decomposition
strategy-plannermodel: opus-4.7constraints: 1

Limited blast radius to src/auth/* before any file was touched.

14:23:02 UTCFile decision
src/auth/sso.ts · chose NEW over patch
refactor-botmodel: sonnet-4.6constraints: 2

Rejected mutating session.ts — its JWT interface has 6 downstream callers.

14:23:05 UTCConstraint check
policy/pii.never.logged → PASS
guardrail.gatemodel: haiku-3.5constraints: 2

Verified the planned diff writes no PII to any log sink.

14:23:07 UTCEdit
src/auth/sso.ts +148 / −0
refactor-botmodel: sonnet-4.6constraints: 2

Wrote a SAML assertion parser. Preserved the JWT contract intact.

14:23:14 UTCVerified
src/auth/sso.test.ts · 12/12 pass
verifiermodel: sonnet-4.6constraints: 1

Malformed assertion returns null rather than throwing. Chain sealed.

chain sealed · 6 events · 23s elapsed

replay the chain

askwhy did auth.ts change on Monday?
hop 1 → 14:23:07edit on auth/sso.ts by refactor-bot
hop 2 → 14:23:02chose a NEW file (session.ts had 6 callers)
hop 3 → 14:22:58plan scoped the work to src/auth/* — at user request

Root cause: the user asked. The path proves it — no guessing, no archaeology.

The path is the proof.

$ cairn record →