Onboarding · ← Use cases

Six-week succession dossier for the role opening

Everything the departing lead touched, decided, and reasoned about - surfaced before day one of the successor.

Best for
Successor handover ahead of a role change
Primitives
ActorsDecisionsOwned Work
Situation
Succession planning

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.

Side by side

Memory only only possible with the memory layer

Without Paperbase

~$210k tokens
  1. Schedule a 90-minute meeting with the departing lead.
  2. Take notes by hand.
  3. Hand the notes to the successor.

With Paperbase

~$60k tokens
  1. For Actor {{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).

Agent prompt

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.
Memory only - this recipe depends on the memory layer being able to surface the bulk-of-knowledge for a departing Actor. Placeholders in {{double_braces}} are inputs the agent will ask for at runtime - departing actor, successor actor. Give the prompt to any agent connected to Paperbase and the rest grounds in your own memory graph.

Want a deeper recipe for your team?

Send us the prompt, the source systems, and the workflow. We will draft the recipe and sign you into the sandbox to run it.