knowledge-priming

You load project context by configuring a knowledge base document in `.lattice/config.yaml`. This provides ambient context to align all skills with your actual tech stack, architecture, and directory layout for consistent decisions.

Ambient context is concise project identity loaded from your repository config and knowledge base. It makes tech stack and architecture details available to all skills, enabling components to tailor outputs to actual project standards.

You generate a knowledge base document by triggering the knowledge-priming-refiner. Once produced, place it at `.lattice/standards/knowledge-base.md` and reference it in your config for automatic loading across all skills.

Yes, knowledge priming supports loading context directly from `.lattice/config.yaml`. You can reference a manually created knowledge base document within this config to keep project context up-to-date automatically.

Yes, you can manually place a markdown document at `.lattice/standards/knowledge-base.md` and reference it in `.lattice/config.yaml`. The system will load this manual doc to provide ambient context if you prefer not to use the refiner.

You should avoid loading ambient context when your project lacks established architecture conventions or a defined tech stack. Without a valid knowledge base document or `.lattice/config.yaml` setup, the context loading provides minimal alignment value.