implements PR-19.1 normative spec propagation

This commit is contained in:
2026-03-26 19:00:29 +00:00
parent 38d8c25bba
commit 82d2bfafb8
9 changed files with 164 additions and 44 deletions
@@ -75,7 +75,8 @@ Mandatory declaration metadata on required declaration nodes includes:
1. declaration name,
2. declared signature/surface when applicable (parameters/return),
3. declaration-level syntactic flags/attributes required by later phases,
4. stable `file/start/end` attribution.
4. stable `file/start/end` attribution,
5. lifecycle-marker metadata when a declaration carries `[Init]` or `[Frame]`.
Missing required attribution or metadata on mandatory nodes is non-conformant.
@@ -91,11 +92,18 @@ The v1 AST must represent, at minimum, declaration families for:
- `error`,
- `enum`,
- `callback`,
- `declare global`,
- `declare const`,
- and declaration nodes required by barrel/linking flow.
Declaration identity must be preserved at AST boundary; implementations must not prematurely merge/collapse declarations (including overload sets).
Lifecycle-observable declarations must preserve marker metadata explicitly:
- top-level `fn` marked with `[Init]`,
- top-level `fn` marked with `[Frame]`,
- and host method signatures marked with `[InitAllowed]`.
## 9. Mandatory Statement and Expression Families
The v1 AST must represent statement/expression families for the supported core syntax slice, including at minimum:
@@ -130,7 +138,7 @@ For conformance, required diagnostic identity is keyed by stable machine fields,
## 12. Conformance and Gate U Evidence
AST conformance evidence is provided through Gate U fixtures as defined in `docs/general/specs/13. Conformance Test Specification.md`.
AST conformance evidence is provided through Gate U fixtures as defined in `docs/specs/compiler/13. Conformance Test Specification.md`.
At minimum, Gate U must include: