Controlled technical evidence

Exact-action authorization case study

Reviewed payment integration and separately recorded v1.5.2 local mock execution explain the boundary from approval to verified effect.

What has been independently reviewed?

AgenTrust PR #201, merged September 20, 2026: 27 adapter tests in maintainer reproduction; the exact $250,000 payment committed once with TRACE, while the changed $260,000 path was refused with zero commits and no TRACE. PR #236, merged October 6, 2026 after the October 3 review: 36 integration tests, 97 negative wrapper/direct-executor probes refused without protected effect and four positive executions. These validate bounded integrations, not the whole proprietary runtime or all routes.

How does authorization differ from execution?

In a separate v1.5.2 controlled local mock-target run, the changed amount returned HTTP 409 with no observed mock commit, a tampered consume acknowledgement was refused, and an exact verified consume produced one recorded local effect. The pre-effect packet reports CONSUMED_OUTCOME_UNKNOWN (checkpoint 4); the exact-effect packet reports EXECUTED_EFFECT_FORMED (checkpoint 5) after an accepted signed outcome receipt. The former is not proof of no effect. Both historical checks used development test trust; V16 current freshness was NOT RUN. No real financial transfer, independent production log or customer deployment is claimed.

Inspect the ten selectable proof packets · Before outcome packet · Recorded exact-effect packet · Reference execution observations.

Historical video and accessible transcript

The 65-second historical DA overview describes the PR #201-era verified adapter milestone, not the entire current runtime qualification.

00:00.000 AI agents can now move money and change records. The question is whether this exact action is authorized to happen.

00:07.500 OntoGuard sits at that decision boundary. It evaluates the exact proposed action against evidence, governing basis, intent, and authority.

00:15.500 The result is explicit: ALLOW, BLOCK, or ESCALATE to qualified human authority.

00:24.000 Change something material — and the prior decision no longer binds. Authorization binds to the action that was actually evaluated.

00:33.000 OntoGuard records the decision: release state, human-review requirement, and whether the protected consequence formed.

00:42.000 A self-contained headless layer inside the enterprise execution environment.

00:51.000 AgenTrust Marketplace — Verified tier. Twenty-seven of twenty-seven adapter tests passed in maintainer reproduction.

00:58.500 OntoGuard. Decision Authorization for Agentic AI. ALLOW. BLOCK. ESCALATE.

Technical note by OntoGuard · product evidence and review scope are identified in the linked materials. Publication approval pending.

Evidence and buyer questions

What happens on changed payment amount?

In PR #201 (merged September 20, 2026), 27 adapter tests were reproduced; the exact $250,000 action committed once with TRACE, but $260,000 was refused, pending, zero commits and no TRACE. This is bounded reviewed integration evidence, not actual customer funds or every execution path.

Inspect source or product evidence

What did PR236 test?

PR #236 (merged October 6, 2026) reviewed 36 integration tests: 97 negative wrapper/direct-executor probes refused without protected effect and four positive executions. The evidence covers the reviewed adapter/harness, not all proprietary logic or deployment-wide non-bypassability.

Inspect source or product evidence

Does authorization prove execution?

No. In the local v1.5.2 mock run, checkpoint 4 records CONSUMED_OUTCOME_UNKNOWN, not proof of no effect. Checkpoint 5 records the accepted signed exact-effect receipt. This is a controlled mock target, not an actual payment or independent production log.

Inspect source or product evidence

Does historical DA verification establish current freshness?

No. Historical verification with development test keys and historical-only age policy is distinct from online current freshness. V16 was NOT RUN. The controlled v1.5.2 reference log is not an independently operated production transparency log.

Inspect source or product evidence