wiki-itlisted

# Wiki-it The pipeline is a compiler: `Sources -> Schema -> Compiler (LLM) -> Review gate (human) -> Product (plain files)`. The domain-specific parts are the schema and the sources; the workflow is universal; the product is markdown+frontmatter that outlives the agent, the human, and the tooling. Two tests, and both must pass: - **Reader test:** a person lands on any editorial page and learns something true that makes them want to go deeper. - **Cold-agent test:** an agent lands on the vault with this skill absent and still operates it correctly, because the vault carries its own contract (AGENTS.md, schema.md, llms.txt). The second test is the architecture. This skill is the compiler and toolchain; the vault is the program. Build-time knowledge lives here; the run-time contract ships inside the vault, so it travels with the artifact to every future agent, tool, and fork. ## Gate A vault is a maintenance commitment, not a document. Size the ask before building one: | Situation | Move | |-------------------------------------------------------------|-------------------------------------------------------------------------------------| | One question, one answer | Answer it. No vault. | | Source should change how agents *behave*