coulomb-social/workplans/CSOC-WP-0015-communication-runtime-acceptance.md
custodian-sync d983bd92cd chore(consistency): renormalize lifecycle state [auto]
Updated by fix-consistency on 2026-10-08:
  - workplan status: ready → active

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a119cf-56d0-7fa3-840b-eb8732e1db0b
2026-10-08 15:14:36 +02:00

65 lines
3 KiB
Markdown

---
id: CSOC-WP-0015
type: workplan
title: "Communication runtime, inbox operations and flow acceptance"
domain: communication
repo: coulomb-social
status: active
owner: codex
topic_slug: coulomb-social
created: "2026-10-08"
updated: "2026-10-08"
origin: residual
origin_ref: CSOC-WP-0010
state_hub_workstream_id: "38208f72-c285-56fa-be44-de9b59a4e031"
---
Residual acceptance from CSOC-WP-0010, split at the user's request. Existing implementation/release/acceptance evidence remains in the originating workplan; these tasks own the remaining concrete outputs. Source checks never grant runtime or productive acceptance.
## T01 — Admit and activate explicit transactional caller policies
```task
id: CSOC-WP-0015-T01
status: wait
priority: high
state_hub_task_id: "e87ea643-7bee-5427-b4f5-b32f20dc2f29"
```
Receiver source is implemented and image deployment recorded in EMAIL-WP-0008. EMAIL-WP-0008-T03 owns actual caller/binding/template/operation/quotas, separate token custody/delivery and original-caller transition. Product acceptance verifies the admitted integration; avoid duplicating receiver implementation or granting arbitrary app notifications.
## T02 — Establish platform sender and monitored reply/bounce ownership
```task
id: CSOC-WP-0015-T02
status: todo
priority: high
state_hub_task_id: "0604cb15-72c7-5d15-bb42-0335d4ec80df"
```
Review replacing the receiver forgejo sender with platform identity through its credential owner, then name reply/inbox/support owner and prove authorized inbound access, DNS MX/SPF/DKIM/DMARC, correlated bounce/suppression and retention. No unsolicited scans or auto responses. Existing native personal reset is accepted and stays separately evidenced.
## T03 — Complete independent ledger recovery and copy custody
```task
id: CSOC-WP-0015-T03
status: wait
priority: high
state_hub_task_id: "286e60bf-76a1-5a18-bd2c-edd9d1400c41"
```
EMAIL-WP-0007-T03/T04 and RPF-WP-0053-T05/T06 own primary archive admission/atomic credential pair, first encrypted capture/retrieval/rehearsal and monitoring. Require image/schema-bound six-table recovery, restored accepted/unknown/consumed/cancelled/suppressed/quota continuity and post-capture reconciliation; govern temporary pre-release copies.
## T04 — Establish owner-spanning browser journeys and productive flow verdicts
```task
id: CSOC-WP-0015-T04
status: todo
priority: high
state_hub_task_id: "7c718d86-8f0d-5cb2-a765-b0c07116005c"
```
Use isolated issuer/directory/local mail sink/app for UC-009/010/011. Bind exact mandatory browser nodes without production URLs/accounts or SMTP provider sends; test expired/replayed handles and tenant/client/caller denials. Future UC-012 needs a user-selected product template/caller. Preserve UC-008 manual mail distribution and UC-009 existing personal reset acceptance.
## Completion
Finish when every task above has its stated evidence and acceptance, or hand off any newly discovered residual to a live work record first. Cross-owner dependencies remain their existing canonical records.