coulomb/mail-address-semantics
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
mail-address-semantics/workplans/MAS-WP-0007-retire-live-test-environment.md
custodian-sync 7208eb47b4 chore(consistency): renormalize lifecycle state [auto] 
Updated by fix-consistency on 2026-10-21:
  - workplan status: backlog → active

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-21 12:25:49 +02:00

2.9 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated origin origin_ref state_hub_workstream_id
MAS-WP-0007 workplan Retire the MAS live test environment communication mail-address-semantics active claude coulomb-social 2026-10-18 2026-10-19 residual MAS-WP-0003 03751989-8ed1-5a3f-bcc3-71aef8b375a6

Retire the MAS live test environment

Residual of MAS-WP-0003. The live MX for mas.coulomb.social stays up for follow-up validation (founder, 2026-10-18), capped at 300 sent replies. Retire it once MAS-WP-0004 and MAS-WP-0005 no longer need it. Cluster-scoped and external pieces do not disappear when the namespace is deleted.

Founder decision (2026-10-19): redeploy, then keep. The MX stays up for a second deployment (MAS-WP-0009) or for live validation of the mode contract. Retirement stays in backlog.

  • 2026-10-19: redeployed mas-mx and mas-statute with image mas-live:v0.2-a95f848, side-loaded into k3s containerd. The previous image was v0.2-a45f1a1. The evidence (events.jsonl, 36 events, and tickets.sqlite3) was backed up before the rollout and is intact on the PVC. Checked: mas discover valid; the profile's relay control; TEM relay with null-sender discard; OpenDKIM/OpenDMARC running; the ticket service runs with --max-sent 300 --require-dmarc-pass; empty queue; relaying to the public IP refused with 554 (x@other, x!y@other, a@mas...@other).

  • 2026-10-19: redeployed with image mas-live:v0.2-480e69a: MAS-WP-0012's one outbound path, and v0.2 final. The evidence was backed up first. The legacy outbox was imported once into tickets-outbox.sqlite3: 9 rows, 4 sent, so 4 of 300 count toward the cap. The ticket service runs with --max-sent 300 --require-dmarc-pass --email-held-duration-max 7d --emails-held-storage-max 100MB. Checked: statute valid, 36 evidence events intact, TEM relay with null-sender discard, empty queue, relaying refused with 554. The migration was first tested in the image against a copy of the live volume.

Retire the environment

id: MAS-WP-0007-T01
status: wait
priority: medium
state_hub_task_id: "e0a65837-1769-5129-b258-fbaeb3047f62"

Run when follow-up validation is done:

  1. Export the evidence (/var/lib/mas/events.jsonl and the ticket DB from the mas-mx pod) into the repo or an archive.
  2. Delete namespace mas.
  3. Notify ops-mason to remove OpenBao role external-secrets-mas-tem-relay, policy workload-kv-read-mas-tem-relay and KV path platform/suppliers/scaleway/mas-tem-relay (MASON-WP-0014 teardown).
  4. Founder: revoke the Scaleway TEM API key and remove the TEM domain.
  5. Founder: remove the mas.coulomb.social MX, A, SPF and DKIM records at IONOS, the mas-fwd@coulomb.social forward, and the coulomb-social Google Group if no longer used.
  6. Remove the side-loaded mas-live:wp0003-* images from k3s containerd.