jarvis-at-skic
3a2e19fc52
4.3 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-31 — Browse and recognize saved apartment projects | 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 | 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
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.
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.