git:20260725.47080ce to git:20260808.8b7af2a

11 added, 6 removed. Audit A to A.

---

name: governed-outbound

- description: Fetch one allowlisted external source, scrub personal data, obtain human authorization for the exact safe plan, and seal a provider-neutral outbound handoff without claiming delivery. Use when external content must cross a trust boundary through a separate delivery adapter.

+ description: Fetch one allowlisted source, scrub personal data, and deliver the exact safe payload through a configured provider with approval and independent readback; use plan explicitly for a handoff only.

---

# Governed Outbound

- Prepare an exact outbound handoff in this order:

+ Deliver exact scrubbed outbound content in this order:

1. `web-fetch` performs the bounded provider read and returns source readback.

2. `redact-pii` detects semantic identifiers, deterministically scrubs the content, and withholds residual content unless its final verdict is `ready`.

- 3. The approval gate runs only for a ready redaction result. It authorizes this exact downstream plan; it does not send anything.

- 4. `send-as` plans principal, audience, provider lane, and the redacted digest.

- 5. A deterministic finalizer verifies the source evidence, redaction verdict, approval, principal, audience, content digest, and plan-only completion. The Runx graph receipt seals the chain.

+ 3. A deterministic binder replaces one declared payload placeholder with the

+ scrubbed content and binds its digest to expected provider readback.

+ 4. `send-as#send` plans principal and audience, gates the consequential send,

+ performs it once, and requires independent provider readback.

- The delivery adapter remains separate. This skill never claims a message was sent or delivered, and it does not use `sign-receipt` to manufacture a second attestation for work Runx already receipts.

+ The provider adapter remains separately configured and tenant-agnostic. Missing

+ adapter authority blocks before delivery; a plan or accepted request is never

+ reported as sent. Select the explicit `plan` runner when a provider-neutral

+ handoff is the requested outcome.

## Composes

- `redact-pii#redact-pii`

- `send-as#plan`

+ - `send-as#send`

- `web-fetch#web-fetch`

## Stop conditions

- Missing or disallowed fetch inputs stop in `web-fetch`.

- `needs_review` or `blocked` redaction skips approval and planning.

- Denied or absent approval skips planning.

- A send plan whose principal, audience, or digest differs from the approved redaction fails deterministic finalization.

- Provider execution and readback must occur in the selected downstream adapter before any caller reports delivery.

## Output

`outbound_plan` records `completion: plan_only`, `provider_delivery: not_executed`, source and redaction digests, the approval reference, the bounded send plan, and the selected provider actions. The scrubbed content remains available only in the redaction step output for the authorized downstream adapter.

Inputs are `url`, `allowlist`, `channel`, `principal`, and optional `operator_context`.