jarvis-at-skic
3a2e19fc52
4.0 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-14 — Move through a collision-aware 3D workplace | Enable a user to walk, run, strafe, rotate, and jump through the office with visible animation and physical boundaries. |
Move through a collision-aware 3D workplace
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-14 |
3DARCH-EP-3 — Navigate and Explore the Virtual Workplace | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable a user to walk, run, strafe, rotate, and jump through the office with visible animation and physical boundaries.
User or operator problem
Users need responsive movement through the office while respecting its physical boundaries.
Expected value
Creates a responsive, bounded traversal experience that supplies movement state to co-presence.
Scope
Includes walk, run, strafe, turn, and jump input; local animation; collider response; and movement-state publication.
Exclusions
- VR/controller navigation and generated-apartment review are excluded.
Acceptance outcomes
- Keyboard input produces responsive supported movement states.
- Movement respects floor and scene colliders.
- Walking, running, idling, jumping, and turning produce coherent local animation.
- Movement state is available to the live-presence experience.
Dependencies
Risks
- Client-originated movement and pose data require validation before they can be trusted by other 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.