# VSA-3CS

Visible · Self-serve · A receipt · Three codes · Stamp

Canonical text · v1.0 · 18 November 2026

VSA-3CS is a library card catalogue for machines. Every record has a visible card, available through a self-serve fetch, accompanied by a signed receipt, findable through three code systems, and stamped with the date of its last completed check against the regulator. An agent takes the card it needs when it needs it.

## §01 · The contract

VSA-3CS defines how an artificial-intelligence (AI) agent or AI lab finds and reads a medicine card. It has five parts.

| Letter | Name | What it means |
|---|---|---|
| V | Visible | Every record has a card at its own permanent address, open for any agent or lab to read. Sitemaps list every card. |
| S | Self-serve | One fetch returns the card requested. An agent takes the card it needs when it needs it. There is no bulk download. |
| A | A receipt | Each fetch leaves a signed receipt: which card was read, and when. |
| 3C | Three codes | A card is found by its pack barcode (Global Trade Item Number, GTIN), its national pack code, or its authorisation number, wherever the regulator publishes that code. |
| S | Stamp | Every card shows the date it was last checked against the regulator. A completed daily read sets it. |

All five parts are required. A catalogue that offers only some of them does not conform to VSA-3CS.

VSA-3CS governs discovery, access and evidence of a read. DOSE-10060 governs the medicine record's content and signature. Conformance to one does not establish conformance to the other.

## §02 · Visible

Every record has a card at its own permanent address. That address continues to identify the same record when its content changes. Each signed version remains distinguishable from every other version.

The card is public. Any agent or lab may read it and verify its signature without a reader account.

Sitemaps list every card. They publish the catalogue of addresses; they do not constitute a bulk download of records.

The human page and the machine response present the same underlying record. A page exists only after its card does. A catalogue never claims cards that its node does not serve.

## §03 · Self-serve

An agent takes the card it needs when it needs it.

A fetch accepts a card's permanent address or any one of the three supported codes. The caller does not have to name the code system. Matching follows published, deterministic rules. Nothing is inferred from a similar name or code.

Where the input identifies one card, the fetch returns that signed card with its stamp. Where a code identifies several cards, the fetch returns the matching signed cards as a list. Where none matches, the answer is empty.

Several matches are never silently reduced to one. An authorisation number shared by several packs returns those packs.

The same lookup against the same record state returns the same card versions through every interface the node offers.

There is no bulk download.

## §04 · A receipt

Every completed fetch leaves a signed receipt, including a fetch that returns several cards or an empty answer.

The receipt identifies each card returned by its record and version, and states when the fetch occurred. An empty answer is recorded as empty.

The receipt carries a hash of the answer exactly as served and a hash of what was asked, never the text of the request. The issuer publishes exactly how each hash is made. A hash is an integrity mechanism, not a promise of secrecy.

The response supplies the receipt's identifier through a documented transport field, without altering the signed card. The caller retrieves and verifies the receipt by that identifier.

The producing node signs the card under its record key. The receipt issuer signs the receipt under a separate receipt key. No key signs the other's object. Public verification keys remain available for historical verification.

A receipt establishes what the service returned and when. It does not establish that an agent understood the answer or acted on it.

## §05 · Three codes

A card can be found through three code systems:

| Code | What it identifies |
|---|---|
| Global Trade Item Number (GTIN) | The trade item or pack identified by that barcode. |
| National pack code | The pack identified under the market's national code system. |
| Authorisation number | The authorisation, which may cover several packs. |

A card carries the codes its cited source publishes. A missing code remains unknown. A node never invents a code to complete the set.

The node publishes its matching and normalisation rules. Leading zeroes and punctuation that distinguish national codes are preserved. An input of digits only, shorter than 14 digits, is looked up both as given and padded with leading zeroes to 14 digits, the notation in which a pack barcode is held; no GTIN check is made first.

Code systems and markets may overlap. Where the same input matches several cards, all matches are returned.

Two cards that share a code, an ingredient or an authorisation are still two different packs.

## §06 · Stamp

Every card shows the date of its last completed check against the regulator.

The stamp keeps four events distinct:

