jarvis-at-skic
3a2e19fc52
4.3 KiB
title, description
| title | description |
|---|---|
| 3DARCH-FT-21 — Exchange floor-scoped text conversation | Enable participants on the same floor to send and receive named, timestamped messages and see recent speech represented above the sender's avatar. |
Exchange floor-scoped text conversation
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-21 |
3DARCH-EP-5 — Communicate in Spatial Context | IN_BACKLOG |
EXACT |
3D Architecture Wizzard team | No |
Description
Enable participants on the same floor to send and receive named, timestamped messages and see recent speech represented above the sender's avatar.
User or operator problem
Colocated participants need a quick written conversation channel that preserves the current floor context.
Expected value
Keeps lightweight written communication inside the participant’s immediate spatial context.
Scope
Includes opening/collapsing chat, non-empty submission, floor-scoped relay, sender/time display, scrolling, and temporary avatar speech bubbles.
Exclusions
- Direct messaging, persistence, history, recording, transcription, and cross-floor communication are excluded.
Acceptance outcomes
- The chat panel can be opened, collapsed, composed in, and scrolled.
- A sent message is relayed only to the sender's current floor.
- Messages identify the sender and time.
- A temporary speech bubble and speaking/talking state connect the message to the in-world avatar.
- Changing floors cannot present previous-floor chat as current-floor conversation.
Dependencies
- 3DARCH-FT-18 — See who shares the current floor
- 3DARCH-FT-19 — Recognize coworkers by workplace identity
Risks
- Chat is ephemeral and the legacy client can retain previous-floor messages after a floor change.
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
- Discord – Scope – Linas: original Feature request
- Discord – Scope – Linas: proceed with documented mapping
Legacy implementation evidence
The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.