coulomb/can-you-assist
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(concept) + chore(workplan): complete T01 for CYA-WP-0003 — conceptual model for directory-bound activation + retrospection loops (design doc created)

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-26 15:08:39 +02:00
parent 9e249d859b
commit cdae2fac2f
2 changed files with 146 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
workplans/CYA-WP-0003-contextual-memory-activation-and-retrospection.md
View File

@@ -48,21 +48,26 @@ This workplan directly addresses two remaining gaps identified in the post-0002
```task
id: CYA-WP-0003-T01
status: todo
status: done
priority: high
state_hub_task_id: "335595b4-96fe-401f-ab4c-0824a6ba3f05"
started: "2026-05-27 ralph iter 1"
completed: "2026-05-27"
```
- Deeply align the two ideas (directory-bound activation + regular retrospections) with INTENT.md and MemoryVision.md.
- Define clear models for:
- "Memory activation" (what gets recalled automatically, when, and why).
- Retrospection as a first-class interaction pattern (what is captured, how goals/preferences are updated).
- Produce a short design note (or section in MemoryVision) describing the interaction loop.
- Identify minimal extensions needed to the existing memory ports and data model.
**Done** — produced `docs/cya-memory-activation-and-retrospection-concept.md`.
**Acceptance criteria**:
- Clear, written concept exists and is consistent with INTENT and MemoryVision.
- The two ideas are shown to reinforce each other rather than compete.
- Deeply aligned the two ideas with INTENT.md (Personalized Console Helper, project-specific memory, recurring workflows, user control) and MemoryVision.md (Project/Directory Memory, Workflow Recipes, activation planning, explainability requirements).
- Defined clear models:
- **Memory Activation**: Automatic, scope-aware (cwd + git root) surfacing of relevant items (preferences, patterns, safety signals) with strong provenance and user control.
- **Retrospection Loops**: Deliberate reflection sessions that produce higher-order memory (`interaction_goal`, retrospection outcomes) which preferentially influence future activation and behavior.
- The two mechanisms reinforce each other: normal use generates candidates for retrospection; retrospection produces high-quality memory that improves future activation.
- Identified minimal port/data model extensions for T02 (richer `kind` support and activation hints in recall, standardized retrospection record kinds).
- Non-negotiables (explainability + safety invariants) explicitly preserved.
**Acceptance criteria met**:
- Clear, written concept document exists and is consistent with INTENT and MemoryVision.
- The ideas are shown to reinforce each other in a user-controlled continuous optimization loop.
### T02 — Extend memory ports and data model for activation and retrospection