HUE-014 — Implement global, Space, source and episodic memory lifecycle with provenance
Canonical source:
docs/roadmap/issues.json·HUE-014Specification status:
TBI· Readiness:agent:blocked
Keep preferences, current Space state, authoritative-source facts and archived episodes separate and correctable.
- Implement four memory layers and proposal lifecycle
- Add provenance, sensitivity, freshness, supersession and retention
- Prevent workers from direct shared-memory writes
- Add typed epistemic status
Acceptance criteria
Section titled “Acceptance criteria”- Layer cannot be promoted silently
- Stale source memory is visibly stale
- Closed Session stays searchable but is not injected by default
- Correction/supersession changes future retrieval
- Export/delete works by layer
Dependencies
Section titled “Dependencies”HUE-013
Non-goals
Section titled “Non-goals”- None beyond the documented scope.
Product contract
Section titled “Product contract”- Follow the milestone and repository product contract.
Implementation handoff requirements
Section titled “Implementation handoff requirements”- Preserve the documented security, project, memory and event boundaries.
- Add or update automated tests for every observable acceptance criterion.
- Provide real verification output; do not rely on a worker/agent self-report.
- Update only the exact documentation sections whose status changed.
- Include screenshots or a recording for user-interface changes.
- Include migration, rollback and recovery notes for data/state changes.
- Link the pull request to this issue with
Closes #<issue-number>.