Files
corp-v1-3darch-documentation/scope/epics/3darch-ep-6/features/3darch-ft-23.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.1 KiB
Raw Blame History

title, description
title description
3DARCH-FT-23 — Discover seat availability and occupant identity 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 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

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.

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.