Your Name
2dabf8ef03
- memory/: cross-session project memory with decisions, lessons, failures, architecture, and sessions categories. Each has format templates and lifecycle documentation. - skills/: 12 reusable specialized methodologies (tdd, systematic-debugging, architecture-design, code-review, security-review, repository-analysis, failure-analysis, refactoring, test-analysis, incident-investigation, browser-automation, research). Each has frontmatter and methodology sections. - improvements/: proposal-based improvement system requiring human approval. - scripts/memory-lifecycle.sh: deterministic memory operations (recall, store, list, search, sessions, cleanup). - scripts/test-memory-system.sh: 12 structural tests for all new systems. - orchestrator.md: added Memory Recall stage, Learning and Memory Storage stage, Improvement Proposals workflow, memory/skills rules, and 3 new actions (A23-A27) to the action catalog. Updated behavioral acceptance test and state separation model. - All 12 subagents: added Memory & Skills Awareness sections with recall and store instructions. - docs/AGENT_ARCHITECTURE.md: documented memory, skills, and improvements systems (sections 12-14). Updated action count (27), state model, and remaining weaknesses. - README.md: documented new systems, updated repository layout, added test-memory-system.sh documentation. All 39 tests pass (16 architecture + 12 memory + 11 bootstrap).
29 lines
893 B
Markdown
29 lines
893 B
Markdown
# Current Architecture
|
|
|
|
This directory contains the current architectural state of the project, updated by Architect and Maintainer.
|
|
|
|
## Files
|
|
|
|
- `component-map.md` — current component relationships
|
|
- `constraints.md` — architectural constraints and rules
|
|
- `interfaces.md` — key interfaces and contracts
|
|
|
|
## Ownership
|
|
|
|
- **Architect** owns architecture decisions and boundary definitions
|
|
- **Maintainer** audits architecture against reality and corrects drift
|
|
- **Reviewer** verifies architecture documentation is consistent with code
|
|
|
|
## Lifecycle
|
|
|
|
Architecture records are updated when:
|
|
- New components or boundaries are established
|
|
- Interfaces change
|
|
- Constraints are added or relaxed
|
|
- Architecture decisions are made (link from `decisions/`)
|
|
|
|
Architecture records are NOT updated for:
|
|
- Task-specific implementation details
|
|
- Temporary workarounds
|
|
- Feature-specific code paths
|