MAS-WP-0005-T04: split into T07-T10 (v0.2 bundle, receiving, sending, live)

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:16:50 +02:00
parent b9301786b8
commit 3709fbb54b

View file

@ -152,7 +152,7 @@ by design. Verify on the live MX by repeating the Google Groups post.
```task
id: MAS-WP-0005-T04
status: todo
status: progress
priority: medium
state_hub_task_id: "4ff67908-52c4-5106-b851-e1dec8274226"
```
@ -162,6 +162,12 @@ Draft the statute object `alternate_syntax` (enables the fixed stand-ins
the destination transforms (see SCP-6), and
`equivalence.resource_id_case`, with policy semantics and fixtures.
Split into T07 to T10 on 2026-10-18 (token budget). Stand-in recognition
lives in the policy layer, not the parser: the parser stays statute-blind,
and only a statute that enables the stand-ins gives `--`/`---` meaning.
v0.2 is a separate draft bundle `mas-v0.2-spec/`, because it adds features
rather than errata.
## SCP-5: reply only to authenticated senders
```task
@ -212,3 +218,57 @@ statute and the case-insensitive ticket service. Then re-run a smoke test
quarantined with no reply.
Sends: 3/300. Done.
## v0.2 draft bundle and version support
```task
id: MAS-WP-0005-T07
status: progress
priority: medium
```
Create `mas-v0.2-spec/` (draft): the specification with SCP-6
(`alternate_syntax`, matching order, destination transforms, informative
integration section) and the SCP-7 statute field
`equivalence.resource_id_case`, the v0.2 statute schema, and a CHANGELOG.
`mas_core` accepts statutes with `mas_version` 0.1 and 0.2, each validated
against its own schema. Discovery accepts both.
## v0.2 receiving side: stand-ins and resource_id_case in policy
```task
id: MAS-WP-0005-T08
status: todo
priority: medium
```
The policy interprets `---MODE` (interaction first, enabled mode only) and
`TYPE--ID` (declared type only) when the statute enables them, and applies
`resource_id_case: insensitive` in the equivalence key. Statute lint covers
the stand-in constraints. Statute-aware fixtures.
## v0.2 sending side: destination transforms in the generator
```task
id: MAS-WP-0005-T09
status: todo
priority: medium
```
Add a generator `destination` parameter with the five transforms. Emit the
canonical form when allowed; refuse when the namespace would not accept the
result; re-check the length after transforms. Include an example destination
profile `ionos-forward`. This is the base for the composer (MAS-WP-0006).
## v0.2 live check: IONOS forward with stand-ins
```task
id: MAS-WP-0005-T10
status: todo
priority: medium
```
Switch `mas.coulomb.social` to a v0.2 statute that enables both stand-ins
and case-insensitive ids. Repeat the IONOS forward test with
`ticket--gs-…+comments@`. It must now be correlated to the ticket.