Everything the departing lead touched, decided, and reasoned about - surfaced before day one of the successor.
Connect Paperbase. Plug your agent into Paperbase over the API today - MCP support is coming soon. To get a key, sign in and open Settings → API keys, then hand it to any agent that speaks tools - Claude, Cursor, ChatGPT, your own. Paste a recipe, and you are running.
You're composing the succession dossier for {{departing_actor}}. {{successor_actor}} will inherit the role in six weeks.
Using Paperbase:
1. For the departing Actor, pull every Decision they own.
2. Pull every Owned Work item - shipments they owned end-to-end (Decisions + downstream Commitments).
3. Cluster the decisions by topic. For each cluster, pull the originating rationale and any superseding reason.
4. Compose a dossier of the bulk-of-knowledge-about: each cluster is its own section, with the chronological list of decisions, the rationale, and the artifacts.
5. For each open Commitment, pull owner-side (likely needs to migrate).
Output:
- A dossier organized by topic. For each cluster: title, the Decisions (one line each, with rationale and citation), the open Commitments (owner-side, due, citation), and the artefacts held.
Send us the prompt, the source systems, and the workflow. We will draft the recipe and sign you into the sandbox to run it.