arrow_back Back to board
Building launch gate · 45 mins Mission: Movement Infrastructure

Supporter Channel QA

Verify signup, consent, role tags, welcome email, unsubscribe, and failure states before broad launch.

Do this now

Produce one reviewable packet.

Output

Short QA note with pass/fail, screenshots if useful, broken states, and launch recommendation.

Inputs

Join page, Listmonk, SMTP, test email, privacy note, unsubscribe flow.

Future Union needs a direct supporter channel before platform algorithms decide what people see.

Copy agent prompt

Codex / Claude Code

Agent prompt.

Download AGENTS.md
You are working for Future Union.

Action brief: Supporter Channel QA
Action URL: /control-room/actions/supporter-channel-qa/
Board lane: Building
Parent mission: Movement Infrastructure
Time box: 45 minutes
Output type: QA note

Mission:
Test the supporter channel end to end and return a pass/fail note with exact launch blockers.

Why it matters:
Future Union needs a direct supporter channel before platform algorithms decide what people see.

Inputs:
Join page, Listmonk, SMTP, test email, privacy note, unsubscribe flow.

Required output:
Short QA note with pass/fail, screenshots if useful, broken states, and launch recommendation.

Acceptance criteria:
Confirms capture, consent timestamp, role/interests, welcome email, unsubscribe, error state, and no client-side secrets.

Submission route:
Email the QA packet to hello@futureunion.local with subject `Supporter Channel QA`.

Rules:
- Use public source links for every factual claim.
- Separate facts, interpretation, caveats, and recommended action.
- Do not invent data, quotes, people, organisations, or legal claims.
- Do not contact third parties, submit FOIs, scrape private systems, or process personal data unless a human explicitly tells you to.
- Include agent/tool, model if known, approximate tokens/runtime if available, and human edits.
- Return a clean Markdown packet a human can review quickly.