tegwick
6d7bfc8a5d
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a10e2d-a5ef-7e92-b03d-b1694e915680
3.6 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| CSOC-WP-0010 | workplan | Platform email communication and personal account recovery | communication | coulomb-social | active | codex | coulomb-social | 2026-10-06 | 2026-10-06 |
User milestone
You receive a requested password-reset message from platform@coulomb.social, recover your existing tegwick account privately, and sign in to the new app. Platform invitation/notification flows then have a governed reusable sender, observable failures and a clearly owned reply inbox. Each flow gets explicit user acceptance before productive use. This is not a campaign-mail system.
First dependency: CSOC-WP-0008-T11. Deployment and mailbox-provider changes belong to NetKingdom, email-connect and railiance-platform, not this product repo. Current evidence: docs/release/platform-email-2026-10-06.md.
Establish mailbox and reusable delivery evidence
id: CSOC-WP-0010-T01
status: done
priority: high
Fresh read-only inspection: email-connect1/1 healthy, /healthz200, runtime SecretSynced, sender forgejo@coulomb.social. platform@coulomb.social existing owner custody has recorded September28 native SMTP/auth and provider-accepted test; telemetry projection currently SecretSynced. This does not prove a fresh inbox receipt or inbound operation.
Connect password reset to platform mailbox
id: CSOC-WP-0010-T02
status: progress
priority: high
NK-WP-0047 and RPF-WP-0052/CCR-2026-0035 prepare native Authelia SMTP, TLS verification, scoped ESO password-file mount and fixed consumer admission. Implement and test without credentials in code. Obtain exact founder live go/attended owner admission; validate runtime and deploy. Existing deployment approval does not authorize mailbox-access changes.
Prove personal recovery and sign-in
id: CSOC-WP-0010-T03
status: wait
priority: high
User requests a NEW reset for tegwick after SMTP activation, receives mail at the existing directory email, sets a password privately, and completes app.coulomb.social login. Confirm inbox receipt separately from provider acceptance; keep reset URLs, tokens, passwords and private mail content out of Git/Hub/chat. Close CSOC-WP-0008-T11 only after user acceptance.
Establish shared platform notification delivery
id: CSOC-WP-0010-T04
status: todo
priority: high
Extend existing email-connect with explicit caller identities, approved templates, per-caller limits, idempotent retries, suppression/bounce handling and redacted delivery states. Replace forgejo sender with platform identity only through reviewed custody and rollout. Reuse native SMTP for authentication messages, HTTP notification API for supported application templates; do not widen current user-engine-only ingress globally.
Establish reply and mailbox operations
id: CSOC-WP-0010-T05
status: todo
priority: high
Confirm who owns/reads platform inbox, reply routing, monitored bounces, inbound IMAP/provider access, retention and support procedure. Verify domain MX/SPF/DKIM/DMARC and actual inbox receipt with the provider owner. Mailbox existence or SMTP AUTH is not inbox access proof. No unsolicited mailbox scans or automatic response sends.
Register communication use cases and regression checks
id: CSOC-WP-0010-T06
status: todo
priority: high
Catalogue password reset, verification/invitation, and future user-approved notifications. Use synthetic transport fixtures; test authorized caller, invalid recipient/template, retry/idempotency, provider failure and token redaction. ReichelAg protocol distribution remains manual clipboard/email unless the user separately chooses app sending.