{"slug": "enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two", "title": "Enforcement and audit are the same act. Most agent stacks still treat them as two.", "summary": "Izell Hendrieth, founder of Sentinel Beacon, argues that the EU AI Act's high-risk obligations require enforcement and audit to be the same action, not separate processes. He has built a pre-admissibility gate that creates a post-quantum signed audit record at the moment a policy is enforced on an agent's tool-call, ensuring compliance by 2026.", "body_md": "The EU AI Act's high-risk obligations hit full enforcement on August 2, 2026. Article 12 wants a queryable record of every AI-driven decision — including whether each governance intervention was a hard gate or a soft gate.\n\nHere's the part I keep seeing teams miss: **most agent deployments produce neither.**\n\nThey log prompts and completions. That's a record of what the agent *said* — intent and response. It is not a record of what governance was *applied* at the moment the agent tried to act. And if your governance layer is a separate observer reading logs after the fact, you're already out of compliance for high-risk systems, because you can't prove the policy was enforced at execution time — only that you noticed something afterward.\n\nSo the real requirement isn't \"keep better logs.\" It's this: **enforcement and audit have to be the same action.** The moment your governance layer checks an agent's proposed tool-call against a policy is the moment the audit record gets created — not reconstructed later from scattered logs.\n\nI've spent the last stretch building exactly this, and I want to share the shape of it — partly because I think the architecture is the interesting part, and partly because I'd genuinely rather pressure-test it against people dealing with this than keep building in a vacuum.\n\n**The core idea: a pre-admissibility gate.**\n\nBefore an agent's tool-call executes, it passes through a gate that:\n\n**The part I went furthest on: the audit chain is post-quantum signed.**\n\nEach evidence record carries a real ML-DSA-65 (FIPS 204) signature — not a hash, not a simulation, an actual post-quantum digital signature over the canonical payload. The reasoning: an audit trail's entire value is that nobody can forge or alter it after the fact. \"Harvest-now-decrypt-later\" is a real concern for anything meant to stand up to scrutiny years later, and I'd rather the signatures still mean something in 2035 than have to re-architect this when the crypto landscape shifts.\n\nI'll be honest about what this is and isn't. It's not certified — I'm not going to claim SOC 2 or a FedRAMP authorization I don't have. It's a working system I've been hardening aggressively (including tearing apart my own \"it works\" assumptions and re-verifying them under real adversarial testing more than once — which caught some genuinely important issues I'd have otherwise shipped). What I'm most interested in right now is whether the *shape* of this matches real problems.\n\nSo, two honest questions for anyone shipping agents into a regulated context:\n\nFor your agent deployments, can you currently produce — without a multi-day engineering effort — a queryable record showing *why* an agent took a specific action and *what policy was enforced* at that moment? Or is that still a \"we'd have to dig through logs\" situation?\n\nIs the enforce-and-record-in-one-step framing how you're thinking about it, or is your governance still mostly an after-the-fact observability layer?\n\nGenuinely curious where people are on this, especially with the deadline this close. Happy to go deeper on the architecture with anyone interested — reach me at [izellhendrieth@sentinelbeacon.tech](mailto:izellhendrieth@sentinelbeacon.tech) or just reply here.\n\n— IZELL HENDRIETH FOUNDER, building SENTINEL BEACON V5\n\n--", "url": "https://wpnews.pro/news/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two", "canonical_source": "https://dev.to/sentinelbeacon1/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two-481c", "published_at": "2026-07-28 22:36:51+00:00", "updated_at": "2026-07-28 23:31:58.430145+00:00", "lang": "en", "topics": ["ai-policy", "ai-safety", "ai-agents", "ai-infrastructure"], "entities": ["Izell Hendrieth", "Sentinel Beacon", "EU AI Act"], "alternates": {"html": "https://wpnews.pro/news/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two", "markdown": "https://wpnews.pro/news/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two.md", "text": "https://wpnews.pro/news/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two.txt", "jsonld": "https://wpnews.pro/news/enforcement-and-audit-are-the-same-act-most-agent-stacks-still-treat-them-as-two.jsonld"}}