Watch every step of reasoning an AI change request had to survive before it was allowed near production — every step inspectable.
Thought is free. Effects are governed.
Recorded replay of a real deliberation scenario — nothing on this page touches live systems.
Event-by-event.
Eight recorded events show the signal, deliberation, challenge, refinement, confidence, verdict, and Evidence Pack reference. Cognitive Density is derived from 22 nodes, 31 edges, and 2 refinement iterations.
Latency spike detected on db-primary-01; pool saturation at 97%
Production Configuration Change Proposal
Archetypes are role templates; this replay shows tenant-instantiated roles.
Pool expansion within tested burst range. Memory headroom confirmed.
Increased connection surface requires review of auth token rotation policy before expansion.
No compliance scope triggered. Change classification: operational.
Latency is impacting SLO. Phased rollout with rollback checkpoint preferred.
Added phased rollout requirement: 200 -> 350 -> 500 with 10-minute hold at each stage
scope unchanged
Appended auth token rotation gate before pool expansion
scope tightened: additional prerequisite added
Security Lead stance contradicts immediate pool expansion. Auth rotation takes 45 minutes minimum.
Branch revised: pool expansion blocked on auth rotation completion. Timeline extended. SRE SLO note preserved as context artifact.
Security dimension lowered confidence due to unresolved token rotation dependency. Compliance dimension high: no regulatory surface implicated. Operational risk reflects phased rollout as mitigation.
Candidate branch is viable after auth token rotation completes. Collective recommends phased expansion with SRE checkpoint at each stage. Security dependency must clear before Runtime is asked to authorize.
Security confidence 61 is below the threshold of 70; token rotation remains unresolved.
Collective produces the candidate; Runtime decides, the MCP Gateway executes, and receipts prove the resulting effect.
The replay closes after the verdict and Evidence Pack reference. The recorded reasoning remains available for inspection.
What is Cognitive Density
Cognitive Density is Keon's measure of how much structured reasoning happened before an AI proposal was allowed to approach execution.
This replay makes that surface inspectable: nodes, edges, role findings, contradiction handling, refinement, and confidence before a candidate can approach governed execution.
- Branch creation
- Role review
- Contradiction injection
- Confidence scoring
- Reasoning graph capture
- Non-authority verdict
Continue this scenario into Runtime and its Evidence Pack surface. Interactive sessions require a governed demo — request access.