# The answers — you will pay for answers. Never for the record.

visibility.cloud sells answers — where is it, who touched it, prove it — as views over the same catalog the developer surface, epcis.dev, queries. Recomputability is structural: there is nothing to audit because there is nothing separate. Everyone in this market has built a network that is authoritative because you joined it. This platform makes a record that is verifiable whether or not you joined anything — and it carries, in the record itself, an attested answer to who observed the event, including when the observer was an agent.

## The trace: where is it, and who touched it.

For the director of food safety who has run the 24-hour mock-recall exercise and knows exactly where it broke.

One lot, one EPC, one question — the full event chain in seconds, and at every hop not just a company doing a process but the attested observer: which person, which agent, which device, at the moment of the scan. Today's record shows a case arrived at a DC; it never shows who received it. This answer shows both.



## Chain-of-custody evidence: the record that holds up in the room.

For loss prevention, vendor compliance, and anyone who has ended an investigation at “seen here, then not.”

A custody chain you can hand to a regulator, an auditor, or the other side of a chargeback dispute — every event content-hashed per CBV 2.0 §8.9, append-only with corrections as declared events, carrying the attested observer — verifiable whether or not the counterparty joined anything.



## Exception views: the handoffs that went silent.

For the operator whose remaining inventory error is handoff error — which is a who problem, not a count problem.

The standing view of every handoff where the record went quiet — received with no performer, shipped with no custody closure, a franchise or co-manufacturer boundary crossed with nothing attested on the far side — triaged before the auditor or the claim finds it first.



## SharingGrants: scoped sharing that compiles, and revokes, cleanly.

For the 3PL answering a tender's traceability clause, and for the supplier-data steward who has to share without merging.

Share exactly these goods, these event kinds, this window, at this attribution grain — with a customer, a shipper, or a regulator — as a grant that compiles to a spine-native scope, is enforced identically on every door, and revokes without rewriting history. Answer the traceability clause with a grant, not a paragraph.



## Recall & audit readiness: FSMA 204 without the war room.

For the quality director audited on two regimes across one plant network, and the fractional food-safety manager running recall drills on spreadsheets.

When the call comes, the trace-back that took days across the co-manufacturer or franchise boundary becomes a query: covered-food KDEs and CTEs, custody closed at every hop, exportable in the shape the auditor asks for — so the 2028 enforcement floor is a de-risking deadline you beat early, not a gun to your head.



## The Sunrise 2027 decision read: the executive gift.

For the VP who owns a 2027 date she did not set — delivered before you are asked for anything, because it is documents.

Exactly what Sunrise 2027 requires of you — GTIN owner, converter, or retailer; which symbology and which URI form is genuinely your decision; what the lane must extract versus what nothing obliges you to encode — and the one structural fact you can verify without us: EPCIS 2.0 §7.2.2 defines five dimensions and no performer — the Who it carries is a company, a GLN. Ten minutes, the specs are public, don't take our word for it.



## Seats & deputization: the mandate your agent works under.

For the human who will provision an agent seat — the ops VP with no engineering function, and the operator of a triage agent.

A human seat provisions an agent seat with a written mandate — scope named, ceiling named — so the agent that works your exception queue or answers your customer's verifier acts under authority you granted and can be shown to have acted under it. provisionAgentSeat is a ceremony with a human audience, not a route; identity resolves through id.org.ai — Agent. Human. Thing.




## What will cost money, in what unit

- **Capture** — $0 per event, as policy
- **A trace** — per answered trace
- **A custody evidence pack** — per rendered pack
- **Exception views** — per workspace, as a standing view
- **SharingGrants** — per active grant
- **Seats, human and agent** — per seat
- **Retention beyond the free floor** — per event-month of durable storage

## For agents

/icp.json — the business-principal contract. /agent-classes.json — the class enumeration. /flow.json — the interview instrument. /variants.json — the four per-audience reads with each one's evidence class. There is no bookDemo verb, and there will not be one.
