---
title: "3DARCH-FT-14 — Move through a collision-aware 3D workplace"
description: "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](../../3darch-ep-3.md) | `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

- [3DARCH-FT-13 — Enter and resume the last workplace location](./3darch-ft-13.md)

## 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.

- [Documentation decision](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

## 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](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

## 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](./3darch-ft-14/tasks.md). No canonical implementation Tasks have been defined.

## Original source

- [Discord – Scope – Linas: original Feature request](https://discord.com/channels/1518726359512387766/1543925247361814568/1544647879111483562)
- [Discord – Scope – Linas: proceed with documented mapping](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

### Legacy implementation evidence

The Feature boundary was mined from legacy revision `c0ced47ecaf4426f47e5c2e4868677f7144b951a`.

- [`apps/nebula/src/hooks/usePlayerControls.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/hooks/usePlayerControls.ts)
- [`apps/nebula/src/hooks/usePlayerMovement.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/hooks/usePlayerMovement.ts)
- [`apps/nebula/src/components/Player.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/Player.tsx)
- [`apps/nebula/src/hooks/useSceneWithColliders.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/hooks/useSceneWithColliders.tsx)