Messages and Unified Inbox
Workspace inbox for Project-linked email, SMS, calling and in-app Conversations.
Coming soon — no routeFuture Spec 11 →Current-state summary
Messages appears in the authenticated navigation as a disabled # link with an explicit Coming soon badge. No global inbox route, Conversation list, channel queue or composer is available. Record-scoped Communication tabs exist elsewhere, but they do not constitute the Unified Inbox defined in Spec 11.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Navigation | Disabled Messages link with Coming soon badge. | Verified live |
| Conversation rail | Not implemented globally; should support assignment, status, priority, channel, tags, SLA and unread state. | Future requirement |
| Message workspace | No global thread, participant, composer, attachment, note or mention surface exists. | Verified absent |
| Context panel | No global Project, Client, Provider, Task or commercial-record context is available. | Verified absent |
| Channel health | Record Communication tabs expose partial health concepts, but no Workspace channel administration or queue is present here. | Partial behavior elsewhere |
User journeys
Current flows
Triage inbound work
- Open Unified Inbox
- Filter or claim Conversation
- Verify participants and Project context
- Reply on the authorized channel
- Add an internal Note or mention
- Create a Task or escalate
- Resolve or snooze
State model
Current and expected states
Navigation is disabled and labelled.
Not represented globally.
No reconciliation queue exists.
No global state exists.
Product rules
Non-negotiable boundaries
- Conversation is the canonical cross-channel collaboration container.
- Internal Notes and participant-visible Messages remain distinct.
- Project and participant access is re-evaluated before every view, reply and attachment download.
- Email correlation uses deterministic headers and aliases before AI suggestions.
- Calling recordings and transcripts require explicit permissions and retention.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 11 owns closure →- No route or working inbox exists.
- No email, SMS, calling or in-app queue can be verified.
- No Conversation assignment, notes, tags, mentions, SLA, search or participant controls exist globally.
Future alignment
Required evolution
- 01Implement the four-panel Unified Inbox from Spec 11.
- 02Connect all channels through shared Conversations and Messages.
- 03Add deterministic Project/Entity correlation and a governed reconciliation queue.
- 04Support internal collaboration, Task creation, notification preferences and channel health.
Current baseline
Acceptance record
- Messages remains disabled until a real route exists.
- Coming soon is visible wherever the entry point appears.
- Record Communication tabs are not misreported as a global Unified Inbox.
- Future channel claims require end-to-end evidence.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented