Concepts
Clients and plugins
Expose a small factory-based client that works without plugins. Prebuilt interpretation plugins are optional and compose through the same contracts as third-party plugins.Composable standards packs
Split the engineering reference into independent packs, then select a recommended set for each language. Each component directory under `packs/` owns its `granary.json`. `packs/granary.json` composes the distributed sets. The root manifest installs only the five shared/TypeScript components; Rust and Python remain distribution material.Granary context packs
Your project uses a particular version of a tool. A coding agent may know a different version, and your team's conventions may not exist in its training data at all. Links and pasted excerpts help for one conversation; the next agent starts without them.Installation model
Granary installs selected reference material into consumer-owned paths, defaulting to `.granary/context/`.Manifest and pack installation proposal
**Status: draft for review.** This describes a proposed API, not the currently implemented schema. Approval covers the design; it does not authorize publishing or dependency changes.Pack maintenance and skills
Treat installed reference material as content a project may intentionally customize, with explicit review when upstream changes arrive.Skills compatibility
Granary borrows skills' source-based installation experience while defining a separate reference-material contract.Standards documents
Represent standards as readable Markdown with extractable structure, including their rationale, rules, examples, and enforcement.