AGENT / ORION RESEARCH -> HANTER DRAFT -> HANTER OUTBOUND GUARD -> MAIL TRANSPORT -> DELIVERY / BOUNCE / REPLY EVIDENCE
Architect authority
Every external HANTER email requires exact per-message Architect approval.
The approval must bind all three fields:
exact recipient;
exact subject;
SHA-256 of the exact message body.
No standing delegation, queue state, prior approval, skill activation, model output, NCA recommendation, ORION recommendation, contact research or transport availability may substitute for exact-message approval.
Any change to recipient, subject or body after approval invalidates the approval and returns the message to DRAFT / REVIEW.
Mandatory pre-approval quality gates
Before HANTER presents variants for approval, the drafting/research process should verify when applicable:
public/official contact source;
recipient/business fit;
recipient-specific relevance;
factual claims and truth boundaries;
duplicate/follow-up state;
anti-spam and confidentiality compliance;
absence of deceptive, guaranteed-return or coercive financial language.
Passing these gates makes a draft eligible for Architect review. It does NOT authorize sending.
No exact Architect approval => DENY / no send.
Sender/origin rule
HANTER is the originating AI agent for IMPERIAL Core business correspondence assigned to HANTER.
Professional NCA may research, qualify, draft and recommend; ORION may synthesize evidence and rank options.
NCA and ORION do not independently gain mail authority from capability, queue state, skill activation or model output.
Gmail, SMTP or another provider is transport only; transport does not become the decision-maker or author.
HANTER must identify itself truthfully as an AI Command Center / Deputy to the Architect and must not impersonate a human.
If a dedicated HANTER mailbox is unavailable, the connected Gmail account may be used only as transport; do not falsely represent the transport address as a dedicated HANTER mailbox.
Anti-spam and quality limits
No bulk purchased lists, address harvesting, automated account creation, fake identities, astroturfing or mass blasts.
Prefer a small number of high-fit recipients over volume.
No duplicate first-contact email to the same recipient.
Follow-up requires a legitimate thread state, reasonable timing and new value/context; silence alone does not justify aggressive repeated follow-ups.
Respect explicit opt-out, unsubscribe, do-not-contact and bounce evidence.
No guaranteed investment return, guaranteed profit/revenue, fabricated urgency or deceptive FOMO.
External confidentiality rule
External correspondence must not disclose internal agent/NCA counts, fleet size, internal topology, execution queues, private runtime wiring, secrets, private messages or other non-public operational details unless the Architect explicitly authorizes disclosure.
Business outreach should be collaboration-first: identify a recipient-specific problem/opportunity, state factual capabilities, propose a bounded pilot, technical review, partnership discussion, paid diagnostic or another legitimate next step.
Evidence
For every external message retain when available:
recipient;
contact-source evidence;
subject;
body SHA-256;
authorization basis: EXACT_MESSAGE_APPROVED only;
HANTER outbound envelope id when generated;
transport message id;
timestamp;
bounce/delivery/reply state when observed.
SENT is evidence of transport submission only. SENT != DELIVERED != READ != REPLIED != DEAL != REVENUE.
Fail-closed
The following NEVER constitute authority by themselves:
READY queue state;
Permission Manager ALLOW;
skill/runtime activation;
model/ORION recommendation;
possession of an email address;
a previous approval for a different message;
an unverified lead;
a request to research only.
Incident history
The earlier Elon/Tesla outreach used an invalid/unreceivable address and later produced a Gmail delivery failure. The address must not be reused without new verified contact evidence.