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:
@@ -1,8 +1,19 @@
|
||||
---
|
||||
title: "3DARCH-EP-1 Features"
|
||||
description: "Review Features governed by 3DARCH-EP-1."
|
||||
description: "Review the governed Features beneath 3DARCH-EP-1."
|
||||
---
|
||||
|
||||
# Review 3DARCH-EP-1 Features
|
||||
|
||||
No child Features have been defined or approved for this Epic. Feature discovery must preserve the [3DARCH-EP-1 boundary](../3darch-ep-1.md) and requires a separate human **Approved for Solution** decision before Architecture solution work begins.
|
||||
These Features decompose the [3DARCH-EP-1 boundary](../3darch-ep-1.md) into non-overlapping user and operator outcomes grounded in the frozen legacy revision.
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./features/3darch-ft-1.md)
|
||||
- [3DARCH-FT-2 — Shared contracts and reusable interface foundations](./features/3darch-ft-2.md)
|
||||
- [3DARCH-FT-3 — Automated multi-layer quality verification](./features/3darch-ft-3.md)
|
||||
- [3DARCH-FT-4 — Reusable UI component authoring and review workbench](./features/3darch-ft-4.md)
|
||||
- [3DARCH-FT-5 — Versioned engineering knowledge hub](./features/3darch-ft-5.md)
|
||||
- [3DARCH-FT-6 — Repeatable database schema lifecycle](./features/3darch-ft-6.md)
|
||||
- [3DARCH-FT-7 — Integrated local runtime with persistence and health checks](./features/3darch-ft-7.md)
|
||||
- [3DARCH-FT-8 — Package, deploy, and health-check workplace services](./features/3darch-ft-8.md)
|
||||
|
||||
Documentation approval does not grant **Approved for Solution** or implementation approval.
|
||||
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: "3DARCH-FT-1 — Reproducible monorepo development workspace"
|
||||
description: "Enable contributors to install one pinned toolchain and run coordinated development, build, type-check, lint, test, documentation, and Storybook workflows across the platform."
|
||||
---
|
||||
|
||||
# Reproducible monorepo development workspace
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-1` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable contributors to install one pinned toolchain and run coordinated development, build, type-check, lint, test, documentation, and Storybook workflows across the platform.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Contributors face onboarding delays and environment-specific failures when each package requires separately reconciled tools and commands.
|
||||
|
||||
## Expected value
|
||||
|
||||
Reduces contributor setup time and makes workspace checks repeatable across the monorepo.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes the pinned Node/pnpm workspace baseline, root task orchestration, environment examples, and contributor setup path.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] The workspace uses a declared Node and pnpm baseline.
|
||||
- [ ] One root workflow can run each supported application/package task through the dependency graph.
|
||||
- [ ] Local setup instructions and environment examples are available to contributors.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- None recorded.
|
||||
|
||||
## Risks
|
||||
|
||||
- Tracked setup guidance and environment examples have legacy inconsistencies that can undermine repeatability.
|
||||
|
||||
## 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-1/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`.
|
||||
|
||||
- [`package.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/package.json)
|
||||
- [`pnpm-workspace.yaml`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/pnpm-workspace.yaml)
|
||||
- [`turbo.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/turbo.json)
|
||||
- [`devbox.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/devbox.json)
|
||||
- [`README.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/README.md)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-1 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-1."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-1 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-1](../3darch-ft-1.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: "3DARCH-FT-2 — Shared contracts and reusable interface foundations"
|
||||
description: "Enable application teams to evolve real-time interactions and user interfaces against shared types, constants, TypeScript rules, lint rules, and reusable UI components rather than duplicating incompatible definitions."
|
||||
---
|
||||
|
||||
# Shared contracts and reusable interface foundations
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-2` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable application teams to evolve real-time interactions and user interfaces against shared types, constants, TypeScript rules, lint rules, and reusable UI components rather than duplicating incompatible definitions.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Application teams risk incompatible real-time behavior and inconsistent interfaces when contracts, constants, and components are duplicated.
|
||||
|
||||
## Expected value
|
||||
|
||||
Keeps client, service, and interface behavior aligned while reducing duplicated definitions.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes shared player, chat, voice, seat, authentication, control, socket, TypeScript, lint, and reusable UI foundations.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Frontend and backend consume the same player, chat, voice, seat, and authentication contracts.
|
||||
- [ ] Common controls and socket event names have one shared definition.
|
||||
- [ ] Reusable UI components can be developed, demonstrated, and tested independently.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Shared contract changes can break multiple applications unless all consumers are validated together.
|
||||
|
||||
## 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-2/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`.
|
||||
|
||||
- [`packages/utils/types/src/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/types/src/)
|
||||
- [`packages/utils/constants/src/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/constants/src/)
|
||||
- [`packages/utils/typescript-config/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/typescript-config/)
|
||||
- [`packages/utils/eslint-config/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/eslint-config/)
|
||||
- [`packages/stardust/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-2 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-2."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-2 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-2](../3darch-ft-2.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "3DARCH-FT-3 — Automated multi-layer quality verification"
|
||||
description: "Enable contributors to detect regressions in UI components, stores, APIs, real-time handlers, persistence behavior, generation pipelines, and end-to-end journeys before release."
|
||||
---
|
||||
|
||||
# Automated multi-layer quality verification
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-3` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable contributors to detect regressions in UI components, stores, APIs, real-time handlers, persistence behavior, generation pipelines, and end-to-end journeys before release.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Maintainers need regressions to surface before release across stores, APIs, persistence, UI components, and integrated journeys.
|
||||
|
||||
## Expected value
|
||||
|
||||
Provides earlier, repeatable evidence that principal product and platform behavior still works.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes root and application-level unit, integration, component, persistence, and end-to-end verification commands and assets.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Root commands invoke unit, CI, type, lint, and end-to-end checks consistently.
|
||||
- [ ] Application-level tests cover the principal workplace and Archwiz behaviors.
|
||||
- [ ] End-to-end browser checks can validate integrated user journeys.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
- [3DARCH-FT-2 — Shared contracts and reusable interface foundations](./3darch-ft-2.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- The repository contains broad test assets but no tracked CI workflow, so local commands alone do not prove release readiness.
|
||||
|
||||
## 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-3/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`.
|
||||
|
||||
- [`package.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/package.json)
|
||||
- [`apps/horizon/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/horizon/)
|
||||
- [`apps/nebula/src/test/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/test/)
|
||||
- [`apps/singularity/src/test/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/test/)
|
||||
- [`apps/archwiz-portal/src/test/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/test/)
|
||||
- [`apps/archwiz-forge/src/test/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/test/)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-3 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-3."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-3 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-3](../3darch-ft-3.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "3DARCH-FT-4 — Reusable UI component authoring and review workbench"
|
||||
description: "Enable frontend developers and designers to create, demonstrate, accessibility-check, and test consistent interface components outside a product application."
|
||||
---
|
||||
|
||||
# Reusable UI component authoring and review workbench
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-4` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable frontend developers and designers to create, demonstrate, accessibility-check, and test consistent interface components outside a product application.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Designers and frontend developers need to review component behavior and accessibility without mounting a complete product application.
|
||||
|
||||
## Expected value
|
||||
|
||||
Accelerates consistent component delivery and exposes interaction or accessibility defects earlier.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes component generation, package export, Storybook documentation, accessibility checks, and headless story interactions.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] A generator creates a component, story, and package export in the chosen atomic category.
|
||||
- [ ] Storybook presents component documentation and accessibility tooling.
|
||||
- [ ] Story interactions can run in a headless browser.
|
||||
- [ ] The component library builds behind a stable package entry point.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
- [3DARCH-FT-2 — Shared contracts and reusable interface foundations](./3darch-ft-2.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Storybook, accessibility tooling, and browser interaction tests can drift from the shipped component package.
|
||||
|
||||
## 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-4/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`.
|
||||
|
||||
- [`packages/stardust/README.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/README.md)
|
||||
- [`packages/stardust/turbo/generators/config.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/turbo/generators/config.ts)
|
||||
- [`packages/stardust/.storybook/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/.storybook/)
|
||||
- [`packages/stardust/src/atoms/Button/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/src/atoms/Button/)
|
||||
- [`packages/stardust/vite.config.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/stardust/vite.config.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-4 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-4."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-4 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-4](../3darch-ft-4.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: "3DARCH-FT-5 — Versioned engineering knowledge hub"
|
||||
description: "Enable contributors and operators to maintain architecture, setup, authentication, rendering, and deployment guidance alongside source and publish it as a browsable static site."
|
||||
---
|
||||
|
||||
# Versioned engineering knowledge hub
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-5` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable contributors and operators to maintain architecture, setup, authentication, rendering, and deployment guidance alongside source and publish it as a browsable static site.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Contributors and operators need one discoverable, versioned source for implemented architecture and operating guidance.
|
||||
|
||||
## Expected value
|
||||
|
||||
Keeps engineering knowledge reviewable with source and available as a browsable reference.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes version-controlled engineering documentation authoring, build, navigation, indexes, sitemap, and implemented-versus-planned boundaries.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Contributors can author and preview version-controlled MDX documentation.
|
||||
- [ ] The knowledge hub builds through a root workspace command.
|
||||
- [ ] Static output contains navigable topic pages, indexes, and a sitemap.
|
||||
- [ ] Published guidance distinguishes implemented behavior from future intent.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Published guidance can confuse implemented behavior with future intent unless evidence boundaries remain explicit.
|
||||
|
||||
## 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-5/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/constellation/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/constellation/)
|
||||
- [`apps/constellation/package.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/constellation/package.json)
|
||||
- [`apps/constellation/scripts/build.js`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/constellation/scripts/build.js)
|
||||
- [`README.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/README.md)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-5 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-5."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-5 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-5](../3darch-ft-5.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -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)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-6 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-6."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-6 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-6](../3darch-ft-6.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: "3DARCH-FT-7 — Integrated local runtime with persistence and health checks"
|
||||
description: "Enable developers to start the browser workplace, real-time backend, and database as one local environment and determine whether each service is healthy."
|
||||
---
|
||||
|
||||
# Integrated local runtime with persistence and health checks
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-7` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable developers to start the browser workplace, real-time backend, and database as one local environment and determine whether each service is healthy.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Developers need the browser client, backend, and database to start together with visible dependency health.
|
||||
|
||||
## Expected value
|
||||
|
||||
Provides a repeatable integration environment and shortens diagnosis of startup or dependency failures.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes coordinated local startup for frontend, backend, and PostgreSQL plus storage, ordering, and health checks.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] One local workflow starts the frontend, backend, and PostgreSQL dependencies.
|
||||
- [ ] Service ordering and persistent database storage are declared.
|
||||
- [ ] Frontend, backend, and database health checks expose startup failure.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
- [3DARCH-FT-6 — Repeatable database schema lifecycle](./3darch-ft-6.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Service health can appear green while a dependency or browser route remains unusable.
|
||||
|
||||
## 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-7/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`.
|
||||
|
||||
- [`docker-compose.yml`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/docker-compose.yml)
|
||||
- [`apps/nebula/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/Dockerfile)
|
||||
- [`apps/singularity/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/Dockerfile)
|
||||
- [`apps/singularity/src/routes/health.routes.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/routes/health.routes.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-7 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-7."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-7 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-7](../3darch-ft-7.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,89 @@
|
||||
---
|
||||
title: "3DARCH-FT-8 — Package, deploy, and health-check workplace services"
|
||||
description: "Enable operators to build versionable frontend/backend images, package Kubernetes deployment configuration, and admit only healthy services to traffic."
|
||||
---
|
||||
|
||||
# Package, deploy, and health-check workplace services
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-8` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable operators to build versionable frontend/backend images, package Kubernetes deployment configuration, and admit only healthy services to traffic.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Operators need repeatable artifacts and health gates for deploying the workplace services safely.
|
||||
|
||||
## Expected value
|
||||
|
||||
Creates versionable deployment inputs and prevents unhealthy services from receiving traffic.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes independent service images, repeatable tagging/publishing tasks, Helm configuration, probes, ingress, and dependency-aware readiness.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- End-user product behavior and solution or release authorization are outside these engineering Features.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Frontend and backend images build independently for the declared platform.
|
||||
- [ ] Images can be tagged and published through repeatable tasks.
|
||||
- [ ] Helm charts configure deployments, services, ingress, runtime values, and health probes for both services.
|
||||
- [ ] Process and dependency health distinguish a running backend from a usable backend.
|
||||
- [ ] Database failure withholds readiness and returns a bounded unhealthy response.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md)
|
||||
- [3DARCH-FT-3 — Automated multi-layer quality verification](./3darch-ft-3.md)
|
||||
- [3DARCH-FT-6 — Repeatable database schema lifecycle](./3darch-ft-6.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Legacy packaging and deployment assumptions require validation against the target runtime before release.
|
||||
|
||||
## 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-8/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`.
|
||||
|
||||
- [`Taskfile.yml`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/Taskfile.yml)
|
||||
- [`apps/nebula/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/Dockerfile)
|
||||
- [`apps/singularity/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/Dockerfile)
|
||||
- [`apps/singularity/src/routes/health.routes.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/routes/health.routes.ts)
|
||||
- [`helm/`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/helm/)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-8 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-8."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-8 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-8](../3darch-ft-8.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
Reference in New Issue
Block a user