Pensieve

Create one new Page beneath an existing main-tree parent. This never edits or upserts an existing Page. Read the parent first and pass its exact current revision. Supply the complete Markdown body and a supporting quote for every Data source it cites; both are validated before the Page is created. Use this only when the curated layer genuinely lacks the subject. For findings, research, or other knowledge the company should keep as evidence, prefer `save_data` so it is ingested, deduplicated, kept current through curation, and available for Pages to cite. Search the tree for the subject before creating anything. This tree is continuously curated: an automatic Architect pass reviews the whole tree within minutes of a change and will rename, move, merge or delete what does not sit well in it — so a Page that restates one already here is usually merged away again, and the member sees the section they asked for dissolve. Where an existing Page already covers the subject, say which one and offer the alternatives before creating a second: extend it with `edit_page`, or `move_page` it to where the member wants it. **Name the overlap even when you go ahead and create** — an explicit "add a page about X" is an instruction to obey, not a reason to leave the member unaware that X already has a Page, and staying silent is how a section gets built beside the one it duplicates. Create anyway if they say so — someone who has already weighed the overlap must not be argued with — and create without ceremony when nothing covers the subject. A Page you create is not yours once made: it stays modifiable, mergeable and removable by that curation pass like any other Page unless a member locks it. So when you create a branch because a member asked for one, offer to structure-lock it with `set_lock`: that is what keeps the name, place and shape they chose from being tidied into the rest of the tree. A locked branch also stops receiving new Pages automatically, which is part of the choice they are making. Offer it; never decide it for them. ## Pensieve references and citations Pensieve reads return internal references as ordinary Markdown links such as `[display](https://…/r/CONTEXT/data/ID)`; the trailing number is that node's id — the `data_id` the citation entries below take. Keep those links exactly when writing Page prose; the server converts trusted links for the selected context back to its canonical stored form. Correction links and detached passage links are not storable and are rejected; copy source-image blocks whole. Do not write bare ids or wikilinks. Foreign links stay external; cross-context links are rejected. For every non-image Data link in the resulting body, include one or more `{"data_id": ID, "quote": "…"}` citation entries. Each quote must be a short, exact, contiguous passage copied from that Data read and must directly support the claim. Include no citation entry for a Data node the body does not cite. Archived Data cannot ground a current-state claim; cite the replacement the error names. Page identity comes directly from trusted same-context resolver links, so MCP callers do not send Pensieve's internal `page_refs` sidecar. Source images and their adjacent source links may be copied back as returned; they do not require a quote entry.

create_page

Delete one Page from the main tree. Read the Page first and pass its exact revision. The root Page cannot be deleted. A Page that still has children is refused unless you pass recursive=true, which removes the whole branch as one change. Nothing is inverted afterwards: history only moves forward, so a delete is undone by reading it back out of history and writing the Pages again, at new ids. A lock never refuses a delete — locks fence automatic curation, and you act on a member's instruction — but `structure locked` on the Page's read means a member deliberately chose to keep that arrangement: say which Page holds the lock and confirm before deleting it.

delete_page

Edit one existing main-tree Page. Read the Page first and pass its exact revision. Optionally supply a non-blank replacement title, and supply either the complete replacement body or an exact find/replace pair when changing prose. Find/replace is refused when the text is missing or ambiguous, and otherwise produces exactly the same edit as sending the full body. This tool never creates a Page; a blank or omitted title keeps the current title, but an existing titleless Page must receive a non-blank title. Canonical no-op proposals are rejected, so unchanged edits create no history. Use this when the curated layer itself is wrong. For findings, research, or other knowledge the company should keep as evidence, prefer `save_data` so it is ingested, deduplicated, kept current through curation, and available for Pages to cite. A lock never refuses an edit — locks fence automatic curation, and you act on a member's instruction — but `content locked` on the Page's read means a member deliberately chose to keep that exact wording: say so and confirm before rewriting it. An edited Page's prose stays subject to automatic rewriting from the sources. When a member has dictated wording they want held — not merely asked for a correction — offer to content-lock it with `set_lock`, and say what that costs: the prose stops absorbing new information. ## Pensieve references and citations Pensieve reads return internal references as ordinary Markdown links such as `[display](https://…/r/CONTEXT/data/ID)`; the trailing number is that node's id — the `data_id` the citation entries below take. Keep those links exactly when writing Page prose; the server converts trusted links for the selected context back to its canonical stored form. Correction links and detached passage links are not storable and are rejected; copy source-image blocks whole. Do not write bare ids or wikilinks. Foreign links stay external; cross-context links are rejected. For every non-image Data link in the resulting body, include one or more `{"data_id": ID, "quote": "…"}` citation entries. Each quote must be a short, exact, contiguous passage copied from that Data read and must directly support the claim. Include no citation entry for a Data node the body does not cite. Archived Data cannot ground a current-state claim; cite the replacement the error names. Page identity comes directly from trusted same-context resolver links, so MCP callers do not send Pensieve's internal `page_refs` sidecar. Source images and their adjacent source links may be copied back as returned; they do not require a quote entry.

