Understand
How it works
The chain has four stages. Material moves through three of them and is judged in one, and almost every misunderstanding about this system is a confusion about which is which.
- Sources conversations, meetings, commits, issues
- Archives four dot-folders in the vault
- Processing core-skills 1.89.4 in a session
- Knowledge notes, tasks, insights, a recap
The stages
Sources are where work leaves a trace: what was said in writing, what shipped, what is planned, what was said in a room. Archives are four folders in the vault that hold those traces, deliberately shaped alike so that something reading one can read all of them.
Processing is a session: skills running against the vault with the contract and the project's own configuration in context. Knowledge is what comes out — notes with decisions, owned tasks, a recap, insights that survive the week they were written in.
Two principles that explain most of the design
Metadata from systems, content from conversations. From code hosting and issue trackers, only the traces are taken — never the code, never an issue's description, never a comment thread. From chats and meetings, what was actually said is taken, because that is the material. The difference is not inconsistency: an issue already has a home, and a conversation does not.
Nothing is fetched that was not declared. A folder's own configuration says which chats, repositories and boards it touches. The tools never write that block; a person does. Nothing is archived because it happened to be reachable.
Read next
From ecosystem.yaml, contract 41 · core-skills 1.89.4 · read at build 2026-10-08