Wiki

The Wiki () is the human-readable, browsable view of your published brain — every article grounded in citations. It is also a stewardship surface: from an article a Curator can propose to improve or prune the brain's knowledge, and those proposals flow through the governed Librarian loop before anything changes.

• Readers browse, search, deep-link, and ask the LLM to elaborate (Deepen).
• Curators additionally steward content — propose edits, flag concepts for removal, and promote a Deepen into durable article content.

Reading the wiki

• Table of contents grouped by category, with search.
• Provenance chips on each article tell you where the content came from — see Trust & provenance.
• Citations throughout — the Wiki reflects exactly what has been certified and published.

Deep links (shareable, durable)

Every article is addressable. Use Copy link on an article to get a shareable URL that is stamped with the durable concept id and the published version it came from — so a link you paste in a ticket keeps resolving even after the brain is re-published. Relationship chips and citations are all navigable from the article.

Deepen (grounded LLM synopsis)

Deepen via LLM writes a concise, encyclopedic synopsis of the concept using only the published knowledge base — cite-then-verified, with a confidence score and its source citations. It renders as Markdown and is transient (a reading aid) until a Curator promotes it into the article as an enrichment (below).

Content stewardship (Curator)

Curators only

The stewardship actions below require the Curator (or Admin) role. Readers see the wiki read-only. See Concepts & Roles.

From an article, a Curator has three actions — each creates a proposal that goes to the Librarian for review (it never edits the published wiki directly):

Action	What it proposes
Edit	A revised description for the concept.
Flag for removal	Prune the concept from the brain.
Propose as enrichment	Promote a grounded Deepen synopsis into the article as a durable, cited narrative — kept separate from the machine-extracted facts.

After you submit one, the article shows "pending review in librarian". The change is not live yet — it's queued.

The workflow: Wiki → Librarian → Publish

flowchart LR
    W[Wiki article] -->|Curator proposes<br/>edit / prune / enrich| P[Curation proposal]
    P --> Q[Librarian<br/>“Wiki proposals” queue]
    Q -->|Confirm| D[Applied to the draft<br/>audited]
    Q -->|Dismiss| X[Recorded, no change]
    D --> C{Certify<br/>safety gate}
    C -->|pass| PUB[Publish → new version]
    PUB --> W2[Wiki regenerates]

1. Propose — from the wiki (see above). The proposal captures the concept, the intended change, and — for an enrichment — the synopsis's citations, confidence, and version as provenance.
2. Review — the proposal appears in the Librarian's Wiki proposals panel. Any Curator or Admin can confirm it (including the person who proposed it); Confirm applies the change to the draft via the audited edit primitives, Dismiss records the decision with no effect. → Librarian › Wiki proposals
3. Certify & publish — as with any draft change, certifying runs the safety hard-gate; publishing cuts a new immutable version and regenerates the wiki. → Librarian › Certify & publish

When does the change show in the wiki?

Confirming a proposal changes the draft. The published wiki you browse updates only after a certify & publish. Until then the article shows its previously published content.

Pruning: resolving orphans

A Flag for removal that would strand neighbouring concepts (leave them with no remaining links) surfaces a needs-resolution notice on confirm — a curator resolves each orphan (keep / remove / reattach) before the prune commits, so removals never silently fragment the graph.

Trust & provenance

The wiki is designed so you can verify what you're reading:

• Provenance chips label each section's origin — Extracted from sources (deterministic, machine-extracted, no LLM) vs. AI-authored · human-approved (a promoted enrichment). The two are kept in separate fields so they stay independently verifiable.
• AI content is never unattended — a narrative only enters the corpus via a human-approved proposal that carries its citations and confidence.
• Everything is audited — every applied change writes to the append-only, hash-chained audit ledger (who, what, when, grounded on what), so the change history is tamper-evident.

How this relates to the Sentinel flow

The wiki stewardship loop is the human-initiated counterpart to Sentinel. Both are propose → Librarian → HITL — neither writes the corpus directly; both terminate at a Curator decision in the governed loop.

	Wiki stewardship	Sentinel
Trigger	A human, reading the published wiki	The system, sweeping already-ingested sources
Proposes	Edit / prune / enrich a concept	Flags: freshness / temporal / grounding drift
Lands in	Librarian Wiki proposals	Librarian review (from confirmed flags)
Curator decides	Confirm / dismiss	Confirm / dismiss
On confirm	Applies edit/prune/enrich to the draft	Routes the source into the ingest loop

Think of it as two doors into the same governed room: Sentinel watches the known sources for drift; the wiki lets a person act on what they see in the finalized artifact. Both funnel into the Librarian, get certified through the safety gate, and publish a new version — the same pipeline Scout uses when it targets a discovered source.

Roles at a glance

Role	In the wiki
Reader	Browse, search, deep-link, Deepen (read-only)
Curator	All of the above + propose edit / flag for removal / propose enrichment; confirm/dismiss proposals in the Librarian
Admin	Everything a Curator can do

When the wiki appears

The Wiki is generated when the brain is certified & published. Until then it shows an empty state prompting you to publish a version first — see the Librarian. Each publish (re)generates it to match the latest version.