Pattern Proposal: Knowledge Base Artifact Folder Contract
Summary
cas-knowledge uses a fixed folder taxonomy for global rules, models, patterns, narratives, signals, projects, runtime state, and templates.
Candidate Pattern
- ID:
knowledge-base-artifact-folder-contract - Classification: governance
- Maturity: strategic_direction
- Type: emerging
Observed Signals
No specific signals listed.
Evidence
Supporting Evidence
- cas-knowledge/global/rules, cas-knowledge/global/models, cas-knowledge/global/patterns, cas-knowledge/global/narratives, cas-knowledge/global/signals - Directory taxonomy for long-lived knowledge artifact classes.
- cas-knowledge/runtime, cas-knowledge/runtime/evaluations, cas-knowledge/runtime/traces, cas-knowledge/runtime/execution-profile.yaml, cas-knowledge/runtime/rule-context.json - Directory and file layout separate mutable runtime context from governed knowledge.
- cas-knowledge/templates/architecture_decision_record_template.md, cas-knowledge/templates/pattern_template.md, cas-knowledge/templates/rule_template.md - Named templates act as artifact contracts inside the same knowledge-base tree.
Scope Assessment
- Evidence Strength: medium
- Confidence: medium
- Applies to: ideas-to-life-cas
Rationale
- Intent: Use the directory layout as a lightweight schema for classified and governed knowledge artifacts.
- Context: A repository that treats markdown-based knowledge and runtime context as first-class system state.
- Force: Artifacts need stable classification
- Force: Runtime state should be separated from long-lived governance content
- Force: Templates need to live alongside the artifacts they define
Traceability
Artifact source: proposed-patterns