Docs/Agents & governors

Communication rules and simulation

Screens 5.5 and 5.6 — govern outbound messages with exact-content approval, and test templates against synthetic cases before release.

PEEK Platform Administrator · PEEK Technical Reviewer

/peek/customers/tenant-a/5-6

Live walkthrough · Communication rules and simulation

Communication rules and simulation — /peek/customers/tenant-a/5-5 — /peek/customers/tenant-a/5-5

Drafting a message is distinct from sending it. Approval binds the content hash, exact recipients, destination and expiry — any change invalidates it. The PEEK preview never sends. Simulation (5.6) runs synthetic action cases with no production egress, secrets or live identity; failed critical cases block release.

5.5 · Communication Rules & Preview

Govern messages and external transmission. Open it at /peek/customers/tenant-a/5-5 (any tenant ID you can access works in place of tenant-a). The primary action is Preview communication rule, which requires communication_policy.publish or preview.use.

How 5.5 works

1. Preview synthetic outbound content and define recipient, destination, marking and exact-content approval rules

Screen 5.5 contract

Fields shown: Recipients, destination allowlist, content approval hash, sensitivity
Primary action: Preview communication rule
Required capability: communication_policy.publish or preview.use
Validation: Approval binds content hash, exact recipients, destination and expiry; changes invalidate it.
Successful outcome: Agency users see a preview before authorized sending; PEEK preview never sends.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.5.5.action (acceptance test AT-UI-5.5)
Requirements: R02, R06, R16, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, SYS12, UI-5.5

Boundary — Drafting is distinct from sending and content or recipient changes invalidate approval.

Rejected even if the browser allows it — Modify a recipient after approval or click send in PEEK preview; reject the transmission.

5.6 · Simulation & Release Review

Test actions with synthetic inputs before releasing templates. Open it at /peek/customers/tenant-a/5-6 (any tenant ID you can access works in place of tenant-a). The primary action is Release reviewed version, which requires simulation.run or agent_template.publish.

How 5.6 works

1. Run synthetic action cases, compare expected denials/approvals and submit the exact tested template for review

Screen 5.6 contract

Fields shown: Simulation fixtures, expected decisions, diff, reviewer
Primary action: Release reviewed version
Required capability: simulation.run or agent_template.publish
Validation: Simulation environment has no production egress, secrets or live execution identity. Failed critical cases block release.
Successful outcome: Record fixture, template and governor versions with results and independent release review.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.5.6.action (acceptance test AT-UI-5.6)
Requirements: R02, R06, R18, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-5.6

Boundary — Simulation cannot contact production destinations or create real side effects.

Rejected even if the browser allows it — Use a production destination in simulation; block before any network side effect.

Related guides

Governors and execution identity

Screens 5.3 and 5.4 — bound allowed operations, destinations, quotas and approvals; define who an agent runs as.

Suspend, recover and execution history

Screen 5.7 — stop agents, track cancellation, reconcile external receipts and decide resumption explicitly.