jarvis-at-skic
3a2e19fc52
4.1 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-27 — Follow generation progress and intermediate design states | 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 | 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
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.
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.