When a loss turns on what an agent did…
Whose record do you read?
Today it is usually the log kept by the party whose agent caused the loss. The Ancilla flight recorder is being built so that a record can be checked against signed checkpoints held outside that party's control, with every limit stated on the packet itself.
Why this matters at claims time.
Generative-AI exclusions and affirmative AI cover both make "did the AI cause this loss?" a question someone has to answer with evidence. Under an exclusion the insurer has to show it; under an affirmative policy the insured has to.
For underwriters
Applications ask about governance documents and testing before cover. They don't usually see what an agent did in operation. A packet is a record from operation, with its gaps declared.
For claims professionals
Reconstructing an agent incident usually means piecing together the operator's logs, the agent's own account and whatever the target system kept. A packet keeps those sources apart and says where they disagree.
For brokers
Your clients are being asked how they control the agents they deploy, and documents describe intent rather than what happened. A packet is a record of what happened, which a client could bring to a submission.
Who holds what
Our current position: the company deploying the agent owns the record. Forerunner Labs holds signed, dated checkpoints of it, which the policyholder may also keep. An insurer may request the packet and the checkpoints when it needs them.
Ancilla separates custody of the content from custody of the commitments used to check it. Forerunner Labs is not sent the record's contents, holds no credential and holds no decision key.
What you can check yourself
That the packet matches checkpoints you fetched directly from the checkpoint service, not from the policyholder
That the signed decisions verify under the policyholder's decision key
That the target system's ledger, where there is one, agrees with what the gateway forwarded
The verifier runs wherever the packet is, without Forerunner Labs in the loop. A packet ending at an earlier, checkpointed export is reported as passing as of that date and marked as an earlier export, never as a clean pass.