tegwick
f07576451a
Founder decision after the second implementation: close the two open gaps, then declare v0.2 final. Section 13: parsers MUST reject over 64 octets (fixtures p1-050/051); section 8: equivalence is between targets, key format not normative. Draft markers removed, CHANGELOG dated 2026-10-19, MAS_VERSION 0.2, mas_conformance vendors the v0.2 addresses.json. Mode contract v0.1 stays draft: MAS-WP-0014 (independent email side). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 5787@bnt-lap001 Assistant-Session: 5db26b82-138b-40cc-9856-4d5eb0f752fd
1.3 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | origin | origin_ref |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
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
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
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.