Pattern Proposal: File-based knowledge base layout
Summary
cas-knowledge separates global, projects, runtime, and templates directories, forming a file-based architectural knowledge store.
Candidate Pattern
- ID:
file-based-knowledge-base-layout - Classification: architectural
- Maturity: emerging
- Type: emerging
Observed Signals
No specific signals listed.
Evidence
Supporting Evidence
- cas-knowledge/global/ - Global knowledge directory with decisions, governance, rules, patterns, and signals subdirectories.
- cas-knowledge/projects/ - Project-scoped knowledge directory with multiple project folders.
- cas-knowledge/runtime/execution-profile.yaml - Machine-readable runtime execution profile.
- cas-knowledge/runtime/rule-context.json - Machine-readable rule context state.
- cas-knowledge/templates/ - Templates for architecture and knowledge artifacts.
Scope Assessment
- Evidence Strength: medium
- Confidence: medium
- Applies to: ideas-to-life-cas
Rationale
- Intent: Persist architecture knowledge, governance rules, project contexts, runtime state, and artifact templates using filesystem conventions.
- Context: The system needs a portable, reviewable, and versionable store of non-code architectural artifacts.
- Force: Knowledge must be inspectable by humans
- Force: Global and project scopes must not collide
- Force: Templates should guide new artifact creation
- Force: Runtime state should be separable from stable knowledge
Traceability
Artifact source: proposed-patterns