docs: publish legacy feature catalogue
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
Build and publish 3D Architecture Wizzard documentation / build (pull_request) Successful in 22s
This commit is contained in:
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "3DARCH-FT-18 — See who shares the current floor"
|
||||
description: "Enable a participant to see coworkers join, remain present, change floors, and leave within the same scene-scoped workplace context."
|
||||
---
|
||||
|
||||
# See who shares the current floor
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-18` | [3DARCH-EP-4 — Experience Live Co-Presence](../../3darch-ep-4.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a participant to see coworkers join, remain present, change floors, and leave within the same scene-scoped workplace context.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Participants need an accurate view of who currently shares their floor as people join, move, and disconnect.
|
||||
|
||||
## Expected value
|
||||
|
||||
Makes the shared environment reflect current floor membership without requiring reloads.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes initial current-floor membership plus real-time join, floor-change, and disconnect reconciliation.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Communication content and seat-reservation ownership are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Joining returns the existing people on the participant's current floor.
|
||||
- [ ] New arrivals appear without reloading.
|
||||
- [ ] Floor changes remove a person from the previous floor and add them to the destination floor.
|
||||
- [ ] Disconnects remove stale participants from the shared scene.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-9 — Enterprise sign-in and session continuity](../../3darch-ep-2/features/3darch-ft-9.md)
|
||||
- [3DARCH-FT-13 — Enter and resume the last workplace location](../../3darch-ep-3/features/3darch-ft-13.md)
|
||||
- [3DARCH-FT-16 — Travel between workplace floors](../../3darch-ep-3/features/3darch-ft-16.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Join, floor-change, and disconnect event ordering can temporarily duplicate or retain 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-18/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/singularity/src/socket-server/event-handlers.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/socket-server/event-handlers.ts)
|
||||
- [`apps/singularity/src/socket-server/scene-manager.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/socket-server/scene-manager.ts)
|
||||
- [`apps/singularity/src/socket-server/broadcast-service.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/socket-server/broadcast-service.ts)
|
||||
- [`apps/nebula/src/socket-client.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/socket-client.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-18 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-18."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-18 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-18](../3darch-ft-18.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "3DARCH-FT-19 — Recognize coworkers by workplace identity"
|
||||
description: "Enable a participant to recognize each current-floor coworker by persisted avatar and visible name in both the 3D scene and map."
|
||||
---
|
||||
|
||||
# Recognize coworkers by workplace identity
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-19` | [3DARCH-EP-4 — Experience Live Co-Presence](../../3darch-ep-4.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a participant to recognize each current-floor coworker by persisted avatar and visible name in both the 3D scene and map.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
Participants need to recognize each coworker consistently across the 3D scene and floor map.
|
||||
|
||||
## Expected value
|
||||
|
||||
Provides stable social recognition across scene and map representations.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes persisted avatar selection, safe avatar fallback, visible names, map labels, and identity-change reconciliation.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Communication content and seat-reservation ownership are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Every current-floor participant renders as one embodied avatar.
|
||||
- [ ] The persisted avatar is used when valid, with a safe fallback for an unavailable model.
|
||||
- [ ] A visible name label follows each remote avatar.
|
||||
- [ ] The floor map shows labeled coworker markers and distinguishes the local participant.
|
||||
- [ ] Identity changes propagate without creating a duplicate participant.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-10 — First-entry avatar onboarding](../../3darch-ep-2/features/3darch-ft-10.md)
|
||||
- [3DARCH-FT-18 — See who shares the current floor](./3darch-ft-18.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Missing avatar models and delayed profile changes can reduce reliable coworker recognition.
|
||||
|
||||
## 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-19/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/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/components/Scene.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/Scene.tsx)
|
||||
- [`apps/nebula/src/components/Map/components/MapPlayerLayer.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/Map/components/MapPlayerLayer.tsx)
|
||||
- [`packages/utils/types/src/player.types.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/types/src/player.types.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-19 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-19."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-19 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-19](../3darch-ft-19.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "3DARCH-FT-20 — Follow coworker movement and activity in real time"
|
||||
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."
|
||||
---
|
||||
|
||||
# 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](../../3darch-ep-4.md) | `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-ep-3/features/3darch-ft-14.md)
|
||||
- [3DARCH-FT-18 — See who shares the current floor](./3darch-ft-18.md)
|
||||
- [3DARCH-FT-19 — Recognize coworkers by workplace identity](./3darch-ft-19.md)
|
||||
|
||||
## 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.
|
||||
|
||||
- [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-20/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/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/usePlayerAnimations.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/hooks/usePlayerAnimations.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)
|
||||
- [`packages/utils/types/src/player.types.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/types/src/player.types.ts)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-20 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-20."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-20 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-20](../3darch-ft-20.md). Architecture must first receive a separate human **Approved for Solution** decision, derive requirements and readiness evidence, and then register any resulting Tasks through Scope governance.
|
||||
Reference in New Issue
Block a user