Executed local workflow · 9 September 2026
The chain,
not just the calls.
A deterministic driver discovered operations, searched for a document, passed its ID into a read, assembled a source-backed citation and confirmed a denied role could not repeat the read.
Cross-step execution
Data had to survive the hand-offs.
- 01HEALTHFixture ready
WF-EV-001 - 02DISCOVERTwo required operations found
WF-EV-002 - 03SEARCHdemo-002 selected
WF-EV-003 - 04READSelected ID propagated
WF-EV-004 - 05CITEStatement and source matched
WF-EV-005 - 06DENYDenied role rejected
WF-EV-006
What was verified
Sequence, provenance and permission.
A collection of passing calls is not automatically a passing workflow. This run also checked that each operation was discovered before use, the search result became the read input, and the citation reused the returned source.
- DISCOVERY GATE
search_documentsandread_documentwere present before either was called.- DATA FLOW
demo-002moved from the search response into the read request without substitution.- CITATION
- The statement appears in the returned text and the source remained
demo://documents/demo-002. - LEAST PRIVILEGE
- The denied role received HTTP 403 when attempting the same document read.
Local output under test
“Renewals require 30 days notice.”
demo://documents/demo-002The words and source came from the fictional fixture. This is not a statement about a real policy or customer document.
Read the boundary
This is scripted workflow evidence—not agent-client compatibility.
The orchestrator was our deterministic test driver. No Codex session, Sourcegraph server, autonomous reasoning, conformant MCP implementation, external network or customer system participated. PASS applies only to contract 1.0.0 and fixture-3.
The earlier WRK-L01 result remains BLOCKED in its original frozen run. This later run does not rewrite it.
ZIP SHA-256
7da0acbf1316ca2651183d48a0de60d38d71898bee7548d5373cab2100b76f56MANIFEST SHA-256
f02bdc94e8f3b6b0cb73a0aedf097825a78f999614395300fd16afe54a895e76