Commonplace architecture
Type: types/tag-readme.md
How Commonplace itself is structured and installed. Assign this tag when an artifact substantively explains or proposes a Commonplace-specific arrangement: repository or package layout, installation, control-plane organization, storage authority, subsystem responsibilities, or interfaces. A worked Commonplace case can qualify within a broader argument. A general design principle does not qualify merely because Commonplace uses it or a footer links to its implementation.
This is a child of architecture; members keep both tags. The parent covers structural questions across agent-operated KBs and agent runtimes. This head also routes to current-state documentation and ADRs, which remain untagged under their collection rules. A tag on a proposal indicates its subject, not adoption.
Current structure and decisions
- Reference overview — entry point for current-state documentation and architecture decisions
- Commonplace architecture — collections, packaged runtime, shipped skills, and operational surfaces
- Projects read the library from the installed package — the user's KB stays in the project while the library is read from the installed package
- Control-plane goals — how AGENTS.md, the scaffold template, and installation supply KB goals
- Instruction generation — the shipped build step and substitution points
- Scenario architecture — how the shipped architecture meets the requirements derived from user scenarios
- Storage architecture — canonical files, derived indexes, and database-owned operational state
- Review state in SQLite — the authority decision that made review operational state database-owned
Worked cases
- Canonical files and database authority — Commonplace's review subsystem illustrates an explicit authority transfer for one state class
- Edge ownership and storage choice — the freshness store supplies a bounded example of workload requirements and a separate database authority decision
- Runtime structure and governance — the Commonplace matrix identifies the governance surfaces it owns and the harness scheduler it does not
- Always-loaded context mechanisms — configuration injection uses Commonplace's installation mechanism as a worked case
Proposed changes
- Checked inline blocks — proposed source/copy control for shared authoring instructions
- Channel-compiled instruction artifacts — proposed installation-time resolution of shell-specific instruction forms