| Event | Meaning |
|---|---|
| Regulatory effective date | When the regulator states that a decision or status took effect. |
| Source reading date | When the node read a value from its source. |
| Stamp | When the node last completed the check covering the card. |
| Receipt time | When the service returned the answer. |

A node reads each market it holds once a day. A completed market read produces a signed stamp identifying the market, the date and the change checkpoint it covers. That stamp is attached to the cards it covers.

Cards are not signed again merely because a completed check found no change.

A failed or incomplete read issues no new stamp. The previous date remains visible. A new date must never imply that a check succeeded when it did not.

The stamp is a date, not a countdown. It does not establish availability, regulatory approval or permission to act. A record that is no longer in the regulator's file reads withdrawn on its card, with the date it was first found gone and the regulator's last published status; withdrawn states that fact and no other.

## §07 · What the protocol does not do

VSA-3CS does not authorise prescribing, dispensing, import or sale.

It gives no dosing advice or clinical recommendation.

It does not certify a medicine, manufacturer or supplier.

It does not verify an individual physical pack, serial number or lot.

Cards and receipts carry no patient data.

Signature verification establishes integrity and attribution. The accuracy of the source and the node's reading remain separately assessable.

A successful fetch is a read, not permission for a downstream action.

## §08 · Publication discipline

The approved human text and its machine representation come from one source.

Every published interface describes an endpoint that exists and the behaviour it serves.

Coverage is generated from records actually served. Counts are never entered as fixed claims in protocol prose.

The protocol version, schema version and deployment version remain distinguishable. A new deployment is not a new protocol.

Earlier published versions remain identifiable. Signed history is preserved.

## §09 · Conformance

A conforming node demonstrates all five parts:

| Part | Required evidence |
|---|---|
| Visible | Permanent public card addresses and sitemaps listing every card. |
| Self-serve | A working fetch that returns the matching card, matching cards or an empty answer, under published matching rules. |
| A receipt | A retrievable signed receipt for every completed fetch, with reproducible hashes and public verification keys. |
| Three codes | Published support for GTIN, national pack code and authorisation number, with missing codes left unknown. |
| Stamp | A verifiable date from a completed regulator check, with no new stamp after a failed or incomplete read. |

All five must be observable in operation. A description of a capability is not evidence that it works.

Visible cards. Self-serve reads. Signed receipts. Three code routes. A dated check.

VSA-3CS — the library card catalogue for machines.

---

Human page: https://vsa-3cs.org/ · JSON: https://vsa-3cs.org/vsa-3cs.json · DOSE-10060: https://dose-10060.org/

FOR AGENTS: [/index.md](https://vsa-3cs.org/index.md) · [/vsa-3cs.json](https://vsa-3cs.org/vsa-3cs.json) · [/llms.txt](https://vsa-3cs.org/llms.txt) · [/sitemap.xml](https://vsa-3cs.org/sitemap.xml) · [MCP server card](https://dose-10060.org/.well-known/mcp/server-card.json) · [Agent card](https://dose-10060.org/.well-known/agent-card.json) · [Keyring](https://dosidal-registry.ai/.well-known/jwks.json) · [security.txt](https://dose-10060.org/.well-known/security.txt)
FOR BUILDERS: [fetch](https://dosidal.ai/docs#tool-fetch) · [verify_card](https://dosidal.ai/docs#tool-verify_card) · [changes](https://dosidal.ai/docs#tool-changes)
FOR HUMANS: [Contact](https://vsa-3cs.org/#contact) · [Standard](https://dose-10060.org/) · [Library](https://book-of-dose.org/) · [Docs](https://dosidal.ai/docs) · [Setup](https://dosidal.ai/setup) · [Status](https://dosidal.ai/status) · [Terms of Use](https://dosidal.ai/terms) · [Privacy](https://dosidal.ai/privacy) · [Disclaimer](https://dosidal.ai/disclaimer) · [Legal](https://dosidal.ai/legal)

VSA-3CS · Canonical text · v1.0

Dosidal AI Corp. · 6687 Nelson Avenue, Suite 304, West Vancouver, BC V7W 2B2, Canada · © 2027 Dosidal AI Corp.
