EXECUTABLE COUNTEREXAMPLE / 29

The invisible second recipient.

A target check that reads only to can miss cc and bcc. A host manifest commits every supported delivery field to one exact policy resource before the simulated tool callback.

Explore seven cases ↓Integration guide ↗

Local simulation. The prior example mapper intentionally reads only to. BCC is a normal email feature; this case tests an unapproved addition. Both paths use in-memory callbacks. No message is sent or person asked for approval.

1 → 0simulated callbacks with an unapproved BCC
7executable cases with explicit controls
0external sends or verified approvals

See every destination.

Choose a case. The two columns run the same target-bound wrapper with a to-only mapper or a complete, strict recipient manifest.

Loading the checked-in report…
01 / REPRODUCE

The to-only mapper passes

The approved primary address matches. The callback still receives an added BCC field in its frozen arguments.

02 / COMMIT

One resource for all recipients

The host builds a canonical manifest of To, CC, and BCC. Its SHA-256 becomes the exact resource in a trusted policy rule.

03 / LIMIT

The tool schema defines the scope

This adapter accepts a narrow mail argument schema. A different API or downstream redirect needs its own resolver. Content and consent remain separate.

Reproduce the comparison

The builder invokes both paths, asserts each callback count and receipt reason, then compares the published report bytes in CI.

node test/action-boundary-mail-targets.test.js
node scripts/build-mail-target-report.mjs --check
Machine report ↗Strict host adapter ↗Integration guide ↗