Files
corp-v1-3darch-documentation/scope/epics/3darch-ep-2/features/3darch-ft-10.md
T
jarvis-at-skic 3a2e19fc52
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
docs: publish legacy feature catalogue
2026-09-03 08:14:14 +00:00

4.0 KiB
Raw Blame History

title, description
title description
3DARCH-FT-10 — First-entry avatar onboarding 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 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

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.

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

Legacy implementation evidence

The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.