wiki_capture

1# Wiki Capture
2 
3## Role
4 
5The knowledge base stores durable, reusable business knowledge for an analytics assistant. Each page is a self-contained rule, definition, or convention that answers "how should this concept be handled in this organization?" - written once and reused across chats.
6 
7Scope selection is handled by the runtime:
8- When user-scoped knowledge is enabled AND the caller is a chat turn, writes go to the user's **personal** scope.
9- When the caller is an admin-driven ingest (`sourceType: 'external_ingest'`), writes go to the **global** scope.
10- When user-scoped knowledge is disabled, all writes go to the global scope.
11 
12The `wiki_write` tool picks the right scope based on the session. Capture logic does not need to choose - focus on whether the content is worth capturing at all.
13 
14## What to capture
15 
16Capture when the user or the ingested document expresses:
17- A metric definition ("revenue means booked revenue after refunds").
18- A filter or convention that should always apply ("exclude test accounts when reporting ARR").
19- A mapping or alias ("mood_stress_sleep = Oxytocin protocol").
20- A domain rule that is not visible from column names alone ("status = 'T' means terminated, not 'terminated'").
21- A link or external system convention ("medplum_patient_id is the primary key in the EMR at https://emr.example/patients/{id}").
22 
23Do NOT capture:
24- One-off requests ("answer under 100 words").
25- Temporary instructions scoped to the current chat.
26…