# Mail Address Semantics (MAS) v0.2 — Specification Bundle

This bundle is MAS v0.2, final as of 2026-10-19. It extends v0.1.1 (see
`CHANGELOG.md`). Two independent implementations pass its fixtures
unchanged: `mas_core` (Python) and `impl/js` (JavaScript).

## Contents

- `SPECIFICATION.md` — normative protocol/convention text (v0.2)
- `CHANGELOG.md` — errata applied since v0.1
- `grammar/mas-v0.2.abnf` — canonical ASCII local-part grammar (unchanged from v0.1.1)
- `schema/mas-statute-v0.2.schema.json` — statute discovery document schema
- `examples/mas-statute.example.json` — example statute
- `CONFORMANCE.md` — parser/generator/statute conformance rules
- `conformance/addresses.json` — positive and negative address fixtures
- `conformance/statute-aware.json` — v0.2 stand-in, equivalence and destination-transform cases
- `reference/mas_parser.py` — small non-normative reference parser

## Profiles

- **P1 / Naming + Resource:** naming hints, `=` resource binding, `+` facet
- **P2 / Interaction:** optional `!` interaction preference
- **P3 / Economic:** reserved only; `$` and `^` have no v0.2 semantics

The normative machine grammar is deliberately ASCII-only. SMTPUTF8/Unicode
addresses may exist, but Unicode MAS semantics are not part of the canonical
grammar.

## Discovery status

`/.well-known/mas` is specified here as the intended discovery location.
RFC 8615 requires new well-known URI suffixes to be registered for general
Internet use. Until such registration exists, this path should be considered
a draft/controlled-deployment convention rather than an IANA-registered
Internet-wide well-known URI.