jarvis-at-skic
3a2e19fc52
4.3 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-16 — Travel between workplace floors | Enable a user to approach an elevator, receive a contextual action, and move between the implemented ninth- and tenth-floor scenes. |
Travel between workplace floors
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-16 |
3DARCH-EP-3 — Navigate and Explore the Virtual Workplace | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a user to approach an elevator, receive a contextual action, and move between the implemented ninth- and tenth-floor scenes.
User or operator problem
Users need a contextual, understandable way to move between the implemented workplace floors.
Expected value
Connects the workplace’s floor experiences while keeping real-time scene membership accurate.
Scope
Includes elevator proximity detection, contextual action, ninth/tenth-floor transitions, scene-membership updates, and persisted destination.
Exclusions
- VR/controller navigation and generated-apartment review are excluded.
Acceptance outcomes
- Elevator proximity exposes the floor-change action only when applicable.
- Activating the action moves the user to the target floor entry point.
- Real-time scene membership changes with the floor.
- The new floor becomes the location resumed later.
Dependencies
Risks
- The implemented floor set and entry points are fixed and require explicit expansion rules.
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.