// Embedding
Embed .knowledge in your app
Embedding should read generated trust artifacts and run CLI checks, not bypass the source-of-truth order.
// integration pattern
Use generated artifacts as the boundary
Applications should read .knowledge outputs such as routing bundles, trust reports, repair queues, metrics, and PR summaries after the repository has generated them.
Do not treat a website copy, wiki paragraph, or external memory recall as the implementation contract. Use the repo-local artifacts and exact commands as proof.
- Call CLI tools from the repository root.
- Read JSON outputs for status and diagnostics.
- Display trust state next to context, not hidden behind it.
- Keep external memory advisory unless current source evidence agrees.
Routing bundle PROOF LINK
Routing bundle
Builds the first-read routing artifact.
PR summary generator PROOF LINK
PR summary generator
Produces reviewer-facing summary output.
// technical notes