Why
NEXO has procedural fragments distributed across skills, workflow_runs, change_log, checkpoints, and followups, but not a dedicated procedural memory layer.
Current state
- Exists: partial procedural knowledge spread across many surfaces.
- Missing: a canonical representation of how this gets done that can be replayed, improved, and retrieved as a procedure.
Goal
Build a procedural memory layer that captures reusable execution patterns from real work.
Scope ideas
- Extract procedures from completed workflows and repeated change/fix patterns.
- Store steps, prerequisites, validation, failure modes, and confidence.
- Connect procedures to skills and guard/learning systems.
- Surface procedural recall separately from semantic recall.
Done when
- A procedure can be created or inferred from completed work.
- NEXO can retrieve a procedure as a first-class object.
- Repeated execution can strengthen or refine it.
Why
NEXO has procedural fragments distributed across
skills,workflow_runs,change_log, checkpoints, and followups, but not a dedicated procedural memory layer.Current state
Goal
Build a procedural memory layer that captures reusable execution patterns from real work.
Scope ideas
Done when