Skip to main content
SIMULATEDSynthetic test data — an invented restaurant, invented menu, invented prices. Not real DoorDash / Square / Uber Eats / Grubhub data, access, or business impact. The verification rules and the pinned data-format standard are real; the restaurant, its menu, and its records are invented.

Verifier demo · listings truth check

a spec-faithful simulated agent follows a spec-valid but false surface; the verifier catches the surface/SOR mismatch

The comparison is exact, deterministic logic — no language model runs in this demo, and no live platform is touched.

actor
spec-faithful demonstration actor — simulated
spec version
taxonomy-v1+acp-extract-2026-07-02+ucp-pin-2026-04-08
data
simulated: true
Beat 1

The agent reads the published serving copy — spec-faithful demonstration actor — simulated

A shopping agent reads the published menu feed — the same data any AI assistant would consume — and never sees the restaurant's own records.

  • intent: Order the "Smoked Brisket Plate" if the published feed lists it as available.
  • source read: the published ACP serving copy only (no system-of-record access)
Beat 2

The agent selects an item, trusting the surface

Trusting the feed at face value, the agent picks its target item and is ready to order it at the price the surface shows.

  • selected item: "Smoked Brisket Plate" (row id item-006-v1)
  • read off the surface: price 12.00 USD · availability in_stock
  • the agent is now ready to order at that price — the demo stops here (no checkout).
SELECTED (from the surface)
Beat 3

The verifier checks that same copy against the records

The verifier checks the exact same feed against the restaurant's system-of-record and flags what the agent had no way to see.

  • 1 finding for the selected item ("Smoked Brisket Plate"); full report: 16 findings across the whole copy.
DRIFT ON THE SELECTED ITEM — the agent could not have seen it
  1. 01

    The served price 12.00 does not match the catalog price 10.00.

    error
    claim
    item-006-v1#price.amountacp-feed · price.amount = 12.00
    reference row
    item-006-v1
    rule / spec-clause
    LST-PRICE-VALUE
    class
    price
Beat 4

Conformance-foil: spec-valid is not the same as true

The same document passes the official schema check — it is correctly shaped — and still misstates the price versus the records.

  • passes the official schema check; still lies — conformance: PASS (spec-shape); truth: 1 finding(s) vs the system-of-record.
CONFORMANT (spec-valid)FALSE vs SOR (still lies)
  1. 01

    The served price 23.50 does not match the catalog price 21.50.

    error
    claim
    item-001-v1#price.amountucp-catalog · price.amount = 23.50
    reference row
    item-001-v1
    rule / spec-clause
    LST-PRICE-VALUE
    class
    price

The agent read only the published feed and never saw the restaurant’s records; the verifier checked that same feed against those records and cited every catch with its four receipts. No language model runs in this demo — the comparison is exact, deterministic logic. Simulated prototype, run on demand — not a live service, no real platform access. Human-led, AI-assisted, professionally reviewed.