jarvis-at-skic
3a2e19fc52
4.9 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-26 — Generate a complete apartment concept from a natural-language brief | 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 | 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
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.
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.