Channels
In plain words: Broker: Channels and views
How clients, staff and technical operators each get their own view (Business Console, Client Web, Control Panel) and how incoming messages and outgoing answers are handled safely.
- 1No view gives direct access to the database, model server or insurer.
- 2Incoming messages and attachments are treated as hostile data; credentials stay out of the briefing.
- 3The first proof admits email only; phone and public web need their own evidence.
Designed Contract only.
Words on this page, decoded click one for its card
The client, staff member, and technical operator need different views of the same work. Email, forms, telephone, and future peer envelopes carry contacts and reviewed results; the case and staff mandate stay with Broker.
| Surface | What the reader can do |
|---|---|
| Business Console | Work with cases, releases, drafts, approvals, deadlines, and corrections. |
| Client Web | Submit bounded material and see authorized records and choices. |
| AltarControl Panel | Inspect RunsJob Records, evidence, readiness, consent, and recovery. |
Each surface is a separate typed projection of permitted work. None opens a direct route to PostgreSQL, a model server, or an insurer.
Before using an incoming message, treat its prose, attachments, mail, audio, and provider material as hostile data. Keep credentials and raw client secrets outside ContextBriefing Pack. Processing locally still carries duties for access, retention, backup, export, and deletion. Remote inference adds another decision: the exact ContextBriefing Pack/Security privacy and egress policy must admit the transfer.
For delivery, bind the reviewed answer to its recipient and channel, payload digest, case/product revisions, current authority, expiry, and idempotency identity. A missing acknowledgement leaves delivery uncertain; reconcile it before retrying. This preserves the connection between what staff reviewed and what the client may actually have received.
Deletion begins by closing admission and draining or containing atomic work. It can then remove governed local derivatives while retaining explicit legal holds and an account of third-party custody.
The first proof admits email only. Telephone and public client routes must each establish their own authentication, recording, disclosure, and delivery evidence before joining it.
Return to Broker.