jarvis-at-skic
3a2e19fc52
4.6 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-32 — Reopen a saved project into the active workspace | 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 | 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-FT-31 — Browse and recognize saved apartment projects
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.
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.