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,13 @@
|
||||
---
|
||||
title: "3DARCH-EP-7 Features"
|
||||
description: "Review Features governed by 3DARCH-EP-7."
|
||||
description: "Review the governed Features beneath 3DARCH-EP-7."
|
||||
---
|
||||
|
||||
# Review 3DARCH-EP-7 Features
|
||||
|
||||
No child Features have been defined or approved for this Epic. Feature discovery must preserve the [3DARCH-EP-7 boundary](../3darch-ep-7.md) and requires a separate human **Approved for Solution** decision before Architecture solution work begins.
|
||||
These Features decompose the [3DARCH-EP-7 boundary](../3darch-ep-7.md) into non-overlapping user and operator outcomes grounded in the frozen legacy revision.
|
||||
|
||||
- [3DARCH-FT-26 — Generate a complete apartment concept from a natural-language brief](./features/3darch-ft-26.md)
|
||||
- [3DARCH-FT-27 — Follow generation progress and intermediate design states](./features/3darch-ft-27.md)
|
||||
|
||||
Documentation approval does not grant **Approved for Solution** or implementation approval.
|
||||
|
||||
@@ -0,0 +1,89 @@
|
||||
---
|
||||
title: "3DARCH-FT-26 — Generate a complete apartment concept from a natural-language brief"
|
||||
description: "Enable a person to describe residential needs in ordinary language and receive a saved 3D apartment with inferred requirements, connected rooms, openings, furniture, and lighting."
|
||||
---
|
||||
|
||||
# Generate a complete apartment concept from a natural-language brief
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-26` | [3DARCH-EP-7 — Generate a Furnished 3D Apartment from a Brief](../../3darch-ep-7.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to describe residential needs in ordinary language and receive a saved 3D apartment with inferred requirements, connected rooms, openings, furniture, and lighting.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
A residential user needs to translate an ordinary-language brief into a coherent furnished 3D concept without manual modelling.
|
||||
|
||||
## Expected value
|
||||
|
||||
Produces the Epic’s primary saved artifact: a connected, furnished, and lit apartment scene.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes prompt validation, requirement inference, connected rooms/openings, furnishing, lighting, final persistence, and stable project identity.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Office, retail, and factory generation, export, and loading scenes into Nebula are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] The service rejects empty, too-short, or oversized briefs before generation.
|
||||
- [ ] Missing residential needs can be inferred and represented in the generated requirements.
|
||||
- [ ] The floor plan contains connected rooms, circulation, doors, exterior windows, and dimensions.
|
||||
- [ ] Furniture reflects room purpose and available space.
|
||||
- [ ] Ambient, sunlight, and room lighting complete the scene.
|
||||
- [ ] Completion returns a stable project identity and persists the final scene.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-8 — Package, deploy, and health-check workplace services](../../3darch-ep-1/features/3darch-ft-8.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Generated YAML lacks complete schema, bounds, clearance, and overlap validation.
|
||||
|
||||
## 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-26/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/archwiz-portal/src/components/LeftSidebar.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/components/LeftSidebar.tsx)
|
||||
- [`apps/archwiz-forge/src/routes/generate.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/routes/generate.ts)
|
||||
- [`apps/archwiz-forge/src/skills/extract-requirements.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/skills/extract-requirements.md)
|
||||
- [`apps/archwiz-forge/src/skills/generate-structure.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/skills/generate-structure.md)
|
||||
- [`apps/archwiz-forge/src/skills/place-furniture.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/skills/place-furniture.md)
|
||||
- [`apps/archwiz-forge/src/skills/add-lighting.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/skills/add-lighting.md)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-26 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-26."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-26 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-26](../3darch-ft-26.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-27 — Follow generation progress and intermediate design states"
|
||||
description: "Enable a person to understand which generation stage is running and see the apartment emerge instead of waiting for an opaque request."
|
||||
---
|
||||
|
||||
# Follow generation progress and intermediate design states
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-27` | [3DARCH-EP-7 — Generate a Furnished 3D Apartment from a Brief](../../3darch-ep-7.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to understand which generation stage is running and see the apartment emerge instead of waiting for an opaque request.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
A person needs visible generation stages and intermediate results rather than waiting on an opaque long-running request.
|
||||
|
||||
## Expected value
|
||||
|
||||
Builds trust in long-running generation through progressive feedback and safe failure handling.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes ordered stage reporting, intermediate structural/furnished previews, final-scene selection, and failure cleanup.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Office, retail, and factory generation, export, and loading scenes into Nebula are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Progress identifies requirements, structure, furniture, and lighting stages in order.
|
||||
- [ ] Structural and furnished intermediate scenes replace the current preview as they become available.
|
||||
- [ ] Completion selects the final persisted scene.
|
||||
- [ ] Failure produces a visible message and does not leave a false completed project.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-26 — Generate a complete apartment concept from a natural-language brief](./3darch-ft-26.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Failure cleanup must prevent partial generation output from appearing as a completed project.
|
||||
|
||||
## 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-27/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/archwiz-portal/src/api/client.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/api/client.ts)
|
||||
- [`apps/archwiz-portal/src/App.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/App.tsx)
|
||||
- [`apps/archwiz-portal/src/components/LeftSidebar.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/components/LeftSidebar.tsx)
|
||||
- [`apps/archwiz-forge/src/routes/generate.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/routes/generate.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-27 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-27."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-27 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-27](../3darch-ft-27.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