2026-03-04T09-45-14_auto_memory/memories.db, memory/2026-03-04-procedural-m
This commit is contained in:
parent
d9423813e1
commit
7c7d9147ee
17
memory/2026-03-04-procedural-memory-p1-sprint-planning.md
Normal file
17
memory/2026-03-04-procedural-memory-p1-sprint-planning.md
Normal file
@ -0,0 +1,17 @@
|
||||
# 2026-03-04 Session Notes
|
||||
|
||||
## Procedural Memory P1 Sprint Planning
|
||||
|
||||
Nicholai reviewed SPRINT-BRIEF.md for Procedural Memory P1 (making skills first-class graph nodes) and determined the optimal execution sequence for six deliverables based on dependencies.
|
||||
|
||||
Identified implementation order:
|
||||
1. **Configuration** — add `procedural` config to types + defaults (foundation)
|
||||
2. **Migration** — create `skill_meta` table (storage foundation)
|
||||
3. **Skill entity creation** — install flow: parse, enrich, create entity + metadata
|
||||
4. **Frontmatter enrichment** — called during install, integrated with creation
|
||||
5. **Skill uninstallation** — cleanup counterpart
|
||||
6. **Filesystem reconciler** — startup backfill + watcher (integrates everything)
|
||||
|
||||
Key emphasis: check migration numbering in `packages/core/src/migrations/index.ts` before writing new migration code to avoid collisions (has been a recurring issue when translating specs to code).
|
||||
|
||||
Session ended with assistant beginning to inspect the migrations index prior to implementation.
|
||||
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user