- EmailMode slave role: master-issued case ids, events to the master, sends only on instruction or autonomous policy, transfers blocked or to a primed webhook, timeouts left to the master; principle 10 refusals reported back. - conformance/flows.json (13 flows) + mas_modes.runner; mas test runs the mode corpus (172/172). - SCP-8 / v0.2 section 7.1: !MODE requests a handoff defined by the mode contract. docs/reuse-surface.md. - Deploy image copies mas_modes (ticket service imports its mailer). 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 |
||
|---|---|---|
| .. | ||
| conformance | ||
| schema | ||
| CONTRACT.md | ||
| README.md | ||
MAS mode contract v0.1 (draft): specification bundle
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 messageschema/mas-event-v0.1.schema.json: the normalized gateway event (mas-gateway→ application, andcase.intake/case.messagepayloads)conformance/transitions.json: the status machine as dataconformance/messages.json: valid and invalid messagesconformance/flows.json: scripted flows forMAS-MODES-EMAIL-MASTERandMAS-MODES-EMAIL-SLAVEconformance/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.