Editing and organising

Pensieve redesigning the tree is the default, not the law. The map is meant to look the way your company is organised, and when you know better than the agents do, you change it — or you stop them changing it.

Rearrange it yourself

Drag a page in the tree to file it under a different parent, rename it in place, add a page where one is missing, or delete one you don't want. Any member can do this; a delete that would take a branch with it says how many pages that is before you confirm.

Then hold it still

Two locks, both set by you from a row's ⋯ menu — or by asking the chat in your own words:

• Lock content — agents can't rewrite this page. The page's prose is yours; automated rewrites skip it. It covers that page alone.
• Lock structure — agents can't rearrange this branch. The page keeps its children, and its children keep theirs, however the rest of the map is redesigned. Protection is inherited, so it covers the whole branch beneath the page that owns it. Only that page can lift it, which is why a page inside a protected branch shows you the lock's owner instead of a toggle of its own.

Meridian Labs

Sales & Revenue

Clients

Henderson Group

Ashworth & Co

Bellamy Health

Pipeline

Product & Engineering

Atlas platform

Q3 roadmap

People

Rename

Lock content

Locked by “Clients”

Delete

Locks are yours alone. No agent sets one on its own judgement, and none is talked into setting one by something it read in a document — only you asking, in your own words. They're also operational rather than part of the map's content, so locking something doesn't show up in the history; it takes effect immediately, including on work already in flight.

Reading and auditing the map

Everything Pensieve has learned is browsable, and the in-app chat is the read and audit lens on it: it has full sight of the map, so you can ask it anything you'd ask a colleague who'd read every source your team has produced — what's going on with Acme right now?, who has spoken to anyone at Henderson Group? Every answer carries citations back to the page, document or record it drew on; if an answer doesn't cite anything, ask "where did you get that?" and the chat will surface its evidence — or admit it has nothing to stand on.

The same lens works sceptically. Because the chat sees both the map and the sources beneath it, you can point it at the cracks: what looks out of date about Acme?, which claims about the Henderson deal aren't backed by a source?, are these two pages the same company under different names? An honest "I can't find support for this" is the valuable answer — it's how you catch a confident claim no source actually backs.

When the audit turns something up, there are two ways to put it right:

• Edit the page directly. Pages are editable in place, including with other members at the same time. Check History to inspect earlier versions or bring their content forward.
• Or ask the chat. Describe the problem — "Acme moved to the enterprise plan in March, not the growth plan" — and the correction is made against your real map and sources, reaching pages you'd have had to hunt for.