MAS-WP-0005 finished; residual MAS-WP-0008 (finalize v0.2)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 252470@bnt-lap001
Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241
This commit is contained in:
tegwick 2026-10-18 22:47:04 +02:00
parent 10281e07f4
commit 2123e2e4c9
2 changed files with 46 additions and 1 deletions

View file

@ -4,7 +4,7 @@ type: workplan
title: "MAS spec v0.1.1 errata and v0.2 proposals"
domain: communication
repo: mail-address-semantics
status: proposed
status: finished
owner: claude
topic_slug: coulomb-social
created: "2026-10-18"
@ -451,3 +451,12 @@ the send counter.
- T05 is complete. The reference stack now meets all of spec §14
item 10.
## Residuals
Handed off as live work records (origin: residual, origin_ref MAS-WP-0005):
- MAS-WP-0008: finalize v0.2 (wording pass, bundle conformance cases for
v0.2, release decision).
- MAS-WP-0004 (existing) carries the milter/header_checks lessons for the
Postfix profile; MAS-WP-0006 (existing) builds on
`generator.for_destination`.

View file

@ -0,0 +1,36 @@
---
id: MAS-WP-0008
type: workplan
title: "Finalize MAS v0.2"
domain: communication
repo: mail-address-semantics
status: proposed
owner: claude
topic_slug: coulomb-social
created: "2026-10-18"
updated: "2026-10-18"
origin: residual
origin_ref: MAS-WP-0005
---
# 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: todo
priority: low
```
- 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.