setup-curator-cascade-for-new-memory-category
When adding a new memory primitive or category, the setup-curator cascade must update four targets in order: (1) new topic file in the owning workspace, (2) MEMORY.md in all affected workspaces including cross-workspace pointer, (3) setup-curator SKILL.md routing tree with renumbered sequential items and no gaps, (4) delete any superseded drafts immediately. Skipping any cascade target leaves orphaned backlinks or stale paths that corrupt future session routing.
Related
- setup-curator-cascade-required-for-new-artifact-categories
- sops-architectural-primitive-between-one-off-and-skill
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- self-evolving-is-model-discipline-not-hook-enforced
- setup-curator-skill-is-the-permanent-routing-guardian
- sops-canonical-home-aj-workspace-not-aj-ea