Follow coworker movement and activity in real time
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-20 | 3DARCH-EP-4 — Experience Live Co-Presence | IN_BACKLOG | EXACT | 3D Architecture Wizzard team | No |
Description
Enable a participant to see current-floor coworkers' synchronized position, orientation, and movement/activity animation so that the shared environment feels live rather than static.
User or operator problem
Participants need remote movement and activity to feel live and remain associated with the correct coworker.
Expected value
Makes co-presence legible through synchronized pose and activity rather than static avatars.
Scope
Includes remote position, orientation, movement/activity animation, identity association, and local/remote distinction.
Exclusions
- Communication content and seat-reservation ownership are excluded.
Acceptance outcomes
- Movement updates remain associated with the correct recognized participant.
- Position and orientation changes update smoothly for floor peers.
- Supported animation/activity state follows the remote participant.
- Local and remote representations remain distinguishable.
Dependencies
- 3DARCH-FT-14 — Move through a collision-aware 3D workplace
- 3DARCH-FT-18 — See who shares the current floor
- 3DARCH-FT-19 — Recognize coworkers by workplace identity
Risks
- Unvalidated pose and activity updates can create implausible or misleading remote 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.