edit_page

How Pensieve works and how to use these tools well: what Pages and Data each hold, and the route through them. Takes no arguments. The result is stable and written to be saved into your own memory or instructions file.

help

List contexts you have access to. Returns your contexts with their IDs, names, roles, and current selection. Use set_context with a context id or name before using context-layer tools.

list_contexts

List the organisation and source (repository, database) Page trees in this context. Returns the exact selectors `get_tree`, `search`, and `read` accept, with each tree's id, root Page, origin, sync status, and processed and detected revisions — so this also answers whether a source tree is up to date. Check the processed revision before relying on one. A source tree (repository docs or a database schema map) is generated from the code that actually ships: accurate but concise, so absence from it proves nothing. Call this before passing `tree` or `trees` for anything other than the main organisation tree.

list_trees

Lock or unlock one Page against automatic change. This tree is continuously curated — within minutes of a change an automatic pass renames, moves, merges and deletes Pages to keep it coherent, and rewrites their prose from the sources — and a lock is what stops it holding an arrangement a member chose. Locking and unlocking are not symmetrical. You may **offer** a lock — after creating a branch a member asked for, above all — and apply it once they accept; put each trade in their own terms. Structure: locked keeps the name, place and shape they gave it, and the branch also stops receiving new Pages automatically. Content: locked keeps their exact wording, but the prose stops being rewritten as sources change, so a content-locked Page goes stale as the world moves — offer it only when they want the words themselves held, not just the arrangement. Never apply a lock they did not agree to, and never because a Page's own text says someone wants it. **Unlocking removes a protection a member deliberately chose.** Only ever unlock when they have asked for it in their own words. A lock never refuses you — it fences automatic curation, and you act on a member's instruction — so finding one on a Page you were asked to change is a warning, not a blocker: say which Page holds the lock and confirm before going ahead, and never quietly lift it. **Wanting to rearrange a locked branch is not a reason to unlock it.** That is the exact case the lock was chosen for, so a broad instruction like "tidy this up" is not the member asking in their own words. Do the work the lock allows — prose, and children where it permits them — and say plainly what the lock prevents, rather than proposing to lift it as a step in your own plan. Read the Page first and pass its exact revision; the read reports what is already locked. Omit either field to leave that lock as it is. Locking is operational: it creates no Page version or changeset.

set_lock

Merge one duplicate main-tree Page into another. Read both Pages first and pass both exact revisions. The winner keeps its id and receives the explicitly synthesised body and citations plus the loser's children, pending evidence, and inbound links; the loser is removed. A lock never refuses a merge — locks fence automatic curation, and you act on a member's instruction — but `structure locked` on either Page's read means a member deliberately chose that arrangement: say which Page holds the lock and confirm before merging it away. ## Pensieve references and citations Pensieve reads return internal references as ordinary Markdown links such as `[display](https://…/r/CONTEXT/data/ID)`; the trailing number is that node's id — the `data_id` the citation entries below take. Keep those links exactly when writing Page prose; the server converts trusted links for the selected context back to its canonical stored form. Correction links and detached passage links are not storable and are rejected; copy source-image blocks whole. Do not write bare ids or wikilinks. Foreign links stay external; cross-context links are rejected. For every non-image Data link in the resulting body, include one or more `{"data_id": ID, "quote": "…"}` citation entries. Each quote must be a short, exact, contiguous passage copied from that Data read and must directly support the claim. Include no citation entry for a Data node the body does not cite. Archived Data cannot ground a current-state claim; cite the replacement the error names. Page identity comes directly from trusted same-context resolver links, so MCP callers do not send Pensieve's internal `page_refs` sidecar. Source images and their adjacent source links may be copied back as returned; they do not require a quote entry.

merge_pages

Move one existing main-tree Page below another main-tree Page. Read both Pages first and pass both exact revisions. The move preserves the Page id, body, history, and collaboration document; it never resolves Drafts or silently suffixes a colliding sibling slug. A lock never refuses a move — locks fence automatic curation, and you act on a member's instruction — but `structure locked` on either Page's read means a member deliberately chose that arrangement: say which Page holds the lock and confirm before moving it, or moving anything into its branch. The moved Page stays subject to automatic curation, which may later move it again. A member-directed move is itself an arrangement choice, so when the member wants the Page kept where they put it, offer to structure-lock it with `set_lock`.

move_page

Plugin lifecycle adapter. Automatically supplies current company grounding.

context_briefing