HUE-009 — Implement Space manifests plus Project/Area CRUD and archive lifecycle
Canonical source:
docs/roadmap/issues.json·HUE-009Specification status:
TBI· Readiness:agent:blocked
Persist Projects and ongoing Areas as explicit Space subtypes with common boundaries and distinct lifecycle semantics.
- Create Space, Project and Area schemas/migrations
- Implement create/read/update/archive/delete/export
- Support role-based human-readable context-pack references
- Keep repository/milestone fields Project-only and review-cadence/evidence policy Area-specific
Acceptance criteria
Section titled “Acceptance criteria”- Project and Area persist across restart
- Subtype cannot change silently
- Archive/export preserves context-pack and source relationships
- Area works without repository fields
- Deletion impact preview lists Sessions, tasks, knowledge and bindings
Dependencies
Section titled “Dependencies”HUE-008
Non-goals
Section titled “Non-goals”- None beyond the documented scope.
Product contract
Section titled “Product contract”docs/03-spaces-sessions-knowledge.mddocs/06-projects-context-memory.mddocs/09-data-model-and-apis.md
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>.