jarvis-at-skic
3a2e19fc52
4.1 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-19 — Recognize coworkers by workplace identity | Enable a participant to recognize each current-floor coworker by persisted avatar and visible name in both the 3D scene and map. |
Recognize coworkers by workplace identity
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-19 |
3DARCH-EP-4 — Experience Live Co-Presence | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a participant to recognize each current-floor coworker by persisted avatar and visible name in both the 3D scene and map.
User or operator problem
Participants need to recognize each coworker consistently across the 3D scene and floor map.
Expected value
Provides stable social recognition across scene and map representations.
Scope
Includes persisted avatar selection, safe avatar fallback, visible names, map labels, and identity-change reconciliation.
Exclusions
- Communication content and seat-reservation ownership are excluded.
Acceptance outcomes
- Every current-floor participant renders as one embodied avatar.
- The persisted avatar is used when valid, with a safe fallback for an unavailable model.
- A visible name label follows each remote avatar.
- The floor map shows labeled coworker markers and distinguishes the local participant.
- Identity changes propagate without creating a duplicate participant.
Dependencies
Risks
- Missing avatar models and delayed profile changes can reduce reliable coworker recognition.
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.