docs: publish legacy feature catalogue
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
This commit is contained in:
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: "3DARCH-FT-6 — Repeatable database schema lifecycle"
|
||||
description: "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](../../3darch-ep-1.md) | `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
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
|
||||
## 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.
|
||||
|
||||
- [Documentation decision](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)
|
||||
|
||||
## 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](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)
|
||||
|
||||
## 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](./3darch-ft-6/tasks.md). No canonical implementation Tasks have been defined.
|
||||
|
||||
## Original source
|
||||
|
||||
- [Discord – Scope – Linas: original Feature request](https://discord.com/channels/1518726359512387766/1543925247361814568/1544647879111483562)
|
||||
- [Discord – Scope – Linas: proceed with documented mapping](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)
|
||||
|
||||
### Legacy implementation evidence
|
||||
|
||||
The Feature boundary was mined from legacy revision `c0ced47ecaf4426f47e5c2e4868677f7144b951a`.
|
||||
|
||||
- [`apps/singularity/prisma/schema.prisma`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/prisma/schema.prisma)
|
||||
- [`apps/singularity/prisma/migrations/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/prisma/migrations/)
|
||||
- [`apps/singularity/package.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/package.json)
|
||||
- [`apps/singularity/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/Dockerfile)
|
||||
Reference in New Issue
Block a user