Metadata, Not the Archive

The first question serious operators ask about a connective platform is the right one: "So you're going to hold all our data?" The answer is no — and understanding why is the fastest way to understand what Veritas by ATG really does.

The connective layer, not the archive

Every party in a complex transaction already has a system of record. The carrier has its TMS, the shipper has its ERP, the clinic has its EHR, the contractor has its project software. Those systems hold the authoritative version of what happened — the signed contract, the full document, the ledger entry. That's the archive, and it belongs to whoever owns it.

Veritas doesn't try to replace any of that. It moves the facts about those records between the parties who need them, while each side keeps the records themselves. The archive stays home. Only the metadata travels.

So what is "metadata," concretely?

It's less abstract than the word suggests. In a multi-party operation, most of the friction isn't about the documents themselves — it's about knowing the current state of things. Metadata is that state, structured so a machine can act on it instead of a person having to ask:

• Status — where something is in its lifecycle. Booked, in transit, delivered, approved, denied, closed. The one-word answer everyone keeps calling to get.
• Milestones — the timestamped events that move status forward. Picked up at 9:14, authorization received, inspection passed, funds cleared. Each one a small, verifiable fact.
• Document references — a pointer that says this document exists, here's its type, here's its version, and it's ready. The proof-of-delivery has been signed; the claim packet is complete. Not the file's contents dumped into a shared pool — a reference the owner controls.
• Structured identifiers — the shared keys that let two systems agree they're talking about the same shipment, case, or order without merging their databases.

That's the payload. It's small, it's specific, and it's exactly what the other party needs to take the next action.

Why the distinction matters

Keeping the archive where it lives isn't a technical shortcut — it's the whole point. Three things follow from it:

Nobody hands their books to a counterparty. The reason cross-company consolidation almost never happens is that no one wants their commercial data sitting inside software a competitor or customer controls. A metadata-only layer sidesteps that entirely. Your records never leave your system; only the facts you choose to share cross the wire.

The record of authority stays clean. When there's one archive per party and a layer that moves facts between them, there's no second "master copy" to drift out of sync. Veritas doesn't become a competing source of truth — it becomes the path along which each party's truth reaches the others.

The surface you have to trust is smaller. Moving structured facts is a far lighter security and governance problem than warehousing everyone's raw documents. Less sits in the middle, so less can leak, and each party keeps control of the sensitive material.

The same pattern, across industries

This is why the model isn't specific to any one vertical. A logistics broker needs the shipper and carrier to share status and delivery milestones. A referral network needs the specialist, primary practice, and payer to share authorization state. A general contractor needs subs and suppliers to share schedule and change-order status. Different paperwork, identical shape: each party keeps its archive, and a connective layer keeps the facts moving so no one is waiting on a phone call to learn what's already true.

The mental model to keep

A payments network lets a buyer and seller transact without merging their ledgers — it moves the authorization and settlement facts, not the banks' internal books. Veritas applies that same discipline to operations: it moves status, milestones, and document references between parties, and leaves every archive exactly where it belongs. Metadata, not the archive. That's the line, and holding it is what makes a shared layer something independent companies can actually agree to use.