Pattern Proposal: File-Backed Knowledge Repository
Summary
Persistent architectural and governance state is structured in version-controlled markdown, YAML, and JSON directories.
Candidate Pattern
- ID:
file-backed-knowledge-repository - Classification: architectural
- Maturity: established
- Type: implemented
Observed Signals
No specific signals listed.
Evidence
Supporting Evidence
- src/cas_runner/bootstrap.py (merge_cas_governance_block, init_workspace, bootstrap) - Initializes and updates local workspace structures against knowledge templates.
- cas-knowledge/ - Repository root for global rules, project configurations, and runtime state.
Scope Assessment
- Evidence Strength: high
- Confidence: high
- Applies to: ideas-to-life-cas
Rationale
- Intent: Use git as the source of truth for architecture decisions, patterns, governance rules, and runtime profiles.
- Context: Architecture artifacts need transparency, branchability, peer-review capabilities, and audit histories without database lock-in.
- Force: Decisions and patterns must be visible and editable by developers directly in source control.
- Force: Runtime tools must be able to read and write execution context without external relational infrastructure.
Traceability
Artifact source: proposed-patterns