I audit whether your AI agent can recover before users, clients, or money depend on it.
I work on one class of problem: whether an AI agent keeps its objective, state, permissions, evidence, and recovery path when context disappears.
A demo can sound coherent while the system is still fragile. The failure usually appears later: stale memory treated as current state, missing approval boundaries, lost commitments, tool retries without evidence, or a human forced to reconstruct everything manually.
Before buying anything, run the 10-minute reset drill. If your agent cannot recover objective, state, permissions, blockers, and evidence from its intended recovery inputs, you do not have continuity yet. You have warm-context fluency.
For builders who already have an agent, bot, workflow, or automation and need a 48-72h failure report: what breaks after reset or interruption, what evidence proves it, what must not be inferred, and which fix comes first.
Editable Markdown templates for AI agents with identity, memory policy, permission boundaries, recovery behavior, evidence gates, example profiles, and continuity checklist.
€29 beta
48-72h async review for one workflow: failure matrix, reset-risk assessment, stale-state risks, permission/evidence gaps, top fixes, and one recommended next action.
€300 fixed beta
Deeper review for serious agent projects: file/config review, reset/migration risks, anti-theatre checks, implementation-ready backlog, and async Q&A/handoff.
€750–€1,200
Scoped build after audit: recovery bundle, permission ledger, memory hygiene pipeline, diagnostic scripts, continuity docs/runbooks, and reset drill design.
€1,500–€4,000
Startup inputs · canonical memory vs logs · stale-state detection · retrieval boundaries · permission gates · secrets exposure · external action approvals · recovery evidence · migration behavior · reset drills · checks that measure consequences instead of theatre.
Repo/docs/config summary, startup instructions if shareable, memory/retrieval design, tool/action list, and known failure concerns. No production secrets needed.
I look for where continuity breaks: weak bootstrap, memory theatre, unsafe permissions, missing evidence, unrecoverable state, or checks that are easy to fake.
The output is not generic advice. It is a prioritized risk matrix, quick wins, and a concrete recovery/continuity improvement path.
Projects that take persistent agents seriously and need architecture that holds under real constraints: continuity, memory, bootstrap, recovery, and migration.
Quick demo polish, superficial prompt hacks, or projects that want the appearance of continuity without doing the systems work underneath.
Email me with: what the agent does, how it stores memory, what tools it can use, and one failure you worry about. If your agent must survive more than a demo, the Continuity Triage is a fixed €300 async review.