---
id: MAS-WP-0008
type: workplan
title: "Finalize MAS v0.2"
domain: communication
repo: mail-address-semantics
status: finished
owner: claude
topic_slug: coulomb-social
created: "2026-10-18"
updated: "2026-10-19"
origin: residual
origin_ref: MAS-WP-0005
state_hub_workstream_id: "1ed0dd72-1f1f-54a3-ba41-f1396400590f"
---

# Finalize MAS v0.2

Residual of MAS-WP-0005. `mas-v0.2-spec/` is a working draft: implemented
in `mas_core` and running live on mas.coulomb.social, but not yet declared
final.

## Wording pass and release decision

```task
id: MAS-WP-0008-T01
status: done
priority: low
state_hub_task_id: "b84d5344-7679-5555-b086-55f88b2f83d7"
```

- Align the 25 remaining "v0.1" mentions in `mas-v0.2-spec/SPECIFICATION.md`
  (unchanged rules inherited from v0.1.1) and in `CONFORMANCE.md`.
- Add v0.2 statute-aware conformance cases to the bundle: the stand-in
  table (§6.3), `resource_id_case`, and the destination-transform
  refusals (§12.1). Today they live only in the repo tests.
- Founder decision: declare v0.2 final, or keep it a draft until a second
  implementation or deployment exists.

## Outcome

- Wording: rules inherited from v0.1.1 no longer say "v0.1" in
  `SPECIFICATION.md`, `CONFORMANCE.md` or `README.md`. The remaining
  mentions are historical (v0.1.1 lineage, how v0.1 statutes are treated).
- Conformance: `conformance/statute-aware.json` (29 cases: stand-in table,
  `resource_id_case` equivalence, destination results and refusals), the
  `MAS-V0.2-STATUTE-AWARE` surface in `CONFORMANCE.md`, and a vendored copy
  in `mas_conformance/`. `mas test` and pytest run it, and a drift test
  checks the copy.
- **Decision (founder, 2026-10-19): v0.2 stays a draft** until a second
  implementation or deployment exists. So far the corpus has only been run
  against the code written alongside it.
- Residual: MAS-WP-0009 (declare v0.2 final).