Story: Workspace
Table of Contents
This page documents a story in Sprint 17. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Introduce the Workspace entity: bitemporal schema, service layer, CRUD UI, lifecycle operations, and codegen pipeline propagation for workspace_id (Phases 1-4 including controller wiring and the Data Workshop UI tab).
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 17 |
| Now | Completed 2026-05-20. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-05-20 |
3. Acceptance
- All tasks complete; PR-by-PR breakdown in
git log.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Task: Workspace: bitemporal schema, service layer, UI, and lifecycle operations | DONE | 2026-05-22 | 2026-05-22 | Full implementation of the workspace entity as a first-class domain object with bitemporal history, a complete NATS serv |
| Task: Add workspace_id to codegen pipeline (Phases 1-4) | DONE | 2026-05-22 | 2026-05-22 | - Phase 4: propagate `workspace_id` through the C++ codegen layer — adds `workspace_id` field to all domain entities fla |
| Task: [workspace] Phase 3+4: controller wiring and Data Workshop UI | DONE | 2026-05-22 | 2026-05-22 | Completes the remaining workspace propagation work after PR #773 (codegen) was merged. |
| Task: docs: Update workspace design plan with Phase 3–4 progress | DONE | 2026-05-22 | 2026-05-22 | Update the workspace design plan document to reflect completion of Phases 1–2 and substantial progress through Phases 3– |
5. Decisions
- Bitemporal from day one
- the workspace schema uses bitemporal tracking (valid_from / valid_to) to support audit trails and rollback without a separate event log.
6. Out of scope
- Workspace sharing / permissions (deferred to a later sprint).