jarvis-at-skic
3a2e19fc52
4.3 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-17 — Orient with the live floor map | Enable a user to open a floor map, locate themselves, identify coworkers and occupied seats, and pan or zoom to understand the surrounding workplace. |
Orient with the live floor map
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-17 |
3DARCH-EP-3 — Navigate and Explore the Virtual Workplace | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a user to open a floor map, locate themselves, identify coworkers and occupied seats, and pan or zoom to understand the surrounding workplace.
User or operator problem
Users need a compact spatial reference for locating themselves, coworkers, and occupied seating.
Expected value
Reduces disorientation and supports informed navigation and seating decisions.
Scope
Includes current-floor geometry, local/coworker markers, seating state, occupant identity, pan, and cursor-centred zoom.
Exclusions
- VR/controller navigation and generated-apartment review are excluded.
Acceptance outcomes
- The map represents the current floor geometry.
- The local user and coworkers appear with distinguishable markers and names.
- Seats show available/occupied state and occupant identity at the supported zoom level.
- Pan and cursor-centred zoom retain usable orientation.
Dependencies
Risks
- Map markers can become stale when presence or seating events are missed.
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.