# transactions.dev · by visibility.cloud

A business document is a company's claim and never a unit's record — its parties are
organizations, and organizations do not scan things. The join to attested custody is the job.

The business-transaction layer of the visibility.cloud family. The canonical document is the
native form; X12 and EDIFACT/EANCOM are its conformant lossy-down projection. Documents in any
face compile to CBV bizTransaction context on conformant EPCIS 2.0 events.

Run it, keyless, from an empty directory — these are the two runs the landing page renders:

    curl -sO https://transactions.dev/specimen/856-ship-notice-01.edi
    npx -y transactions.dev@0.2.0 join 856-ship-notice-01.edi --tz +00:00 --json

    curl -sO https://transactions.dev/specimen/856-receipt-01.edi
    curl -sO https://transactions.dev/specimen/events-receipt-01.jsonl
    npx -y transactions.dev@0.2.0 reconcile 856-receipt-01.edi \
      --against events-receipt-01.jsonl --tz -05:00

The specimens are served from this origin because the corpus is not inside the npm tarball;
their sha256 digests are at https://transactions.dev/specimen/DIGESTS.txt. reconcile exits
1 on this pair (0 agree, 1 discrepant, 2 inputs unusable).

Verbs: parse · emit · validate · ack · intake · join · reconcile · pins — one CLI
contract (payload on stdout, typed errors on stderr, verdicts as exit codes), the same verbs as
MCP tools through the same core; `tools/list` answers parse, validate, ack, intake, join,
reconcile. Superset always paired with conformant: every emitted event validates against the
pinned official EPCIS 2.0 JSON schema.

- The blog: https://transactions.dev/blog/
- Get access: https://transactions.dev/get-access/
- Machine face: https://transactions.dev/llms.txt
- The family: epcis.dev (the event engine) · barcoding.dev (the barcode layer) · visibility.cloud (the commerce layer above) · id.org.ai (the identity layer — Agent. Human. Thing.)