External communications

Facts

A definition names the facts it relies on. It never asserts them and never infers them: each value comes from the participant that is entitled to assert it.

• recipientClassrequired
• senderIdentityrequired
• recipientCountoptional
• attachmentClassoptional

Enforcement paths

Every path on which the consequence can occur is enforced, named as a bypass capable of reaching the consequence without a Decision, or declared out of scope for this action. Coverage is reported as counts — never a percentage.

0/1 enforced paths observed · 2 named bypasses · 1 outside scope · 1 declared path not implemented

Enforced

• resend-adapter

  Governed adapter in front of one hosted mail API (Resend, the first reference adapter for this action). The Decision is taken before any request is issued, the authorization is bound to a digest of the complete canonical message effect, and the provider credential is held by the governed component — the agent never holds one.

Named bypasses

• direct-provider-credentials

  A process holding its own Resend API key and calling the provider directly, bypassing the governed adapter. Aarmos observes nothing on this path.

• direct-smtp-credentials

  A process holding its own SMTP credentials submits directly to the transport. Aarmos observes nothing on this path.

Outside this action

• human-mail-client

  A person sending from their own mail client. The consequence is real, but this action governs software-generated messages, so the path is deliberately outside its scope.

Evidence

Evidence for this action is projected under a 4096-byte budget. Attribution — who asserted a fact — is never truncated; only the listed payload facts can be shortened under budget pressure.

recipientClass · senderIdentity · recipientCount · attachmentClass