48 lines
1.3 KiB
Markdown
48 lines
1.3 KiB
Markdown
|
---
|
||
|
|
id: MAS-WP-0014
|
||
|
|
type: workplan
|
||
|
|
title: "Finalize mode contract v0.1: an independent email side"
|
||
|
|
domain: communication
|
||
|
|
repo: mail-address-semantics
|
||
|
|
status: backlog
|
||
|
|
owner: claude
|
||
|
|
topic_slug: coulomb-social
|
||
|
|
created: "2026-10-19"
|
||
|
|
updated: "2026-10-19"
|
||
|
|
origin: residual
|
||
|
|
origin_ref: MAS-WP-0009
|
||
|
|
---
|
||
|
|
|
||
|
|
# 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
|
||
|
|
|
||
|
|
```task
|
||
|
|
id: MAS-WP-0014-T01
|
||
|
|
status: wait
|
||
|
|
priority: low
|
||
|
|
```
|
||
|
|
|
||
|
|
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
|
||
|
|
|
||
|
|
```task
|
||
|
|
id: MAS-WP-0014-T02
|
||
|
|
status: wait
|
||
|
|
priority: low
|
||
|
|
```
|
||
|
|
|
||
|
|
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.
|