--- title: "3DARCH-FT-10 — First-entry avatar onboarding" description: "Enable a first-time user to preview, rotate, zoom, choose, and persist an in-world avatar before entering the workplace." --- # First-entry avatar onboarding | Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution | |---|---|---|---|---|---| | `3DARCH-FT-10` | [3DARCH-EP-2 — Secure Access and Personal Setup](../../3darch-ep-2.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No | ## Description Enable a first-time user to preview, rotate, zoom, choose, and persist an in-world avatar before entering the workplace. ## User or operator problem First-time users need to choose an embodied workplace identity before entering the shared environment. ## Expected value Ensures every new participant enters with a persisted, recognizable in-world representation. ## Scope Includes first-entry gating, avatar preview controls, selection persistence, onboarding completion, and entry with the selected avatar. ### Exclusions - Administrator access, account recovery, display-name editing, and unwired self-service logout are excluded. ## Acceptance outcomes - [ ] An unonboarded user cannot enter the workplace before completing avatar selection. - [ ] Available avatars can be previewed from multiple viewing angles. - [ ] Confirmation persists the avatar and onboarding completion. - [ ] The selected avatar appears when the user enters. ## Dependencies - [3DARCH-FT-9 — Enterprise sign-in and session continuity](./3darch-ft-9.md) ## Risks - Reselecting the existing avatar can fail to mark onboarding complete. ## 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-10/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/App.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/App.tsx) - [`apps/nebula/src/components/CharacterSelection/CharacterSelection.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/CharacterSelection/CharacterSelection.tsx) - [`apps/singularity/src/routes/auth.routes.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/routes/auth.routes.ts) - [`apps/nebula/src/test/components/CharacterSelection.test.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/test/components/CharacterSelection.test.tsx)