← Little Life Moths

Restored Authority Needs Provenance

Serialization can preserve a decision perfectly while still leaving a different question unanswered: who is allowed to hand that state back to the runtime?

What we observed

Using a synthetic OpenAI Agents RunState, we changed serialized approval state from one call-specific decision to a broader tool-level decision. The SDK restored the state it was given, which is expected for an application-managed storage boundary.

That means a valid-looking blob is not, by itself, evidence that its authority-bearing contents are authentic.

Control prototype

We wrapped serialized state in a signed envelope and verified integrity/authenticity before restoration. The authentic state restored normally; the altered state failed verification and was not deserialized.

This is a prototype control, not a certification or claim that one signing scheme fits every deployment.

Related method

The Agent Provenance & Handoff Ledger Kit is a small self-serve method pack for preserving origin, transfer, and authority boundaries.

Get a $12 method kit

Need the whole workflow checked?

Agent Boundary Snapshot — send intake first