jarvis-at-skic
3a2e19fc52
4.1 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-6 — Repeatable database schema lifecycle | Enable service developers and operators to evolve and apply the workplace persistence schema consistently across fresh workspaces and deployed instances. |
Repeatable database schema lifecycle
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-6 |
3DARCH-EP-1 — Engineering Platform, Quality, and Operability | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable service developers and operators to evolve and apply the workplace persistence schema consistently across fresh workspaces and deployed instances.
User or operator problem
Service teams need database changes to be ordered, repeatable, and compatible across local and deployed environments.
Expected value
Reduces schema drift and makes migration failure visible before the service accepts traffic.
Scope
Includes the Prisma schema, ordered migrations, client generation, development migration workflow, and production migration gate.
Exclusions
- End-user product behavior and solution or release authorization are outside these engineering Features.
Acceptance outcomes
- The database contract is versioned in one Prisma schema.
- Ordered migrations create and evolve user, settings, scene, and seat data.
- Local service workflows generate the Prisma client and apply development migrations.
- Production startup applies pending migrations before accepting traffic and exposes migration failure.
Dependencies
Risks
- Migration failure can block service startup or leave persistence incompatible with application code.
Human approval
Linas approved this Feature for documentation on 2026-09-02T10:40:43.220Z. It is not Approved for Solution and has no implementation approval.
Delivery status evidence
The Feature was separately registered at IN_BACKLOG as an accepted catalogue boundary. This records backlog retention, not design or delivery progress.
- Event: Catalogue registration
- Actor and authority: Linas — Human project team member
- Reason: The Feature catalogue was accepted for governed documentation and retained in the backlog.
- Status evidence
Architecture traceability
- Requirements: none derived.
- Readiness: Not started.
Architecture solution work must not begin until a separate human Approved for Solution decision is recorded.
Tasks
Review the Tasks group. No canonical implementation Tasks have been defined.
Original source
- Discord – Scope – Linas: original Feature request
- Discord – Scope – Linas: proceed with documented mapping
Legacy implementation evidence
The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.