refactor: cut over to normalized exhibit schema
This commit is contained in:
+3
-3
@@ -28,12 +28,12 @@ This is the ordered implementation roadmap following the accepted exhibit model.
|
||||
|
||||
## Milestone 2: exhibit-schema cutover
|
||||
|
||||
- [ ] Add boards, exhibits, exhibit types, subtype tables, immutable template versions, and cloned mutable levels.
|
||||
- [ ] Migrate transitional `widgets`, `widget_relations`, and `playthrough_*` data with equivalence checks.
|
||||
- [x] Add boards, exhibits, exhibit types, subtype tables, immutable template versions, and mutable levels.
|
||||
- [x] Cut over the explicitly disposable POC database directly; no transitional data existed to backfill or compare.
|
||||
- [ ] Implement template instantiation and “save level as template” as transactional clone operations.
|
||||
- [x] Introduce a server-side repository/service boundary so SQL and cloning transactions do not live in Express route handlers.
|
||||
- [ ] Move the frontend to an exhibit/widget registry backed by the normalized API.
|
||||
- [ ] Remove transitional tables only after automated data-equivalence and behavior checks pass.
|
||||
- [x] Remove transitional `widgets`, `widget_relations`, and `playthrough_*` tables in the canonical cutover migration.
|
||||
|
||||
## Milestone 3: events and parties
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# GUPI OSINT Board: canonical exhibit data model
|
||||
|
||||
Status: accepted design foundation.
|
||||
Status: accepted design foundation; core schema implemented by migration 006. Template clone operations, parties, and the frontend exhibit registry remain roadmap work.
|
||||
|
||||
## Vocabulary
|
||||
|
||||
|
||||
Reference in New Issue
Block a user