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-10 Features"
|
||||
description: "Review Features governed by 3DARCH-EP-10."
|
||||
description: "Review the governed Features beneath 3DARCH-EP-10."
|
||||
---
|
||||
|
||||
# Review 3DARCH-EP-10 Features
|
||||
|
||||
No child Features have been defined or approved for this Epic. Feature discovery must preserve the [3DARCH-EP-10 boundary](../3darch-ep-10.md) and requires a separate human **Approved for Solution** decision before Architecture solution work begins.
|
||||
These Features decompose the [3DARCH-EP-10 boundary](../3darch-ep-10.md) into non-overlapping user and operator outcomes grounded in the frozen legacy revision.
|
||||
|
||||
- [3DARCH-FT-31 — Browse and recognize saved apartment projects](./features/3darch-ft-31.md)
|
||||
- [3DARCH-FT-32 — Reopen a saved project into the active workspace](./features/3darch-ft-32.md)
|
||||
|
||||
Documentation approval does not grant **Approved for Solution** or implementation approval.
|
||||
|
||||
@@ -0,0 +1,86 @@
|
||||
---
|
||||
title: "3DARCH-FT-31 — Browse and recognize saved apartment projects"
|
||||
description: "Enable a person to locate prior apartment concepts by meaningful summary information rather than remembering opaque project identifiers."
|
||||
---
|
||||
|
||||
# Browse and recognize saved apartment projects
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-31` | [3DARCH-EP-10 — Reopen and Continue Previous Design Projects](../../3darch-ep-10.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to locate prior apartment concepts by meaningful summary information rather than remembering opaque project identifiers.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
A person needs to recognize and select earlier apartment concepts without remembering opaque identifiers.
|
||||
|
||||
## Expected value
|
||||
|
||||
Makes completed work discoverable and distinguishable for later continuation.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes automatic/refreshable completed-project listing, meaningful summaries, newest-first ordering, current selection, and malformed-entry filtering.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Sharing, deletion, ownership, authentication, and collaboration are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Completed projects load automatically and can be refreshed on demand.
|
||||
- [ ] Each entry provides enough context to distinguish it, including name, area, and creation date.
|
||||
- [ ] Projects are presented newest first.
|
||||
- [ ] The current project is visually distinguishable from other entries.
|
||||
- [ ] Incomplete or unreadable generation folders are not presented as completed projects, while service failure remains distinguishable from an empty history.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-26 — Generate a complete apartment concept from a natural-language brief](../../3darch-ep-7/features/3darch-ft-26.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Filesystem-backed projects have no implemented authentication, ownership, authorization, sharing, or deletion boundary.
|
||||
|
||||
## 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-31/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-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-forge/src/routes/projects.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/routes/projects.ts)
|
||||
- [`apps/archwiz-forge/src/test/routes/projects.test.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/test/routes/projects.test.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-31 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-31."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-31 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-31](../3darch-ft-31.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,88 @@
|
||||
---
|
||||
title: "3DARCH-FT-32 — Reopen a saved project into the active workspace"
|
||||
description: "Enable a person to restore a selected apartment as active work so it can be reviewed and refined instead of regenerated."
|
||||
---
|
||||
|
||||
# Reopen a saved project into the active workspace
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-32` | [3DARCH-EP-10 — Reopen and Continue Previous Design Projects](../../3darch-ep-10.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to restore a selected apartment as active work so it can be reviewed and refined instead of regenerated.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
A person needs to restore a saved apartment as active work for continued review and refinement.
|
||||
|
||||
## Expected value
|
||||
|
||||
Restores project identity, scene, context, and review controls without regenerating the design.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes retrieval by project identity, transactional workspace replacement, restored context/review modes, edit continuity, and visible load failure.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Sharing, deletion, ownership, authentication, and collaboration are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Selecting a known project retrieves its complete persisted final scene by project identity.
|
||||
- [ ] The scene and project identity become the active workspace without retaining stale data from the prior selection.
|
||||
- [ ] Project context and both review modes are available after reopening.
|
||||
- [ ] The reopened identity enables subsequent natural-language refinement of the same project.
|
||||
- [ ] Missing, unreadable, or malformed projects produce a visible failure and leave the last valid workspace intact.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-28 — Inspect the apartment from an overview](../../3darch-ep-8/features/3darch-ft-28.md)
|
||||
- [3DARCH-FT-31 — Browse and recognize saved apartment projects](./3darch-ft-31.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Missing or malformed project data can replace valid workspace state unless loading remains transactional.
|
||||
|
||||
## 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-32/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-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/store/useAppStore.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/store/useAppStore.ts)
|
||||
- [`apps/archwiz-forge/src/routes/projects.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-forge/src/routes/projects.ts)
|
||||
- [`apps/archwiz-portal/src/components/RightSidebar.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/archwiz-portal/src/components/RightSidebar.tsx)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-32 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-32."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-32 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-32](../3darch-ft-32.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