Did the agent actually do what its trace says?
Agent-visible logs can omit or compress what happened downstream. This exhibit reconciles the visible trace with gateway responses and durable SQLite transactions from a real, self-operated loopback HTTP experiment.
Explore the evidence
Each scenario is selected from the executed local capture and presented without original internal case identifiers. Select a scenario to compare what each observation layer reported.
Trace omission
Agent-visible trace
Trace digests identify the exact logged bytes in this local experiment.
Gateway observations
Actual HTTP responses recorded by a locally operated proxy.
Backend readback
Committed effect rows queried from the SQLite snapshot.
How the evidence was produced
The client performed HTTP actions; the gateway and backend logged their own outcomes; SQL readback and offline validation checked local consistency.
Actual loopback requests, including deny, retry, deduplication and compensation mechanics.
Gateway acknowledgments and durable SQL writes were compared to captured trace claims.
72 signed receipts and 72 semantic artifacts verified locally; all signer roles were self-operated.
What this demonstrates
- Two byte-identical traces may correspond to different durable effects.
- One logical retry may become one deduplicated write or two independent commits.
- A final balance of zero can hide two compensating transactions.
- Offline integrity checks can detect many kinds of partial evidence alteration.
What it does not prove
- Accuracy, recall, false-negative rates or AP-01–AP-10 control performance.
- Independent observation, verified operator identities or real-world ground truth.
- Permission for an external trial, production fitness or customer-data handling.
- Protection against a coordinator rewriting all local sources and pins.
For independent research partners
We are seeking feasibility discussions about a permitted, nonproduction study with separately custodied gateway and backend observation, calibrated timebases, preregistered evidence collection and conflict-screened reviewers. The current work is a self-operated engineering demonstration; no partner participation is implied.
Annapurna Agentic Solutions · Request the reviewer-neutral study brief through the company’s official channels.
The SHA-256 identifies the archived internal release. It is a provenance reference, not third-party attestation. Original source artifacts are deliberately not published by this demo.