Skip to content

Publish a signed automated-mail sender distribution #6105

Description

@devantler

🤖 Generated by the Agentic Engineer

Outcome

Package the reviewed automated sender as an independently verifiable container so the invitation-email deployment can consume exact signed bytes.

Evidence and audience

Platform #6084 delivered the sender and protocol safeguards, but no runnable distribution. The portal's invitation flow therefore still cannot consume this component through normal image admission. This is the next deployable prerequisite for #5400, while the original identity release and verified-TLS commissioning remain separate.

Hypothesis and success signal

A minimal, immutable distribution will make the sender deployable without bringing the whole mailbox service into the customer identity runtime. At merge and its main publication, the exact tested image must have a source-bound digest, verified signature and inventory. Real mail and customer sign-in are not claimed by that signal.

Scope and acceptance

  • Build the existing sender with the repository's pinned Go compiler into a minimal Linux image, with a numeric unprivileged user and complete dependency notices; preserve existing source terms.
  • Exercise the actual packaged program with fictional private inputs and SMTP peers: checked configuration, TLS/authenticated submission, sender/auth/TLS refusal and shutdown. Verify read-only execution and the shipped binary/notices.
  • Reuse the existing same-run verified image archive and main-only signing/publication controls. Publish distinct commit/run/verification-attempt locators, with digest-bound inventory and provenance; never rebuild between verification and publication. Consumers use the signed registry content digest as the immutable identity, without assuming tag immutability. A publication-only retry retains the original verified image and receipt.
  • Retain existing protocol, advisory and full CI checks. No live listener, Deployment, credential, real message, new paid service or image-admission expansion is introduced.
  • Verify main publication after protected merge. Keep Provide the business site's dedicated Email sender #5400 open for private custody, recovery, send-only policy, deployment and actual invitation delivery.

Priority: High because this removes a concrete invitation deployment prerequisite. Size: Small. Prerequisite #6082 is closed; source packaging is independent of held mail recovery and identity release. The next deployment must separately approve the exact publisher identity and private runtime inputs.

Part of #5400.

Activity

  1. moved this to 🫴 Ready in 🌊 Project Boardon Nov 12, 2026
  2. moved this from 🫴 Ready to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 12, 2026
  3. added a commit that references this issue on Nov 12, 2026
  4. moved this from 🏃🏻‍♂️ In Progress to 👀 In Review in 🌊 Project Boardon Nov 12, 2026
  5. moved this from 👀 In Review to 🚀 Ready to Merge in 🌊 Project Boardon Nov 12, 2026
  6. moved this from 🚀 Ready to Merge to ✅ Done in 🌊 Project Boardon Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions