Capture Ingest Protocol

When Kevin pastes a URL, X post, GitHub repo, article, tool, or similar source and says "add it", the task is full graph integration, not a one-page note.

This protocol exists because Kevin's primary capture path is chat. He should not need to say "update every related page, route the tool, rebuild search, and log it." That is the default. Source: User, 2026-05-11; AGENTS.md Ingest

For batch, connector, or multi-source ingestion, Brain Source Fabric provides the substrate below this protocol: raw preservation, normalized source envelopes, typed evidence units, privacy-before-indexing, domain lenses, incorporation receipts, replay, queues, and freshness. This page still owns the human-facing “add it” behavior; the source fabric owns how evidence can safely and traceably influence the brain. Source: User request, 2026-07-15

Trigger Phrases

Treat these as capture ingest unless Kevin explicitly narrows scope:

"add it"
"add this to the wiki"
"remember this"
"capture this"
pasted URL/repo/post with an imperative
"this is important for X"

If Kevin asks only for a summary or opinion, answer the question first. If the result is durable, propose or perform the wiki update depending on repo access.

Non-Negotiables

Resolve the source. Read the source itself through the best available route.
Brain-first. Search existing pages before creating anything.
Choose the right shape. Use Wiki Brain Operating Model before creating pages.
File correctly. Use Filing Decision Tree and target directory README.
Bind stable owners. Touch every materially affected owner, but never create pages to satisfy a quota.
Cite every new fact. Use inline [Source: ...].
Update routing and versions. Tools, CLIs, MCPs, skills, SDKs, frameworks, and workflows must land in the relevant category router, SKILL-RESOLVER, Capability Routing Map, Active Stack (What to Actually Use), trigger evals, or config when behavior changes. Versionable tools also need a current release/package/API snapshot from primary sources.
Keep the graph bidirectional where it matters. Add entity timeline references for meaningful new mentions.
Rebuild machine surfaces. Run build-index, qmd update, and qmd embed; follow Generated Surface Contract when packs, registries, redirects, or stateful ledgers are affected.
Log the operation. Append wiki/log.md.
Codify repeats. If the capture class will recur, create or extend a skill/automation.
Leave proof. Write a validated source-signal review with an integrated, held, or blocked outcome; there is no terminal rejection state.

Standard Flow

Phase	Action	Output
Resolve	Fetch/read the source with agent-reach, browser, GitHub, curl, or primary docs	immutable revision, source facts, and provenance
Expand	Follow threads, replies, media, linked sites, repositories, and primary documentation	complete semantic unit and artifacts
Correlate	Match the source with Discord, X, prior saves, wiki owners, and related evidence	repeated evidence and contradictions
Search	`qmd search`, `qmd query`, `_index.md`, aliases	existing pages to update
Shape	Wiki Brain Operating Model	page, section, ledger, generated view, redirect, or no write
Classify	Filing Decision Tree	primary page location
Interrogate	ask whether each signal reinforces, refines, replaces, or contradicts an owner	explicit decision and reopening condition
Integrate	update primary and related stable owners	compiled truth + timeline entries
Route	update skill/tool/action surfaces	resolver rows, active-stack, trigger evals, version snapshots
Verify	`build-index`, qmd, targeted doctors	machine surfaces current
Record	review record, log entry, and absorb log if raw source	durable operation history and proof

Page Touch Expectations

A capture may affect:

primary entity page
related project/tool/concept page
comparison or stack page
active-stack or resolver
philosophy/design/style page when it changes Kevin's stance
capability routing, active stack, or Dedalus config mirror when behavior changes
entity pages for key people/projects/tools
wiki/log.md

One-owner capture is normal when the source is narrow. Rich captures should change every owner they genuinely challenge, while contextual observations can remain held without creating a page.

Raw vs Chat Captures

Source class	Extra step
Chat paste only	no absorb-log entry unless later stored under `raw/`
`raw/` source	call `markAbsorbed(rawPath, pageSlugs)` after compile
External page	cite URL and access date
X/social post	cite post URL, author, and date where available; use React Tweet / `::tweet` when the original post is source-critical
GitHub repo	cite repo URL and commit/date when exact code facts matter; check releases/tags before calling the tool current
Source-critical external link	use Wiki Artifact Embeds / `::artifact` when a rendered card is more useful than a bare link

Activation Gate

A captured skill/tool/loop is not done until it is usable:

Routed in SKILL-RESOLVER, the relevant category router (tools/README, design/README, skills/README, etc.), or Capability Routing Map.
Recommended in Active Stack (What to Actually Use) or explicitly marked reference-only.
Covered by config/trigger-evals.json if a trigger phrase should route to it.
Reflected in Capability Routing Map and any relevant harness projection if compact routing changes.
Version/release checked from primary sources when the capture changes a tool, SDK, CLI, framework, platform, or agent skill.
Validated by npm run routing-doctor and npm run trigger-eval when routing changed.

The wiki actively recommends. It does not merely store.

Anti-Patterns

Creating a lone page from a rich source.
Summarizing the source without synthesizing it into existing pages.
Missing citations because the source "obviously" says it.
Adding a tool page without a resolver route.
Updating compiled truth by appending stale layers.
Marking raw material absorbed before it is actually integrated.
Promoting a tool from X/social without checking the package registry, release tags, docs, changelog, or API version.

Timeline

2026-08-10 | Added expansion, cross-source correlation, stable-owner interrogation, and validated integrated/held/blocked review proof; removed page-count expectations and terminal discard semantics. Source: User request, 2026-08-10; Wiki Brain Operating Model
2026-07-15 | Linked chat capture to Brain Source Fabric so rich and recurring sources share a traceable evidence-to-disposition contract instead of relying on platform-specific summaries. Source: User request, 2026-07-15
2026-07-01 | Added generated-surface closeout to capture ingest so rich captures refresh packs, registries, redirects, qmd, and review ledgers when they affect them. Source: User request, 2026-07-01
2026-07-01 | Inserted the brain-shape step before filing so captures choose page/section/ledger/generated/redirect shape before Filing Decision Tree chooses a directory. Source: User request, 2026-07-01
2026-06-29 | Added mandatory version/release checks for tool, SDK, CLI, framework, platform, and skill captures so social release signals do not become stale tool claims. Source: User request, 2026-06-29
2026-06-18 | Expanded the capture protocol with triggers, standard phases, page-touch expectations, raw/chat distinction, activation gate, and anti-patterns. Source: User request, 2026-06-18; AGENTS.md
2026-06-25 | Clarified that tool/design discovery can live in category routers instead of a central SKILL-RESOLVER table, and routed source-critical X posts/links through React Tweet and Wiki Artifact Embeds. Source: User request, 2026-06-25
2026-05-11 | Protocol established: chat captures must integrate across wiki and agent docs, not single-file updates. Source: User, 2026-05-11

Source: User, 2026-05-11; AGENTS.md Ingest