Channels

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.

These are separate typed projections. None opens a direct route to PostgreSQL, a model server, or an insurer.

Inbound prose, attachments, mail, audio, and provider material remain hostile data. Credentials and raw client secrets stay outside Context. Local inference preserves access, retention, backup, export, and deletion duties; remote inference additionally requires the exact Context/Security privacy and egress decision.

A reviewed outbound answer pins recipient, channel, payload digest, case/product revisions, current authority, expiry, and idempotency identity. Unknown acknowledgement is reconciled before retry. Deletion closes admission, drains or contains atomic work, and removes governed local derivatives while retaining explicit legal holds and third-party custody.

The first proof admits email only. Telephone and public client routes each need separate authentication, recording, disclosure, and delivery evidence before joining it.

Return to Broker.