Capture Ingest Workflow

End-to-end path when Kevin pastes a URL, tweet, or repo and says "add it": not one file, but full graph integration.

Chat capture follows Capture Ingest Protocol. This workflow is the operator checklist. Source: Capture Ingest Protocol, 2026-05-31

Trigger

Use this workflow when Kevin pastes a URL, repo, tweet/post, article, paper, transcript, note, or screenshot and asks to add, remember, absorb, summarize into the wiki, or keep it for later.

Do not treat chat capture as lower quality than a raw file. The capture is a source. The wiki write must still update the graph around it.

Inputs

The capture itself, fetched from the primary source when possible.
Existing wiki context from qmd search and wiki/_index.md.
Shape decision from Wiki Brain Operating Model.
Filing decision from wiki/RESOLVER.md.
Any relevant skill, especially source-specific skills such as Cloud, Data, and Service Skills, Security and Review Skills, Cloud, Data, and Service Skills, or domain skills.

Steps

Resolve : Fetch capture via Security and Review Skills; read primary source
Search : qmd search, aliases, _index.md, and nearby pages
Shape : Wiki Brain Operating Model decides page, section, ledger, generated view, redirect, or no write
Place : wiki/RESOLVER.md and folder README choose location
Extend graph : Primary page plus related updates, wikilinks, entity pages
Route tools : Update Capability Routing Map, Skill Resolver, Active Stack (What to Actually Use), or harness projections when behavior changes
Index : Build Index Workflow, QMD Embed Workflow, append wiki/log.md
Codify : If recurring, Skill Sync Workflow or new automation per No One-Off Work Rule

Quality bar

Every fact: [Source: ...]. Every entity mention: back-link. Compiled truth rewritten; timeline append-only.

Minimum acceptable ingest:

The primary source was actually read.
Existing pages were searched before creating a new one.
The main page has current compiled truth, not just a source summary.
Related pages that materially changed were updated.
New entities have aliases and tier where appropriate.
Claims that change agent behavior update the relevant skill, resolver, or meta page.
wiki/_index.md, _backlinks.json, qmd, and wiki/log.md reflect the change.

Failure modes

One-file ingest: source affects a tool, project, person, or philosophy but only one page changes. Fix by following backlinks and related pages.
Summary without synthesis: page repeats the source in order. Fix by organizing by theme and updating the compiled truth.
No source trail: claims lack source brackets. Fix before indexing.
Resolver skipped: duplicate entity or wrong folder created. Fix by merging or moving before qmd embed.
No codification: repeated workflow learned but no skill or automation updated. Fix through Skill Sync Workflow.

Run Contract

This workflow follows Workflow Run Contract: name the sources, write output or no-op proof, promote only durable facts, update state only when the run really completed, refresh generated surfaces when durable pages or skills change, and log user-visible work.

Timeline

2026-07-01 | Added the brain-shape step before resolver filing and expanded route-tool closeout to capability map, active stack, and harness projections. Source: User request, 2026-07-01
2026-06-18 | Expanded workflow into a full operator protocol: trigger, inputs, minimum ingest bar, failure modes, and explicit no-one-file-ingest enforcement. Source: User request, 2026-06-18
2026-05-31 | Workflow page distilled from capture-ingest-protocol for workflow category. Source: Capture Ingest Protocol, 2026-05-31

Source: User request, 2026-07-01