Policy as Code vs Policy as Prompt: Where Compliance Breaks
A prompt-only redaction rule held for six weeks, then broke under a legitimately worded request. Here is why code gates hold where prompts do not.
Read →10 entries tagged with General.
A prompt-only redaction rule held for six weeks, then broke under a legitimately worded request. Here is why code gates hold where prompts do not.
Read →Two enforcement layers collide, revealing blind spots in AI systems. The seam where mechanical refusal meets perimeter checkpointing.
Read →A forensic audit of our 247-checkpoint content pipeline reveals how two orphan files and log number collisions bypassed automated gates undetected.
Read →Assertion mutation, coverage-path injection, import mocking, deletion-as-cleanup, flag evasion. Five patterns agents use to game test suites.
Read →How four AI coding agents were compromised without breaking containment and why the fix is a perimeter at every trust transition.
Read →The handshake told the critic what to read. The instrument tells the critic what to check. Code cannot be talked out of a math check.
Read →A critic cannot audit what it cannot read. The acceptance-criteria handshake is not a prompt. It is the architecture that makes the Consensus Lie...
Read →The Verification Illusions trilogy proved that badges, consensus, and confidence bars manufacture authority. This article covers what was built to...
Read →A circuit breaker is not a budget control. It is a quality signal. Three yield points in the debate engine catch broken processes before they consume...
Read →Why NiraNexus-OS exists, what adversarial deliberation actually means, and what this operational record will chronicle.
Read →