CAPTURED 16 SEPTEMBER 2026 / SYNTHETIC INPUTS
What the code
actually did.
This record comes from executing a three-node read-only workflow against a local HTTP gateway and temporary SQLite stores. It is separate from the predefined browser simulation.
| Event | Observed result |
|---|---|
| First execution | RUN · RUN · RUN |
| Identical repetition | REUSE · REUSE · REUSE |
| Authority revoked | Delivery lookup and retry return 403 PRODUCER_AUTHORITY_REVOKED; callback counts stay unchanged. |
| New authority granted | RUN · RUN · RUN; no reuse of the revoked producer’s work. |
| Source A changes | RUN · REUSE · RUN; the independent extraction is retained. |
Source and integrity
Product source checkpoint: 65c61d123041d8bacbf3d5c2baf9ed5ef1484a51. Execution mode: source checkout, local loopback, synthetic inputs. This is a captured result, not an API that executes when you open the page.
JSON SHA-256: 97b34a77345cf4f9798fa50b1815a5be249e717822a2b5625e34e0a77776974b. This checksum detects a changed download relative to this page; it is not a signature or independent attestation.
What this does not prove
The gateway in this example coordinates work; it does not hold or deliver protected result bytes. This run does not establish protected-byte delivery, PostgreSQL row-level isolation, a live provider integration, customer savings, production deployment, capacity or security certification.
The three-node example does not exercise concurrent JOIN. JOIN is a separate product behavior and is not credited by this record.