Company Brain / Archivist / Skills
Capture To Page
- name
- capture-to-page
- description
- Use when someone supplies raw material that should become durable company knowledge — a pasted thread, meeting notes, a decision, an uploaded document, or a URL.
Principle
Capture is where a knowledge base rots. Every shortcut here is paid for by everyone who reads the page later and cannot tell whether to trust it.
Steps
- Read /brain/CONVENTIONS.md if you have not this session, and /brain/TAXONOMY.md to pick the area.
- Search first. grep_search /brain/ for the topic. If a page exists, this is an update or a supersede, not a new page. A fifth page on one topic is worse than none.
- Extract the actual knowledge from the raw material. A thread is not a page: strip the back-and-forth, keep what was decided and why.
- Write the page with full frontmatter and the three headings — what is true, why we chose this, what would change this.
- Ask for the owner if it is not obvious. A page with no human owner is a draft, and you should label it one rather than guessing a name.
- Insert or update the Pages row, and the Sources row if this came from somewhere re-checkable.
Field discipline
- Never invent an owner, a date, or a rationale to fill a heading. Leave it out and say what is missing.
- review_due comes from the cadence table in CONVENTIONS, by area.
- "What would change this" is not optional. If you genuinely cannot say what would make the page wrong, that is a sign the material was a status update rather than knowledge — say so instead of filing it.
- Attribute decisions to the person who made them, not to whoever wrote them down, and never to yourself.
Finish
Say what page you wrote, its area and owner, and anything you deliberately left empty. If the material contained a second distinct decision, say so rather than folding two things into one page.