Curating a memory

Introduction

Brain compiles pages on its own, and an admin of the memory has the last word. Everything below is admin-only, appears in the audit log, and can be undone from there. The same actions exist as routes.

Review

Review has one tab per kind of decision:

Tab	What waits there
Labels	One item per document, listing the passages Brain wants you to label: it proposes labels, it thinks the label of the document is wrong for that part, or it is not sure.
Conflicting facts	Two sources that disagree.
Proposed pages	Answers proposed as new pages.
Possible duplicates	Two pages that may be the same entity.
Empty pages	Pages left with no facts, for example after a source was deleted.
Health	A scan of the whole memory: likely duplicates, pages nothing links to, empty pages and retired facts a conflict still quotes.

Labels: who decides

A label sits on a passage, the piece of the original text a fact cites, not on the document as a whole. A document that mixes Sales and HR parts therefore needs no decision about “its” label: each role reads its parts. A fact is readable when every passage it cites is, and a link or a conflict is read through the facts and passages it came from. Brain at a glance shows the model.

Each label has a meaning, a sentence of up to 500 characters you write on the Labels screen when you create the label or edit it later. Brain reads the meaning to decide which passages get the label, so “Budgets, payroll and headcount costs” works better than “Finance”. A label with no meaning still works, but Brain has only its name to go on.

Brain classifies a document before it compiles it: one call reads every passage and answers, per passage, which labels should read it. A passage that mixes topics is cut at sentence boundaries and judged again in smaller pieces; one that is still mixed counts as unsure. If you set labels on the document yourself, or a labeling rule did, its passages take those labels first, and Brain only narrows them or asks.

In the memory’s Settings, Who decides labels takes one of two values:

Choice	What happens
Brain decides, and asks when unsure	Brain applies the labels it is sure of and keeps an Undo in the audit log. It asks in Review when it is not sure, or when the label of the document looks wrong for a part of it. This is the default.
Always ask me	Nothing is applied by Brain. A document without labels stays unlabelled, a labelled document keeps its labels, and Review proposes the rest.

The audit log has one entry per document for what Brain applied, for example “Brain labelled passages of “Pricing update 2026.pdf”: Sales, Globex”. Undo clears those labels and sends the document to Review.

Review: one item per document

An item shows the document and, for each passage that waits, its locator, the start of its text, the labels Brain proposes and why:

Reason	What it means
Brain proposes	Brain has labels for the passage and, in “Always ask me”, waits for you.
The document’s label looks wrong for this part	The document has labels, but Brain thinks the passage should reach other roles. The passage stays unlabelled, so only admins read it, until you decide.
Brain is not sure	Brain could not tell who should read it. The passage stays unlabelled.

Accept all gives every passage the proposed labels, and Reject all gives each the labels of the document, or none. To decide one passage, use Accept, Reject or Pick labels on its row. A passage you label this way is never overwritten by a later labelling.

Edit a passage, relabel

In the text version of a source, an admin opens Passages and who can read them and edits the labels of any passage in place. Relabel on a source, or Relabel every document in the memory’s Settings, runs the classification again, for example after a new label or a changed meaning. Passages you labelled are skipped, and nothing is compiled again, because facts take their readers from the passages they cite.

Note

A source that is open to a role but has parts restricted to other roles reads differently for each reader. In the text version of the source, the parts a reader may not see appear as a muted Restricted part block under a line saying parts are hidden, and search and Ask skip those passages. Brain keeps no copy of the original file, so there is nothing else to download.

Merge or keep apart

A Possible duplicate shows both pages. Merge into… moves the facts, citations and links of one page to the other, keeps every name as an alias and deletes the merged page; its old id keeps answering the target. Keep apart records that the two are different, and Brain does not raise the pair again.

Tip

Merging keeps each fact’s labels and sources unchanged, so nobody gains access to anything by a merge. Undo restores both pages.

Edit, rename, lock

On a page in Explore, an admin can:

• Rename it. The old title stays an alias.
• Add a fact by hand, choosing its labels and the pages it mentions. A human fact is marked as such. A link between two pages exists while a live fact on one of them mentions the other.
• Edit a fact’s text.
• Split… chosen facts into an existing or a new page.
• Lock page or lock a single fact. A compile never rewrites a locked page or fact.

History

Show history adds the retired facts to a page, each with the date it stopped holding and why, so you can see what a newer source replaced.

Delete or erase a source

Deleting a source retires the facts only it supported and rebuilds the rest from the sources that remain. Erase… removes the source and everything derived from it, history and revisions included, and cannot be undone.

Next steps

• HTTP API for the same actions as routes.