mail-address-semantics/workplans/MAS-WP-0014-finalize-mode-contract.md
repo-manager 480e69a62e repo.work.assign_missing_identifiers
source: repo-manager
reason: deterministic projection registration

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5787@bnt-lap001
Assistant-Session: 5db26b82-138b-40cc-9856-4d5eb0f752fd
2026-10-19 13:35:11 +02:00

1.5 KiB

id type title domain repo status owner topic_slug created updated origin origin_ref state_hub_workstream_id
MAS-WP-0014 workplan Finalize mode contract v0.1: an independent email side communication mail-address-semantics backlog claude coulomb-social 2026-10-19 2026-10-19 residual MAS-WP-0009 a37bd634-25d8-504e-bf52-9b6de53b4cef

Finalize mode contract v0.1

Residual of MAS-WP-0009. The founder decided on 2026-10-19 that mode contract v0.1 stays a draft. Its master side is validated independently (impl/js/src/master.mjs passes the slave-setup flows), but the email side exists only in Python (mas_modes.email_mode).

An independent email side, or a real integration

id: MAS-WP-0014-T01
status: wait
priority: low
state_hub_task_id: "851411f7-ec90-5184-90a7-51a75eb3d856"

Do one of these. Either build an email side independent of mas_modes.email_mode, in another language or by another team, that passes mas-modes-v0.1-spec/conformance/flows.json (both roles) from the bundle alone. Or run a real outside master or mode integration (a CMS, ticketing, telephony) against the contract and record the findings. Fold the findings into CONTRACT.md as proposals, as SCP-9 did for v0.2.

Declare final

id: MAS-WP-0014-T02
status: wait
priority: low
state_hub_task_id: "63e4028d-ff57-5855-92d5-fa6ece0382c2"

With the findings folded in, ask the founder to declare mode contract v0.1 final. Then remove "draft" from the bundle and v0.2 §7.1.