Name one consequential lane only
Runtime, browser checkout, MCP or repo audit remediation. Do not widen the story until one lane already survives cleanly.
NORNRCold external proof for one governed lane.
External proof / Format
A NORNR case study should read like one defended record, not like marketing copy around a dashboard.
The minimum external proof is one lane, one decision path, one named owner, one signed export, one archived bundle and one finance-readable handoff that survives outside the client.
Show intent, policy decision and review path
The case should explain what was attempted, why it cleared or queued, and who owned the review decision when human intervention mattered.
Carry the same path into proof and finance
The exact lane should survive into signed manifest, archived artifacts, finance packet and audit export without manual reconstruction.
This is a warm-stage surface, not the first exposure wedge
Use it after Governance Audit, Budget Shield and the first governed lane already exist. It is strongest when it packages evidence, not when it tries to create first interest alone.
The minimal externally defensible packet
Workspace, lane, owner, counterparty scope, decision basis, review owner, receipt posture, signoff status, artifact storage status and handoff destination.
Attach export, bundle and manifest together
Use the signed export, downloadable artifact bundle and machine-readable manifest together so another party can verify the same lane from different angles.
Do not lead with vanity metrics
“AI saved time” is weak. “This action cleared under mandate, survived review and produced a reusable finance packet” is the stronger external proof.