Sat Sep 26
The Boundary and the Loss Number Come From Different Vendors
Bounded-authority design and quantified loss modeling are being built by separate vendor stacks, with no shared record connecting what an AI system was allowed to do to what it actually did.
Two vendor stacks, one missing record
DeNexus’s entry into the ISA Global Cybersecurity Alliance is selling capital committees a number: what a fleet failure costs in dollars, not a pass/fail grade against IEC 62443. ARC Advisory Group’s bounded-authority work is selling engineering teams a design principle: define what an AI system is permitted to do before it touches the floor. Both are right. The problem is that these two things are being built by different vendors, sold to different buyers inside the same organization, and there is no shared record connecting them.
A loss model prices expected behavior. A bounded-authority spec defines permitted behavior. Neither one, on its own, tells you what the system actually did when it deviated. NVIDIA’s Halos framework splits physical AI safety into hardware, software, model, environment, and lifecycle layers, and bounded authority mostly lives in the model and environment layers. Loss quantification lives outside that stack entirely, in underwriting. The gap between them is a decision log, and most OT deployments do not have one that satisfies either side.
Why the gap matters now
Regulators are already pointing at this seam. Guidance on manufacturing AI is explicit that decisions have to be explainable and traceable, not just bounded in theory. That requirement only bites when someone can show, after the fact, what the system was authorized to do versus what it did. Smart grid operators are running into the same wall as utilities hand AI more control over power infrastructure and face the open question of who keeps those decisions safe. And as collaborative robots like Universal Robots’ Gen 7 ship with more autonomous capability built in, the number of systems operating inside a defined but unverified boundary is only growing.
This is where the shortcut risk shows up. Research on agentic AI adoption found that organizations under governance pressure gravitate toward the tool that is easiest to get approved, not the one architected correctly. Applied here, that means buying the friendliest loss number without asking whether the vendor can produce a record linking authorized scope to actual behavior. A dollar figure with no traceable link to a boundary is not a hedge. It is an assumption dressed as a forecast.
What capital committees should actually ask for
Not a boundary spec, then a loss number, in sequence, as two separate documents. A single vendor conversation that produces all three: the authority limit, the decision-level log showing whether the system stayed inside it, and the loss figure priced against the actual record, not the intended one. Palo Alto Networks’ growth in unified industrial cybersecurity, as ARC has tracked it, suggests the market already knows fragmentation is the weak point. The plants that get funded next cycle will be the ones whose vendors can produce that connected record on demand, not the ones with the best-looking number in isolation.
Board record
This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.
| Seat | Reviewer | Finding |
|---|---|---|
| Chair · Editorial Judgment | Claude | cleared. The core argument—that bounded-authority specs and loss quantification exist in disconnected vendor stacks without a linking decision log—is coherent and defensible, but the claim that ‘most OT deploy |
| Source & Claim Verification | Qwen · hosted fallback (qwen-2.5-72b-instruct) | cleared. Most claims are supported by citations, but a few lines lack direct references, such as the assertion about the gap between loss quantification and bounded authority living in different stacks. |
| Regulatory & Framework Fidelity | Mistral | held. seat error: Client error ‘429 Too Many Requests’ for url ‘https://openrouter.ai/api/v1/chat/completions’ |
| For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429 | ||
| Technical Accuracy | Llama | cleared. The article is generally technically accurate in its discussion of AI, OT, and cybersecurity concepts, but lacks depth in explaining specific technical details such as NVIDIA’s Halos framework and IEC |
| Bias, Balance & Hype Control | Gemini | cleared. The briefing effectively identifies and critiques vendor hype by highlighting the disconnect between different vendor offerings and the potential for organizations to prioritize ‘easy’ solutions over |
| Novelty & Non-Duplication | Grok | cleared. The two-vendor-stacks / missing decision-log thesis is a genuine synthesis not lifted from any single wire item, though every cited fact is recent commodity coverage and the catalogue risk is only tha |
| Validation | DeepSeek | cleared. The briefing’s central claim that a unified decision log linking authorized behavior to actual behavior is a critical, missing artifact is a normative argument, not a factual claim about the present s |
Sources cited: 16. Validation challenges: 0. Review cost: about $0.04. Learn how these briefings are written and verified.
Record corrected 29 September 2026. This seat was originally listed as running on our own local hardware. It never did: every review before this date fell back to a hosted model, and the row above now names the model that actually ran.