# A copy carries the same digits.

> The number on your product identifies a kind of product. It was never able to identify that one. — Jewelry, watches and luxury — brand protection, and whoever answers the client.

**Verified 5 August 2026.** Three doors of the spine answer over HTTPS today — POST https://epcis.dev/translate, /validate and /hash — against sha256-pinned official GS1 artefacts, and 931/931 spine tests pass. Every open gap is a named entry in the open P0 ledger at /p0-ledger/.

## What it costs you

So the claim you actually need to make about a specific piece — it is ours, it was finished in that workshop, it left our hands and it has not left the chain since — has nothing underneath it. A certificate is a document about the piece. It is not the piece’s record, and it copies exactly as easily as the mark does, because both of them are only characters.

The second-hand market, the insurer, the customs officer and the client are asking one question in four vocabularies, and all four stop at the same wall: nothing distinguishes the object in front of them from a faithful copy of it, because nothing about the original was ever recorded about the original.

## What changes

visibility.cloud gives the individual piece an identity of its own and a chain of hands behind it: every handoff an event with an attested observer, identified by the standard’s own content hash (CBV 2.0 §8.9), append-only by construction, and readable by the other side without them joining anything of ours. A copy can carry the same digits. It cannot carry the same chain, and it cannot be given one afterwards, because no service identity in this system holds an UPDATE or a DELETE grant.

What this is not. It is not an anti-counterfeit mark and it does not make a copy detectable in the hand. Whatever is printed on the item can be printed again. What becomes checkable is the claim: a piece either has a custody chain that resolves and recomputes, or it does not — and that difference is arithmetic the other side can run for themselves. No figure about counterfeiting appears on this page, because we hold none we can show you.

## One place to point your agents.

Your agents will reason over anything you hand them. What they get handed is fourteen systems, a credential each, and no two of them describing the same object the same way.

visibility.cloud will onboard those sources as one surface: modern SaaS platforms through their own APIs, Apache Iceberg lakes read and written in both directions, the EDI mailbox that has been running since before anyone there was hired, and the print, scan and read events coming off the floor — landing as one event record with an attested observer on it, at the grain a question is actually asked at.

Then the agents get one secure place to explore it, under a seat with a written mandate: scope named, ceiling named, every read evaluated against the same grants every human read is. The point is not a chat window over a warehouse. It is that the answer comes back actionable — a bounded set of cases, a named handoff, a specific gap — instead of an integration project per source.

The sandbox is a named entry in the open P0 ledger (P0-A11), and the seat mandate it runs under is P0-A7. What is live today is the machine face this surface already publishes: /llms.txt, /icp.json, /agent-classes.json, /flow.json and /variants.json, plus the markdown twin of this page on this same route.

## What this read stands on

Evidence class: `structural-only`. No counterfeit rate, market size or resale figure is cited here, because none is held that can be shown. Every claim on this read is a checkable property of a record.

Go check us. It takes ten minutes and doesn’t involve us.
EPCIS 2.0 §7.2.2 defines five event dimensions: what, when, where, why, how. No performer is among them. The party fields are organisation-grain — EPCIS §7.3.6.4, CBV §7.4.3, CBV §8.7.1 (PGLN). The conformant path to a performer today is a namespaced user-extension field (EPCIS §6.3 / §9.1 / §10.1.3). So the standard can say a company did a process — its Who is the company, a GLN. It cannot say which person or which device observed the event at 06:12: no field names the performer. The specs are public. Don’t take our word for it.

## The other three bills

There is no single company message on this surface, by design — one defect, four costs.

- **Recall** (https://visibility.cloud/for/recall/) — One run went bad and you withdrew everything it could have been in. Food CPG and QSR — whoever owns the recall desk.
- **Shrink** (https://visibility.cloud/for/shrink/) — Every unit was scanned, and the investigation still ends at “seen here, then not.” Apparel and general-merchandise retail — loss prevention.
- **The discarded scan** (https://visibility.cloud/for/the-discarded-scan/) — The lane reads the serial, the lot and the expiry, and keeps none of them. Retailers and brands on the Sunrise 2027 timeline.

The typed index of all four, with each read's evidence class: https://visibility.cloud/variants.json