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
History
Exact
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
..
conformance MAS-WP-0014 T01: independent JS email side for mode contract v0.1; MCP-1..6; flow a-008 2026-10-19 13:56:53 +02:00
schema MAS-WP-0011 finished: peer authentication in mode contract v0.1 2026-10-19 11:25:24 +02:00
CHANGELOG.md Mode contract v0.1 final (MAS-WP-0014 finished) 2026-10-19 13:59:27 +02:00
CONTRACT.md Mode contract v0.1 final (MAS-WP-0014 finished) 2026-10-19 13:59:27 +02:00
README.md Mode contract v0.1 final (MAS-WP-0014 finished) 2026-10-19 13:59:27 +02:00

README.md

MAS mode contract v0.1: specification bundle

Final as of 2026-10-19. Two independent email sides pass its flows unchanged: mas_modes.email_mode (Python) and impl/js/src/email.mjs (JavaScript). See CHANGELOG.md.

How email hands a case to another communication mode, and how email works as one element of a control flow it does not own. It is versioned separately from the MAS address specification (mas-v0.2-spec/, §7).

Contents

  • CONTRACT.md: normative text (roles, transport, status machine, message types, principle 10)
  • schema/mas-modes-v0.1.schema.json: every contract message
  • schema/mas-event-v0.1.schema.json: the normalized gateway event (mas-gateway → application, and case.intake / case.message payloads)
  • conformance/transitions.json: the status machine as data
  • conformance/messages.json: valid and invalid messages
  • conformance/flows.json: scripted flows for MAS-MODES-EMAIL-MASTER and MAS-MODES-EMAIL-SLAVE, with setups and test keys; runnable from the bundle alone
  • conformance/FLOWS.md: the flow format: steps, captures and expectations
  • conformance/scenarios.json: the callback stub's scenarios
  • conformance/auth.json: signing vectors and verification cases (§7)
  • conformance/statute.json: the statute the flows run under

The reference email side, the callback stub and the stub outside master are in mas_modes/. mas test runs this bundle against them.