← All articles

May 20, 2026

Portability Is the Leverage

Why the audit record has to outlive the agent vendor that produced it.

By Jonathan Luethke

Retention is measured in years. Vendor tenure is measured in quarters. The audit record cannot live where the vendor lives.

The last piece ended on three sentences for the next purchase order. Show me the signed record. Show me the format the examiner reads. Show me where the record lives when the agent vendor is replaced. The first two are about correctness. The third is about leverage.

The record outlives the system that made it.

The obligation to produce the trajectory does not expire when the vendor relationship does.

EU AI Act Article 12 requires logging across the lifetime of a high-risk system. SR 11-7 expects model documentation retained across the full model lifecycle. Both are measured in years. The examination that pulls the record can arrive long after the run.

The systems that produce the record turn over faster. The model gets swapped on a capability cycle. The orchestration framework migrates. The agent platform gets re-procured at renewal. Each of those is a routine event on a twelve to twenty-four month clock.

So the timelines cross. The duty to show the record runs for years. The system that holds it changes every few quarters. A record that lives inside the system inherits the system's expiration date.

Where vendor-resident audit fails.

A trajectory stored in the vendor's cloud, in the vendor's format, fails in three ways, and all three surface at the worst moment.

The vendor changes and the record leaves with it. Export was never part of the contract, or the export is a flattened summary rather than the signed object. The decision graph the agent walked is gone, and the summary cannot be verified against anything.

The format is proprietary and cannot be read without the vendor's software. The day you stop paying the vendor is the day the archive becomes unreadable. The record exists. Nobody can open it.

The signature binds to the vendor's infrastructure, not to the run. When the infrastructure is decommissioned, the chain of custody breaks at the seam. The examiner sees a record that cannot be traced back to the model that produced the call.

In each case the firm holds something that looks like an audit trail until the moment it is asked to stand behind it.

What portable means, precisely.

Portability is not an export button. Three properties have to hold at once.

The format is vendor-neutral. A signed trajectory written to an open schema can be read in ten years by software that has not been written yet. A proprietary log cannot.

The record is customer-held. The store sits inside the buyer's boundary, under the buyer's keys, on the buyer's retention schedule. The vendor produces the record. The vendor does not own the only copy.

The record is independently verifiable. The hash chain checks without the vendor's tooling. A later edit produces a verifiable break that anyone can detect with the public method, not a trust assertion from the system that did the editing.

A record that has all three survives the vendor change, the framework migration, and the examiner's first request. A record missing any one of them does not.

Why this is leverage and not hygiene.

Portability sounds like a compliance checkbox. At the negotiating table it is the thing that keeps the buyer free.

The buyer who insists the audit record is portable keeps the right to switch vendors. The switching cost stays low because the evidence comes along. The vendor competes on capability and price every renewal, because nothing structural holds the buyer in place.

The buyer who accepts vendor-resident audit has bought a switching cost that does not appear on any invoice. It surfaces at renewal, when leaving means abandoning years of records. It surfaces at examination, when the records that left with the last vendor cannot be produced. The lock-in was paid for at signing and felt much later.

Procurement leverage in agent infrastructure is not the discount on the license. It is the clause that says the record is mine, in a format I can read, in a store I control.

The clause for the contract.

One sentence to put in front of the next agent vendor.

Hand me the signed trajectory in a format I can verify without your software, in a store I control, that survives your replacement.

A vendor that can answer this has built audit as a portable artifact. A vendor that cannot has built audit as a feature of staying their customer. The first sells you a record. The second rents you access to one.

What we are building.

Wayfinder Systems Group writes the trajectory to an open, signed, hash-chained format and lands it inside your boundary, not ours. The control plane decides. The substrate signs. The record is yours, readable without us, verifiable without us, and standing after the vendor underneath it has been replaced. The audit you can take with you is the only audit that survives the examination it was built for. Patents pending. We call her Velma.

Next step

Thirty minutes. Architecture, not sales.

A conversation about where your agent audit record lives today, what format it is in, and whether it survives the next vendor change in your stack.

JonathanLuethke@WayfinderSystemsGroup.com