Definition-of-ready is met: repo pushed to both remotes, CI green on all
three jobs, openmail.karti.ai live, and all three tier-1 crates pass
cargo publish --dry-run.
Two items left open on purpose and written down rather than dropped: no
x86_64 CI job while GitHub-hosted runners are unavailable for billing, and
the repo stays private until v0.1 closes the ingest loop per ADR 0004.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkyvfNJGTshJNE9FtwPLk7
cloud-1 (phx) and cloud-2 (us-sanjose-1) are both already OCI aarch64
instances, so the open question in ADR 0005 was answerable directly rather
than by reading forum posts. Measured from cloud-2:
BLOCKED 25 gmail-smtp-in.l.google.com, aspmx.l.google.com
OPEN 587/465/2525 gmail, sendgrid, SES, OCI Email Delivery
The community reports claiming 587 and 2525 are also blocked are wrong.
Only 25 is blocked, exactly as Oracle documents, so relay works and the
launch host is viable. Inbound :25 reachability is still unverified — that
is a VCN security-list change, not a platform limit.
ROADMAP.md carries the goal, three success signals that are deliberately
not v0.1, a definition-of-ready checklist, and five standing rules.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkyvfNJGTshJNE9FtwPLk7
