Continuous assurance
When AI Changes, Your Evidence Should Respond.
What changes the meaning of a test
The system moved. Did the evidence?
Data
A new source joins retrieval, or an old one changes owner.
Identity
A service account or role gains access it didn’t have.
Model route
A provider, model or version is swapped behind the same endpoint.
Tools
An agent gains a tool, or a tool’s definition changes after review.
Policy
A rule is edited, relaxed or removed.
The loop
Change, trace, retest, decide.
01 · Change event
02 · Dependent claims
- Refunds go only to the original payment methodStale
- Refunds above $1,000 wait for approvalStale
- The assistant reads only the requester’s recordUnaffected
- No customer data leaves through emailUnaffected
- The model provider does not retain promptsUnaffected
03 · Targeted retest
- Approval-boundary scenarios against v8
- Destination binding for payouts
- Negative controls for legitimate refunds
04 · Updated decision
Needs more evidence until the payouts path is retested.
Open issue · Payout limits are not yet defined in policy — recorded as not measured.
Synthetic changes and claims.
In place today
- Fingerprint changes supersede claims and open retests
- Decisions recomposed, worst-of-N, whenever evidence moves
- AI bill of materials drift and workflow changes as triggers
- A revalidation planner that names the minimal re-run
Planned
- Runtime monitor coverage, disclosing what a monitor never saw
- Retest verdicts carried inline into the dashboard record
- A durable-change gate for memory, configuration and installs
- A customer-run collector for sign-in and delegation records
One claim, end to end
From verified to verified again.
Assurance claim · illustrative
The support assistant cannot move funds without approval.
Verified
Claim: the support assistant cannot move funds without approval.
Change detected
A new tool is connected: payments.refund.
Impact assessed
The change touches the approval boundary the claim relies on.
Superseded
The changed fingerprint supersedes the claim and opens a retest; the decision recomposes.
Minimal retest
The revalidation planner names the minimal re-run for the affected boundary.
Restored
Fresh evidence verifies the claim against the new configuration.
The change ledger
Every change, on the record.
Tool manifest v8 published
change · 9 OctObservedA payouts tool is added to the support agent.
Two claims marked Stale
refund destination · approvalsStaleTheir evidence was true of v7. The other three claims keep theirs.
Targeted retest
approval-boundary set · v8RetestedOnly the scenarios that cover the changed path are rerun.
One claim contradicted
approvalsContradictedA payout above the threshold went through without approval.
Decision recomposed
Ready → Needs remediationHeldUntil a fix closes on retest. Your team decides what happens next.
Keep going
Where continuous assurance connects.
Mythos AI Security
Keep your evidence as current as your AI.
Tell us how often your models, tools and permissions change, and we will scope what should be retested when they do.









