Skip to content
ContractSpec
Start here

reference

SupportOS internal-note evidence

Private immutable case-note evidence without duplicating CommunicationOS message content.

field.key.label
docs.customer-support.internal-notes
field.version.label
field.type.label
field.title.label
SupportOS internal-note evidence
field.tags.label
supportos,cases,notes,communicationos,privacy
field.owners.label
field.stability.label
public

CommunicationOS remains authoritative for private note content. SupportOS stores only bounded note and evidence references, actor and case revision fencing, policy/evidence references, and an immutable timestamp. Note bodies are rejected from the semantic contract, persistence, events, telemetry, and list projection.

The compose operation is the sole exception at the transport boundary: SupportOS may forward a bounded body directly to CommunicationOS, but never persists, events, logs, traces, or returns it. Before forwarding, SupportOS persists a body-free intent bound to authenticated scope, case revision, idempotency, and a server-issued policy decision. CommunicationOS emits a redacted, intent-bound delivery that SupportOS can reconcile after crashes without recovering content.

Creation requires a server-derived workspace scope, case-write permission, idempotency, the current case revision, and a CommunicationOS verifier receipt that proves the referenced note is private and linked to the same case. Missing, mismatched, public, or unavailable verification fails closed. Lists require case-read permission, use a bounded keyset cursor, and remain pinned to a stable watermark.

Reconciliation is idempotent and explicit. Expired or revoked policy, stale case revision, mismatched scope/case/actor, and unavailable dependencies produce a visible needs-review or failed state; they never silently attach or discard a CommunicationOS note. Composer, delivery, reconciliation worker, and read paths remain behind independent global-and-workspace rollout controls.