agendas, decisions and specs changes
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# PBS AST Workshop 1
|
||||
|
||||
Status: Active
|
||||
Status: Closed (2026-03-05)
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -46,6 +46,16 @@ Close the top-level AST contract for `11. AST Specification.md`:
|
||||
2. Decision note on attribution minimums.
|
||||
3. Section targets for `11. AST Specification.md`.
|
||||
|
||||
## Decision Outcome (2026-03-05)
|
||||
|
||||
Decision record: `docs/pbs/decisions/AST Contract and Root Model Decision.md`.
|
||||
|
||||
1. `11` standardizes AST by observable obligations, not by one mandatory Java/in-memory class hierarchy.
|
||||
2. AST root boundary is one root per source file with deterministic child order.
|
||||
3. Nodes consumed by diagnostics or lowering must carry `file/start/end`.
|
||||
4. Mandatory v1 families are declaration/statement/expression categories for the supported source slice.
|
||||
5. Unsupported forms are deterministic reject and must not be masked by permissive synthetic AST.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `docs/pbs/specs/3. Core Syntax Specification.md`
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# PBS AST Workshop 2
|
||||
|
||||
Status: Active
|
||||
Status: Closed (2026-03-05)
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -41,6 +41,18 @@ Close AST obligations for declaration and type-facing source surfaces in fronten
|
||||
2. Decision note on declaration rejection/recovery boundaries.
|
||||
3. Fixture targets for declaration AST coverage.
|
||||
|
||||
## Decision Outcome (2026-03-05)
|
||||
|
||||
Decision record: `docs/pbs/decisions/AST Declarations and Type Surfaces Decision.md`.
|
||||
|
||||
1. Mandatory declaration families for v1 include imports, top-level `fn`, `struct`, `contract`, `service`, `error`, `enum`, `callback`, `declare const`, and declaration nodes required by barrel/linking flow.
|
||||
2. Declaration identity is preserved in AST; no premature merge/collapse of declarations (including overload sets).
|
||||
3. Declaration metadata minimums are name, declared signature/surface when applicable, stable source attribution (`file/start/end`), and required syntactic flags/attributes.
|
||||
4. AST keeps structural contract; static semantics/linking own compatibility and resolution decisions.
|
||||
5. Unsupported declaration forms are deterministic parser/AST rejection with stable diagnostics.
|
||||
6. Recovery is allowed, but recovered AST must remain structurally coherent with consistent attribution.
|
||||
7. Gate U evidence requires positive/negative declaration fixtures with AST-shape, attribution, and diagnostics assertions.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `docs/pbs/specs/3. Core Syntax Specification.md`
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# PBS AST Workshop 3
|
||||
|
||||
Status: Active
|
||||
Status: Closed (2026-03-05)
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -41,6 +41,18 @@ Close AST obligations for statement and expression surfaces, including precedenc
|
||||
2. Decision note on unsupported-form policy.
|
||||
3. Fixture targets for precedence/associativity and rejection cases.
|
||||
|
||||
## Decision Outcome (2026-03-05)
|
||||
|
||||
Decision record: `docs/pbs/decisions/AST Statements and Expressions Decision.md`.
|
||||
|
||||
1. Mandatory statement/expression node families cover the supported v1 PBS syntax slice, including `block`, `let`, `return`, expression statement, `identifier`, literals, `unary`, `binary`, `call`, and `group`.
|
||||
2. Precedence and associativity outcomes are normative via AST shape.
|
||||
3. Non-associative/forbidden chained forms are deterministic reject with stable diagnostics.
|
||||
4. AST remains structural; semantic compatibility/type rules stay in static semantics/linking.
|
||||
5. Unsupported forms are deterministic reject and cannot be masked by permissive placeholder nodes.
|
||||
6. Recovery is allowed, but recovered AST must remain structurally coherent with stable attribution.
|
||||
7. Gate U evidence requires positive/negative fixtures with AST-shape and diagnostics assertions.
|
||||
|
||||
## Inputs
|
||||
|
||||
- `docs/pbs/specs/3. Core Syntax Specification.md`
|
||||
|
||||
+13
-1
@@ -1,6 +1,6 @@
|
||||
# PBS AST Workshop 4
|
||||
|
||||
Status: Active
|
||||
Status: Closed (2026-03-05)
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -41,6 +41,18 @@ Close AST-facing diagnostics/recovery rules and Gate U evidence needed to finali
|
||||
2. Decision note on Gate U AST evidence baseline.
|
||||
3. Closure checklist for `11. AST Specification.md`.
|
||||
|
||||
## Decision Outcome (2026-03-05)
|
||||
|
||||
Decision record: `docs/pbs/decisions/AST Diagnostics, Recovery, and Gate Evidence Decision.md`.
|
||||
|
||||
1. AST-facing syntax diagnostics must remain stable by identity (`code`, `severity`, `phase`, primary attribution).
|
||||
2. Human message text is locale-dependent and not the conformance identity key.
|
||||
3. Stable i18n identity is token/template-id based, aligned with diagnostics contract fields.
|
||||
4. Recovery is allowed for continued diagnostics, but recovered AST must stay structurally coherent with consistent attribution.
|
||||
5. Recovery must not mask real syntax failure by fabricating permissive valid AST shapes.
|
||||
6. Gate U AST evidence must include valid fixtures, malformed/recovery fixtures, diagnostics assertions, and attribution assertions.
|
||||
7. Mandatory negative fixture families include unexpected tokens, missing closers, forbidden non-associative chains, and unsupported forms with deterministic rejection.
|
||||
|
||||
## Explicit Deferrals
|
||||
|
||||
- IRBackend lowering details (owned by `13`),
|
||||
|
||||
Reference in New Issue
Block a user