R6.1 AISL tenant and SES identity in Relay production

Plan issue R6.1, phase 6 of the community-base unification plan.

Spec: docs/plan/phase-6.md, section R6.1, in DataTalksClub/community-base. Status is tracked in docs/plan/STATUS.md there, which stays the source of truth.

Depends on: D1.3, D5.2. Do not start until every one of them is done in STATUS.md.

Process

This repository's AGENTS.md and docs/PROCESS.md govern this work. The plan says what to build and how to verify it; the repository process says how work is done here.

Spec

Repository: DataTalksClub/relay, aws-infra by pull request. Depends on: D1.3, D5.2 (and the D13 gate: four clean weeks of DTC production on Relay).

Steps

1. Record the gate evidence in the issue: DTC production start date, incident log, status
   contract screenshots for four weeks.
2. Provision organisation aisl, audience aisl, client aisl-website, senders matching
   email_classification.get_sender_for_kind (transactional, promotional, team), API key.
3. SES domain identity for aishippinglabs.com in Relay's configuration set; DKIM, SPF, DMARC.
   AISL's own SES identity stays until A6.4 completes, then is retired in aws-infra.

Verification

• canary from Relay production with the AISL sender to an owner mailbox -> delivered, DKIM pass.

Read docs/plan/phase-6.md section R6.1, docs/plan/STATUS.md, AGENTS.md, and docs/PROCESS.md first; confirm D1.3, D5.2, and the D13 gate are complete. Then review Relay's configuration and the email_classification.get_sender_for_kind entry point while preparing the aws-infra pull request. Done means the AISL organization, identities, senders, API key, SES settings, and retirement dependency are recorded and the production canary is delivered with DKIM passing.