We produce it: your agent registry, their configuration, your policies, who may do what, what wakes them and what they then run, what they know and what was decided — in a documented format, in your keeping, with every gap written down. Then someone who did not produce it restores it into a clean workspace and reads it without MeetLoyd.
Twelve categories. Eight of them are required: a dossier missing one does not answer the question it exists to answer, whatever else it contains. Each one arrives with its format, where it landed, and how many items it holds — a category nobody can point at cannot be checked a year later.
Which agents exist, what each one is for, who owns it, its identity.
What each agent is: role, model, system and context prompts, settings.
The composition your agents sit in, and how it is organised.
Governance configuration, artifact governance, budgets and their limits.
Who may do what: tool grants, rights on resources, approval gates.
What wakes an agent and what it then runs: triggers, schedules, workflows, event subscriptions.
What the agents know: memories, team knowledge, the context graph, documents.
What was decided and by whom: the audit trail, authorisation decisions, approvals, escalations.
The mandate each agent was given, and the priorities it is working to now.
The know-how you wrote. Ours stays ours — see below.
The signed evidence records the platform already produced for you.
What is connected and how. Never the credentials — you re-issue those at the destination.
The exercise is the offer. The dossier is taken as delivered from your own destination, restored into a clean workspace with no access to the running platform, and opened with tooling that is not ours — by someone other than the engineer who produced it. The platform refuses that second write to the same person, so it is a rule rather than a promise.
What the dossier must satisfy, in your exit-plan owner's words, and who owns that obligation.
Every category, into your destination, each with its format, location and count.
A readable index, signed, written for someone with no access to MeetLoyd.
Restored into a clean workspace, read without us, counted category by category.
What came back, what did not, and every gap with an owner on your side and a date.
Every required category came back in full, each check passed, and the material was read outside MeetLoyd.
It came back with holes, or short, or only this platform could open it. Each gap becomes a finding with an owner.
A required category did not come back, or was never attempted. Your exit plan does not hold today, and you hear it that day.
The report contradicts itself — more items restored than exported, a restore with no check behind it. Nothing is concluded, and it is re-run.
A re-run is a new dossier and a new exercise, so every result names the material it actually tested.
The honest half of this page. A dossier is only worth something if the limits are in it, in numbers, rather than discovered by whoever inherits your estate.
Every one of those limits is recorded inside the dossier, with the number attached, and repeated in the report your exit-plan owner signs. Where the gap is ours to close, it is on our roadmap with your name against it.
The skills MeetLoyd wrote are our intellectual property, and the platform refuses to export their text — to you, and to our own agents. Your dossier carries your configuration and your content, and records ours as an exclusion with that reason. What you keep is a complete description of what your agents were and did; what you do not keep is our know-how, which you were licensing, not buying.
Credentials never travel in a dossier, in any form. It lists what is connected and how; you re-issue the keys at the destination. If a credential turns up inside exported material, the run stops and it is handled as a security matter rather than delivered.
Producing categories through the platform's own surfaces and recording what came out runs on its own from day one. It changes nothing and it is fully logged.
Your exit-plan owner approves the destination once; deliveries to that destination then run on their own, and a delivery anywhere else drops the whole action back to approval.
Supervised until the environment has been used without incident; a single restore outside the declared environment ends that immediately.
Never autonomous. The team drafts what the dossier shows; your compliance owner signs anything that reaches an auditor or a regulator.
Priced as a fixed fee per milestone — never on the verdict, which would pay us to be optimistic about it. Your own team can run the whole thing; the dossier stays yours whatever happens next. It pairs with Run Takeover when you are bringing work back in-house, and the evidence it produces lands beside the rest through the Regulatory Evidence Desk.