Because evidence ages. A certificate proves how an agent behaved on a set of cases at one point in time. Even if nobody changes the agent, the world moves: new kinds of cases arrive, fraud patterns shift, rules change and models are quietly revised. A fixed lapse date forces renewal before the evidence drifts too far from reality.
Why not keep a certificate until something changes?
Because not every change is visible. Teams can track edits to the brief, new source versions and announced model updates. They cannot easily track:
- Changes in the case mix. Customers start asking about a new product or a new kind of problem the test set never covered.
- Changes in pressure. Fraudsters adapt; a scam script that did not exist at certification appears.
- Changes in rules. A regulator updates its expectations, or the organisation's own policy shifts in ways not yet reflected in the agent's sources.
- Silent model changes. Some providers adjust models behind a stable name.
- Slow drift. Small differences in inputs gradually move the agent's behaviour.
A certificate that only ended on detected change would last longest in exactly the cases where change was hardest to see. A fixed lapse closes that gap.
What are the two kinds of lapse?
| Kind | What triggers it | What it guards against |
|---|---|---|
| Time-based | The lapse date on the certificate | Undetected change; ageing evidence |
| Event-based | A failed run, or a change to model, sources, brief or tools | Known change that voids the evidence |
Both end the certificate. Event-based lapse is usually sudden and unplanned; time-based lapse is known in advance and can be prepared for. The consequence of either is explained in what certificate lapse means for AI agents.
Why should lapse drop the agent's depth automatically?
Because a certificate that lapses on paper while the agent keeps acting is no control at all. When a certificate ends, the depth it supported should end with it, enforced at the moment of action. The agent falls back to read-only for that capability until a renewal passes.
That makes lapse costly if it is not planned, which is the point. Teams that know depth will drop on a fixed date organise renewal ahead of it.
What does lapse change in how agents are run?
Quite a lot, in practical terms.
- A renewal calendar. Every certificate has a known lapse date. Renewals are scheduled ahead of them, with time to fix failures.
- Staggered dates. If every agent's certificate lapses the same week, the test and review teams are overwhelmed. Spread them.
- Fallback capacity. The team that owns each process knows it may need to pick up work if renewal fails.
- A growing case set. Each renewal is a chance to add cases from operation, especially ones the agent got wrong or held.
- A register. Every certificate, its lapse date and its status in one place, so nothing lapses by surprise.
Renewal is easier with a standard checklist; the certificate renewal checklist for AI agents covers what to confirm.
An illustrative example
Take a payments firm with twelve agent capabilities across four agents. When it began, all twelve were certified in the same fortnight, so all twelve lapsed in the same fortnight three months later.
The first renewal was strained. Two capabilities failed and dropped to read-only while the review team worked through the others, and operations had to pick up the work with little notice. For the next cycle, the firm staggered renewals across the quarter, started each one a few weeks ahead of its lapse date, and kept a list of who would cover each capability if it dropped. At the following renewal, one capability failed on a new type of merchant query. It dropped for two days, was fixed, and returned, with little disruption.
What should the certificate say about lapse?
The issue date, the lapse date, and the events that would end it early. The fields are in the AI agent certificate template. The broader scope of what a certificate covers is in what an AI agent certificate covers, and the concept itself in what an agent certificate means.
Where Pryme fits
In Pryme, every certificate lapses after 90 days, and a failed Attest run ends it the same day. Depth drops to 1 automatically on lapse, so authority never outlives its evidence. The reasoning is in what it means to certify an agent.
Questions people ask
Is a 90-day lapse too short for stable processes?
It feels short until the first undetected change. Renewal on a stable process is quick because the case set and method exist, and most of it can run automatically ahead of a named person's review.
Can a lapse date be extended?
Only by renewing on fresh evidence. Extending a date without new evidence turns the certificate into a formality.
What happens to actions taken just before lapse?
They were taken under a valid certificate and remain covered. The record should show which certificate was in force at each moment.