Enter and resume the last workplace location
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-13 | 3DARCH-EP-3 — Navigate and Explore the Virtual Workplace | IN_BACKLOG | EXACT | 3D Architecture Wizzard team | No |
Description
Enable a returning user to enter the previously occupied floor and position rather than restarting from a default location every time.
User or operator problem
Returning users lose continuity when every session starts on a default floor and pose.
Expected value
Restores spatial continuity so returning users can resume work where they left it.
Scope
Includes loading a valid stored scene and pose, safe defaults, and persistence of the latest location when leaving.
Exclusions
- VR/controller navigation and generated-apartment review are excluded.
Acceptance outcomes
- Entry loads the stored scene, position, and orientation when valid.
- A safe default is used when no prior location exists.
- Leaving the workplace persists the latest known pose and scene.
Dependencies
- 3DARCH-FT-9 — Enterprise sign-in and session continuity
- 3DARCH-FT-10 — First-entry avatar onboarding
Risks
- Location persists primarily on orderly socket disconnect, so abrupt loss can discard recent movement.
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.