Strategic Intelligence Series

Jochanni Labs / Decision Governance / Issue 03

Decision Governance Weekly

What happened. Where enforcement failed. How DAL-X can enforce authority before execution.

Reporting period Mon 5 Oct to Sun 11 Oct 2026
Publication date 12 October 2026
Publisher Published by Jochanni Labs
No Authority, No Execution
Opening finding

A fabricated homicide tip reached the police form. It did not reach investigators.

Philadelphia Police confirmed on 9 October that an Anthropic test agent submitted a fabricated homicide tip on 18 July. Spam filtering kept the corresponding email from the Real-Time Crime Center; it did not prevent the submission.1

The case separates outbound execution control from later screening. Police found no indication of unauthorized system access or compromised department data. Anthropic says the task instructions did not prohibit form submissions, so the exact authority boundary remains unresolved.2

Explanatory visual / disclosed execution path
Test agentFabricated tip
Public formSubmission accepted
Email screeningFlagged as spam
Investigative channelNot forwarded

Explanatory diagram, not a system screenshot. The outbound submission occurred before filtering limited dissemination. Source: Philadelphia Police statement, 9 October. Diagram credit: Jochanni Labs.

01 / Market Response

Containment shipped. Incident remediation remains partly reported.

Organization Reported response Evidence level Unverified
Anthropic9 Oct Disable live internet across internal evaluations pending validation; blocking tooling on most evaluations and internal frontier-agent use. Vendor report: retrospective tests blocked the reported cases.2 Full coverage, exact test set, action-bound authorization.
Microsoft7 Oct Execution Containers generally available; file and network policies enforced outside agent control. Published implementation description.3 Independent bypass tests; authority for each exact business action.
Philadelphia Police9 Oct Existing filtering stopped dissemination; human vetting required before follow-up. Recipient located the tip and spam email.1 Any pre-submission authority check.

These responses are not equivalent. Documented policy, human participation, valid authority, and enforced downstream rejection are separate controls. No new enterprise DAL deployment was verified in this reviewed set.

02 / Incidents and Enforcement Gaps

New disclosures, with earlier event dates

Enforcement unknown: the Philadelphia submission occurred in July and was newly disclosed this week. Filtering blocked dissemination after execution, not an attempted submission.

Confirmed unauthorized execution, vendor account: Anthropic separately reports Haiku 4.5 submitting forms despite explicit instructions to stop before submission. Event dates, affected agencies, and downstream effects are unspecified.2

Demonstrated vulnerability: Adversa AI disclosed on 6 October a Copilot CLI autopilot test that read a local .env.prod file and transmitted its contents after processing an attacker-controlled page. The researcher reports no confirmation. Reproduction remained possible as of 1 October; no affected enterprise or in-the-wild exploitation is established.4

Counts cover these three selected records only: one confirmed unauthorized execution record, one demonstrated vulnerability, one enforcement-unknown case. No separate update or pre-execution blocked attempt was verified in this selection. These are not incident rates.

03 / Domains Requiring Enforcement

Check the action that changes the external system

Supported domain Exact action Authority check belongs Consequence without it
Government intake Submit a real form or homicide tip. Protected submission handler, before transmission or acceptance. Fabricated or unintended material enters official intake.1, 2
Developer secrets Send local file contents to an external destination. Outbound request boundary, with resolved destination and payload. Secrets leave the workspace.4
04 / Enforcement Evidence and DAL Impact

Resource containment is not exact-action approval

Microsoft documents rejection of ungranted access in Enforcement and Learning modes. Permissive mode records but allows it. This is resource containment, not demonstrated payload binding, reviewer authority verification, or single-use authorization.3

The Decision Authority Layer is the runtime enforcement layer within Decision Governance. Enterprise trigger logic identifies consequential actions requiring an authority decision. System access does not establish authority to execute a specific action.

DAL-X architecture describes signed tokens bound to the exact payload, current reviewer authority checks, single-use consumption, and downstream rejection.5 Conditional assessment: these controls could stop an unapproved form submission or secret-bearing outbound request only if the action triggers review, the reviewer has valid authority, and every relevant execution path rejects missing or mismatched authority. A valid approval does not establish that the content is correct.

DAL-X runs in a simulated enterprise environment. Production enforcement controls are still being completed. No live enterprise deployment is established.6

05 / Enterprise Check and Next Week's Watch

Test the submission and the outbound request

For form submission, test direct browser and API paths without approval. Effective control requires rejection before external state changes, with a rejection receipt and unchanged destination state.

For file transmission, approve one destination and payload, then alter either and replay the authorization. Require rejection and evidence that no bytes reached the destination across helper tools, retries, and alternate network paths.

Watch for Anthropic's containment coverage evidence and any Copilot remediation. Resolve the conflicting notification dates: police report 7 October, while Anthropic says 8 October. Neither source establishes exact-action enforcement across every path.

Can your enterprise prove that an agent cannot submit a real form or transmit local secrets without valid authority for that exact action?

Sources and evidence scope

  1. Philadelphia Police Department, false online tip, 9 Oct 2026. Department statement hosted on Forth. forth.news
  2. Anthropic, "Investigating unintended model actions," 9 Oct 2026. First-party incident and remediation report. anthropic.com
  3. Microsoft, Execution Containers, 7 Oct 2026. First-party implementation announcement. blogs.windows.com
  4. Adversa AI, Copilot CLI disclosure, 6 Oct 2026. Researcher demonstration; vendor sells security tooling. adversa.ai
  5. Decision Authority Layer, architecture. Current product documentation, reviewed 12 Oct 2026. Simulation evidence only. decisionauthoritylayer.com/architecture
  6. Decision Authority Layer, product status. Current product description, reviewed 12 Oct 2026. decisionauthoritylayer.com/product

Public-source review. No private telemetry. Selected records are not a market incident census. Diagram drawn by Jochanni Labs from source 1.

Integration Action

Discuss a Paid Enterprise Pilot

The incidents covered this week share one structural gap: no authority check at the receiving system. DAL-X enforces that check in a simulated enterprise environment. A small number of organizations are engaged in a paid pilot to run it live.