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:
@@ -1,8 +1,14 @@
|
||||
---
|
||||
title: "3DARCH-EP-6 Features"
|
||||
description: "Review Features governed by 3DARCH-EP-6."
|
||||
description: "Review the governed Features beneath 3DARCH-EP-6."
|
||||
---
|
||||
|
||||
# Review 3DARCH-EP-6 Features
|
||||
|
||||
No child Features have been defined or approved for this Epic. Feature discovery must preserve the [3DARCH-EP-6 boundary](../3darch-ep-6.md) and requires a separate human **Approved for Solution** decision before Architecture solution work begins.
|
||||
These Features decompose the [3DARCH-EP-6 boundary](../3darch-ep-6.md) into non-overlapping user and operator outcomes grounded in the frozen legacy revision.
|
||||
|
||||
- [3DARCH-FT-23 — Discover seat availability and occupant identity](./features/3darch-ft-23.md)
|
||||
- [3DARCH-FT-24 — Manage one daily seat reservation](./features/3darch-ft-24.md)
|
||||
- [3DARCH-FT-25 — Expire stale seat claims at the workplace-day boundary](./features/3darch-ft-25.md)
|
||||
|
||||
Documentation approval does not grant **Approved for Solution** or implementation approval.
|
||||
|
||||
@@ -0,0 +1,86 @@
|
||||
---
|
||||
title: "3DARCH-FT-23 — Discover seat availability and occupant identity"
|
||||
description: "Enable a person to distinguish available and occupied chairs in the 3D office and map before attempting to claim a place."
|
||||
---
|
||||
|
||||
# Discover seat availability and occupant identity
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-23` | [3DARCH-EP-6 — Coordinate Shared Workplace Seating](../../3darch-ep-6.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to distinguish available and occupied chairs in the 3D office and map before attempting to claim a place.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
People need to know which nearby seats are available and who occupies the others before acting.
|
||||
|
||||
## Expected value
|
||||
|
||||
Prevents unnecessary claim attempts and aligns 3D and map occupancy information.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes nearby-chair availability, occupant identity, map parity, and live claim/release/reset updates.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Advance booking, recurring reservations, administrator override, and historical occupancy reporting are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] Nearby chairs expose their current availability.
|
||||
- [ ] Occupied chairs show the occupant's identity in the 3D scene.
|
||||
- [ ] The floor map uses the same occupancy state and can reveal occupant names.
|
||||
- [ ] Live claim/release/reset changes update both views without a reload.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-17 — Orient with the live floor map](../../3darch-ep-3/features/3darch-ft-17.md)
|
||||
- [3DARCH-FT-19 — Recognize coworkers by workplace identity](../../3darch-ep-4/features/3darch-ft-19.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- The legacy client bulk-reset listener does not correctly consume the server reset payload.
|
||||
|
||||
## 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-23/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/interactables/ChairOverlay.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/interactables/ChairOverlay.tsx)
|
||||
- [`apps/nebula/src/components/Map/components/MapSeatLayer.tsx`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/components/Map/components/MapSeatLayer.tsx)
|
||||
- [`apps/nebula/src/stores/chairStore.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/stores/chairStore.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-23 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-23."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-23 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-23](../3darch-ft-23.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-24 — Manage one daily seat reservation"
|
||||
description: "Enable a person to claim an available nearby seat, move the reservation to another seat, release it, and trust that another user's reservation cannot be displaced."
|
||||
---
|
||||
|
||||
# Manage one daily seat reservation
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-24` | [3DARCH-EP-6 — Coordinate Shared Workplace Seating](../../3darch-ep-6.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable a person to claim an available nearby seat, move the reservation to another seat, release it, and trust that another user's reservation cannot be displaced.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
A person needs to claim, move, or release one seat without displacing another user’s reservation.
|
||||
|
||||
## Expected value
|
||||
|
||||
Provides one authoritative daily reservation outcome with visible success or failure.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes contextual claim/release actions, one-seat enforcement, atomic reservation moves, ownership protection, broadcast updates, and user feedback.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Advance booking, recurring reservations, administrator override, and historical occupancy reporting are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] A contextual action offers claim or release according to proximity, occupancy, and ownership.
|
||||
- [ ] A user can hold at most one seat; claiming another moves the reservation atomically.
|
||||
- [ ] Another user's occupied seat cannot be claimed or released.
|
||||
- [ ] Claim, change, and release outcomes are visible to all affected participants.
|
||||
- [ ] Success and failure are communicated to the initiating user.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-9 — Enterprise sign-in and session continuity](../../3darch-ep-2/features/3darch-ft-9.md)
|
||||
- [3DARCH-FT-23 — Discover seat availability and occupant identity](./3darch-ft-23.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- Concurrent claims and reconnects require authoritative ownership checks to prevent inconsistent occupancy.
|
||||
|
||||
## 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-24/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/usePlayerActions.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/hooks/usePlayerActions.ts)
|
||||
- [`apps/nebula/src/stores/chairStore.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/src/stores/chairStore.ts)
|
||||
- [`apps/singularity/src/routes/seat.routes.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/routes/seat.routes.ts)
|
||||
- [`apps/singularity/prisma/schema.prisma`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/prisma/schema.prisma)
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "3DARCH-FT-24 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-24."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-24 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-24](../3darch-ft-24.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,88 @@
|
||||
---
|
||||
title: "3DARCH-FT-25 — Expire stale seat claims at the workplace-day boundary"
|
||||
description: "Enable participants to start each workplace day with stale reservations cleared rather than blocked by people who did not manually release yesterday's seats."
|
||||
---
|
||||
|
||||
# Expire stale seat claims at the workplace-day boundary
|
||||
|
||||
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|
||||
|---|---|---|---|---|---|
|
||||
| `3DARCH-FT-25` | [3DARCH-EP-6 — Coordinate Shared Workplace Seating](../../3darch-ep-6.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |
|
||||
|
||||
## Description
|
||||
|
||||
Enable participants to start each workplace day with stale reservations cleared rather than blocked by people who did not manually release yesterday's seats.
|
||||
|
||||
## User or operator problem
|
||||
|
||||
The workplace needs stale seat claims cleared at a predictable day boundary without manual cleanup.
|
||||
|
||||
## Expected value
|
||||
|
||||
Restores fair seat availability each workplace day and makes reset failures diagnosable.
|
||||
|
||||
## Scope
|
||||
|
||||
Includes an explicit timezone/boundary, authoritative claim clearing, single multi-replica execution, client replacement, failure visibility, and safe retry.
|
||||
|
||||
### Exclusions
|
||||
|
||||
- Advance booking, recurring reservations, administrator override, and historical occupancy reporting are excluded.
|
||||
|
||||
## Acceptance outcomes
|
||||
|
||||
- [ ] The governing workplace timezone and daily reset boundary are explicit.
|
||||
- [ ] Every active claim becomes available with occupant and claim time cleared.
|
||||
- [ ] Available seats remain unchanged.
|
||||
- [ ] Only one reset is applied when the service has multiple replicas.
|
||||
- [ ] Connected clients replace their occupancy state from the authoritative reset without reloading.
|
||||
- [ ] A missed or failed reset is visible and can be retried safely.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- [3DARCH-FT-23 — Discover seat availability and occupant identity](./3darch-ft-23.md)
|
||||
- [3DARCH-FT-24 — Manage one daily seat reservation](./3darch-ft-24.md)
|
||||
|
||||
## Risks
|
||||
|
||||
- The reset timezone, multi-replica coordination, failure visibility, and client refresh behavior are incomplete.
|
||||
|
||||
## 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-25/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/jobs/seat-reset.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/jobs/seat-reset.ts)
|
||||
- [`apps/singularity/src/test/jobs/seat-reset.test.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/test/jobs/seat-reset.test.ts)
|
||||
- [`packages/utils/constants/src/socket.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/packages/utils/constants/src/socket.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-25 Tasks"
|
||||
description: "Review canonical implementation Tasks governed beneath 3DARCH-FT-25."
|
||||
---
|
||||
|
||||
# Review 3DARCH-FT-25 Tasks
|
||||
|
||||
No canonical implementation Tasks have been defined for [3DARCH-FT-25](../3darch-ft-25.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