coulomb/mail-address-semantics
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
mail-address-semantics/mas-modes-v0.1-spec/CHANGELOG.md
tegwick 001cab57d1 Mode contract v0.1 final (MAS-WP-0014 finished) 
Founder decision after the independent JS email side. Draft markers
removed (bundle, address spec v0.2 section 7.1, reuse surface), CHANGELOG
v0.1 with MCP-1..6 and known limits. SCOPE: all workplans but MAS-WP-0007
finished.

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
2026-10-19 13:59:27 +02:00

1.2 KiB
Raw Blame History

MAS mode contract changelog

v0.1 (2026-10-19)

Declared final by the founder after the second, independent email side (MAS-WP-0014). impl/js/src/email.mjs, written from CONTRACT.md and conformance/FLOWS.md alone, passes all 22 flows. With the independent JS outside master it passes the 12 slave-setup flows with no Python contract party.

Built in MAS-WP-0010, 0011 and 0013: roles, the status machine, message types, principle 10 with one send cap that holds over it (MAS-WP-0012), peer authentication (§7), and bundle-only conformance flows.

Folded in before release (docs/mode-contract-proposals.md):

  • MCP-1: a new email-mastered case is acknowledged by mail (§3.1.1).
  • MCP-2: details are Field: value lines; questions list Field: ... (§3.1.4).
  • MCP-3: a resume mail names the terminal status and its reason or detail (§3.1.3).
  • MCP-4: case.key is chosen by email and opaque to others (§1).
  • MCP-5: error table (§5.1).
  • MCP-6: what a blocked or forwarded transfer reports and relays (§3.2.4).
  • Flow a-008 (a master commands only its own resource types).

Known limits, not gates: neither email side has run against a real CMS or telephony system yet. Evidence from such integrations goes into the next version as MCP proposals.