jarvis-at-skic
3a2e19fc52
4.2 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-18 — See who shares the current floor | Enable a participant to see coworkers join, remain present, change floors, and leave within the same scene-scoped workplace context. |
See who shares the current floor
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-18 |
3DARCH-EP-4 — Experience Live Co-Presence | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a participant to see coworkers join, remain present, change floors, and leave within the same scene-scoped workplace context.
User or operator problem
Participants need an accurate view of who currently shares their floor as people join, move, and disconnect.
Expected value
Makes the shared environment reflect current floor membership without requiring reloads.
Scope
Includes initial current-floor membership plus real-time join, floor-change, and disconnect reconciliation.
Exclusions
- Communication content and seat-reservation ownership are excluded.
Acceptance outcomes
- Joining returns the existing people on the participant's current floor.
- New arrivals appear without reloading.
- Floor changes remove a person from the previous floor and add them to the destination floor.
- Disconnects remove stale participants from the shared scene.
Dependencies
- 3DARCH-FT-9 — Enterprise sign-in and session continuity
- 3DARCH-FT-13 — Enter and resume the last workplace location
- 3DARCH-FT-16 — Travel between workplace floors
Risks
- Join, floor-change, and disconnect event ordering can temporarily duplicate or retain participants.
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.