agendas and decisions

This commit is contained in:
2026-03-24 13:42:18 +00:00
parent c66ccd7efe
commit 96f971bbe4
34 changed files with 1090 additions and 1447 deletions
-125
View File
@@ -1,125 +0,0 @@
# PBS Diagnostics Agenda
Status: Active
## Purpose
Drive the remaining discussions needed to close `11. Diagnostics Specification.md` without inventing backend or UI policy prematurely.
## Context
The diagnostics spec already fixes the minimum phase split and source-attribution baseline, but it still leaves open:
- whether diagnostic codes are mandatory in v1,
- which parts of wording are normative,
- what cross-file attribution is required for import and barrel failures,
- whether cost-facing warnings become part of conformance,
- and how backend-facing failures map back to source once lowering and PBX mapping are closed.
This agenda should keep the diagnostics contract narrow, deterministic, and implementable by more than one toolchain.
## Decisions To Produce
1. Decide the minimum normative diagnostic identity model for v1:
phase only, phase plus category, or stable machine-readable code.
2. Decide the minimum normative attribution package:
file, primary span, secondary span/note requirements, and cross-file references.
3. Decide which human-facing wording requirements are normative versus illustrative.
4. Decide whether any qualitative cost diagnostics are mandatory in v1.
5. Decide how lowering, verifier, and load-facing failures surface back into the PBS-facing diagnostics contract.
## Core Questions
1. Is a stable diagnostic code required for conformance, or is deterministic rejection phase and source attribution enough?
2. For import, barrel, and cross-module lookup failures, what exact locations must be reported?
3. Must notes and help text exist for certain classes of error, or are they optional tooling quality?
4. Which backend-originated failures remain PBS diagnostics versus artifact-tool diagnostics?
5. Are warnings part of the normative contract at all in v1, and if so which ones?
## Proposed Workshop Sequence
### Workshop 1: Diagnostic Identity and Attribution
Purpose:
- close the minimum diagnostic identity model,
- close required source-attribution fields,
- and decide cross-file attribution for import and linking failures.
Expected decisions:
- phase-only versus stable code model,
- required file/span/note package,
- and minimum cross-file reporting rules.
### Workshop 2: Wording, Notes, and Help Surface
Purpose:
- decide what human-facing wording is normative,
- whether notes/help are required anywhere,
- and where implementation freedom should remain.
Expected decisions:
- wording stability boundary,
- note/help obligations,
- and illustrative versus normative examples policy.
### Workshop 3: Cost Diagnostics and Warning Policy
Purpose:
- decide whether warnings are part of v1 conformance at all,
- and, if yes, which qualitative cost warnings become mandatory.
Expected decisions:
- warning-in-conformance yes or no,
- mandatory versus optional cost notes,
- and boundary between diagnostics and profiling/tooling.
### Workshop 4: Backend-Originated Diagnostic Mapping
Purpose:
- decide how lowering, verifier, and load-facing failures map back to the PBS-facing contract.
Expected decisions:
- PBS-facing versus artifact-facing boundary,
- source-mapping obligations for backend failures,
- and inputs needed from `12` and `15`.
## Expected Spec Material
The resulting spec work should be able to add or close sections for:
- diagnostic identity and stability,
- source attribution rules,
- cross-file attribution rules,
- optional versus required notes/help,
- warning taxonomy boundaries,
- backend-facing diagnostic mapping boundaries,
- and conformance hooks consumed by `13. Conformance Test Specification.md`.
## Non-Goals
- Designing IDE presentation, colors, or UX.
- Building a complete trap taxonomy.
- Standardizing localization.
- Freezing one internal compiler error architecture.
- Rewriting rejection rules already owned by syntax, semantics, or loader specs.
## Inputs
- `docs/pbs/specs/3. Core Syntax Specification.md`
- `docs/pbs/specs/4. Static Semantics Specification.md`
- `docs/pbs/specs/5. Manifest, Stdlib, and SDK Resolution Specification.md`
- `docs/pbs/specs/6.2. Host ABI Binding and Loader Resolution Specification.md`
- `docs/pbs/specs/7. Cartridge Manifest and Runtime Capabilities Specification.md`
- `docs/pbs/specs/10. Memory and Lifetime Specification.md`
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/12. IR and Lowering Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/15. Bytecode and PBX Mapping Specification.md`
@@ -1,143 +0,0 @@
# PBS Diagnostics Workshop 1
Status: Active
## Purpose
Run the first focused discussion for `11. Diagnostics Specification.md` on the minimum diagnostic contract:
- diagnostic identity,
- phase attribution,
- source attribution,
- and cross-file attribution for import and linking failures.
## Why This Slice First
This slice should come first because every later diagnostics discussion depends on a stable answer to:
- what one diagnostic fundamentally is,
- what metadata is guaranteed,
- and what conformance is even allowed to assert.
It should stay narrow and avoid wording or warning policy for now.
## Proposed Meeting Order
1. Reconfirm already-settled rejection and phase facts.
2. Close the minimum diagnostic identity model.
3. Close the minimum source-attribution package.
4. Close cross-file attribution for import, barrel, and linking failures.
5. Record carry-forward items for wording and warning workshops.
## Already-Settled Inputs To Reconfirm
The meeting should explicitly reaffirm:
- syntax and static semantics already define required rejection classes,
- manifest/import failures are deterministic compile-time failures,
- load-facing malformed or unauthorized host usage is deterministic,
- traps are fatal runtime outcomes rather than ordinary diagnostics,
- and stable source spans are already required at token and AST level.
These should not be reopened here.
## Decisions To Produce
1. The minimum normative identity of a diagnostic.
2. The minimum mandatory attribution fields.
3. Cross-file attribution rules for import and barrel failures.
4. The smallest stable phase vocabulary diagnostics must expose.
## Candidate Decisions
### 1. Diagnostic Identity Is Phase Plus Stable Class, Not Mandatory Numeric Code
Candidate direction:
- v1 requires deterministic phase attribution and a stable rejection class.
- A machine-readable code is allowed but not yet mandatory.
- Human wording is not the identity of the diagnostic.
Rationale:
- This keeps the contract stable without overfitting to one toolchain code system.
- It leaves room to add codes later without making v1 blocked on taxonomy design.
Alternative to discuss:
- require stable codes now because conformance and tooling benefit from them.
### 2. Minimum Attribution Package Is File, Primary Span, and Message Class
Candidate direction:
- every source-attributable diagnostic must expose:
primary file,
primary source span or location,
stable phase,
and enough human-readable content to distinguish the rejection class.
- secondary notes are optional unless another rule explicitly requires them.
Rationale:
- This matches the current draft while making the required payload explicit.
### 3. Cross-File Failures Need At Least One Primary Site And Optional Related Sites
Candidate direction:
- import failure must point primarily to the importing site,
- barrel-entry mismatch must point primarily to the barrel site,
- tools may additionally point to the unresolved or conflicting declaration site when known,
- but v1 does not require one exact note shape yet.
Rationale:
- This keeps source-facing diagnostics actionable without freezing one multi-span presentation format.
### 4. Keep A Small Stable Phase Vocabulary
Candidate direction:
- the minimum stable external vocabulary is:
syntax,
static semantics,
manifest/import resolution,
linking,
and host-binding/capability admission.
- tools may subdivide internally if they map back deterministically.
Rationale:
- This gives `13` enough oracle structure without forcing one compiler pipeline.
## Questions To Resolve In The Room
1. Is phase plus stable class enough, or should v1 require diagnostic codes now?
2. Must every cross-file failure include more than one source location?
3. Should `linking` be a diagnostics phase name directly, or only a broader `resolution` bucket?
4. Are secondary spans purely optional, or mandatory for some classes such as conflicting imports?
5. What is the minimum conformance-friendly diagnostic payload that is still implementation-neutral?
## Expected Outputs
This workshop should produce:
1. a decision record for diagnostic identity,
2. a decision record for required attribution fields,
3. a cross-file attribution policy draft,
4. and a cleanup list for `11`.
## Explicit Deferrals For Workshop 2
- wording stability,
- notes/help obligations,
- warning policy,
- and backend-originated diagnostic mapping.
## Inputs
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/14. Name Resolution and Module Linking Specification.md`
- `docs/pbs/agendas/11. Diagnostics Agenda.md`
@@ -1,113 +0,0 @@
# PBS Diagnostics Workshop 2
Status: Active
## Purpose
Run the second focused discussion for `11. Diagnostics Specification.md` on the human-facing surface:
- wording stability,
- required versus optional notes,
- help text,
- and the boundary between normative content and tooling freedom.
## Why This Slice Second
This slice should follow Workshop 1 because wording cannot be scoped responsibly until the diagnostic identity and minimum attribution package are already settled.
## Proposed Meeting Order
1. Reconfirm the identity and attribution baseline from Workshop 1.
2. Close which human-facing wording elements are normative.
3. Close whether notes and help text are ever required.
4. Close the illustrative versus normative example policy.
5. Record warning and backend mapping topics for later workshops.
## Decisions To Produce
1. The normative boundary for human-facing wording.
2. Whether notes are mandatory for any diagnostic classes.
3. Whether help text is part of the v1 contract.
4. Whether example wording in the spec is illustrative or binding.
## Candidate Decisions
### 1. Human Wording Is Illustrative Except For Distinguishing The Rejection Class
Candidate direction:
- wording does not need to be byte-for-byte stable across implementations,
- but it must remain specific enough to distinguish the rejection class,
- and it must not contradict the governing spec rule.
Rationale:
- This preserves tool freedom while keeping diagnostics usable.
### 2. Notes Are Optional By Default
Candidate direction:
- notes are optional quality features in v1,
- except where a later explicit rule may require related-location reporting for a narrow class.
Rationale:
- This keeps conformance small while leaving room for richer UX.
Alternative to discuss:
- require notes for multi-file conflicts because they are otherwise under-attributed.
### 3. Help Text Is Outside Core Conformance
Candidate direction:
- help text, suggestions, and remediation hints are encouraged,
- but not part of the normative minimum contract.
Rationale:
- This avoids binding the spec to one editorial style or educational approach.
### 4. Spec Examples Are Illustrative Unless Marked Normative
Candidate direction:
- sample messages in `11` are examples only,
- and the normative content lives in phase, attribution, and class requirements.
Rationale:
- This prevents examples from accidentally becoming the wording standard.
## Questions To Resolve In The Room
1. Should any diagnostic class require notes by default in v1?
2. Is there any value in standardizing wording templates now?
3. Should the spec reserve words like `error`, `note`, and `help` as output categories?
4. Does conformance need to inspect wording classes at all?
5. How much editorial freedom is acceptable before diagnostics stop feeling stable?
## Expected Outputs
This workshop should produce:
1. a decision record for wording stability,
2. a decision record for notes/help obligations,
3. editing guidance for future `11` examples,
4. and carry-forward items for conformance discussion in `13`.
## Explicit Deferrals For Workshop 3
- mandatory warnings,
- cost visibility taxonomy,
- and backend-originated failure mapping.
## Inputs
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/agendas/11. Diagnostics Agenda.md`
- `docs/pbs/agendas/11.1. Diagnostics Workshop 1 - Diagnostic Identity and Attribution.md`
@@ -1,127 +0,0 @@
# PBS Diagnostics Workshop 3
Status: Active
## Purpose
Run the third focused discussion for `11. Diagnostics Specification.md` on warnings and cost-facing diagnostics:
- whether warnings are part of the normative contract,
- which qualitative cost facts deserve mandatory surfacing,
- and where diagnostics stops and profiling begins.
## Why This Slice Third
This slice should come after identity and wording because warning policy is only meaningful once the baseline diagnostic surface is already stable.
It should also stay qualitative and avoid turning performance metrics into language law.
## Proposed Meeting Order
1. Reconfirm the cost facts already fixed by memory and lifetime rules.
2. Decide whether warnings are in or out of conformance.
3. Decide whether any qualitative cost diagnostics are mandatory.
4. Decide the boundary between diagnostics, linting, and profiling.
5. Record backend-mapping implications for Workshop 4.
## Already-Settled Inputs To Reconfirm
The meeting should explicitly reaffirm:
- retention-bearing `bind` is a normatively relevant cost fact,
- host-boundary crossings are normatively relevant cost facts,
- copy-versus-alias behavior is normatively relevant qualitatively,
- and exact byte counts or performance rankings are not normative.
## Decisions To Produce
1. Whether warnings are part of v1 conformance.
2. Whether any qualitative cost diagnostics are mandatory.
3. The line between core diagnostics and optional tooling enrichment.
4. Whether cost diagnostics belong in `11` alone or also in `13`.
## Candidate Decisions
### 1. Warnings Are Outside Minimum Conformance In v1
Candidate direction:
- conforming tools may emit warnings,
- but v1 does not require them for conformance.
Rationale:
- This keeps the baseline small.
- It avoids forcing one style of beginner guidance too early.
Alternative to discuss:
- require a very small mandatory warning set for high-value cost facts.
### 2. Cost Notes Are Encouraged But Optional
Candidate direction:
- tools may surface notes or warnings for:
retention-bearing `bind`,
host-boundary crossings,
and observable alias-versus-copy behavior.
- none of these are mandatory in v1 conformance.
Rationale:
- This respects the normative cost model without overcommitting on tooling policy.
### 3. Quantitative Performance Reporting Is Not Diagnostics Contract
Candidate direction:
- exact allocation counts,
- exact byte counts,
- and performance ranking remain outside the diagnostics spec.
Rationale:
- Those belong to profiling, not to language acceptance/rejection diagnostics.
### 4. Linting Remains Implementation-Defined
Candidate direction:
- style hints, performance nudges, and educational suggestions remain implementation-defined unless later promoted deliberately.
Rationale:
- This prevents `11` from becoming a general lint catalog.
## Questions To Resolve In The Room
1. Is there any warning that is valuable enough to make mandatory in v1?
2. Should cost diagnostics be notes only, warnings only, or fully tool-defined?
3. Do host-boundary warnings belong to diagnostics, SDK guidance, or both?
4. How should `13` treat optional warnings in conformance fixtures?
5. Does excluding warnings from conformance undermine the beginner-facing goals of PBS?
## Expected Outputs
This workshop should produce:
1. a decision record for warnings and conformance,
2. a decision record for cost diagnostics boundaries,
3. and follow-up notes for `13`.
## Explicit Deferrals For Workshop 4
- backend-originated error mapping,
- source maps,
- verifier/load-facing attribution,
- and artifact-tool diagnostics.
## Inputs
- `docs/pbs/specs/10. Memory and Lifetime Specification.md`
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/agendas/11. Diagnostics Agenda.md`
- `docs/pbs/agendas/11.1. Diagnostics Workshop 1 - Diagnostic Identity and Attribution.md`
@@ -1,125 +0,0 @@
# PBS Diagnostics Workshop 4
Status: Active
## Purpose
Run the fourth focused discussion for `11. Diagnostics Specification.md` on backend-originated failures:
- lowering failures,
- verifier failures,
- load-facing failures,
- and how or whether they map back into the PBS-facing diagnostics contract.
## Why This Slice Last
This slice should come last because it depends on:
- the phase vocabulary,
- the attribution baseline,
- and the lowering boundary being clearer.
It should be the point where `11` explicitly interfaces with `12`, `15`, and `19`.
## Proposed Meeting Order
1. Reconfirm the frontend diagnostics baseline already closed.
2. Sort backend-originated failure classes.
3. Decide which backend failures remain PBS-facing diagnostics.
4. Decide which failures belong only to artifact-facing tooling.
5. Decide the minimum source-mapping obligations, if any.
## Failure Classes To Sort
- lowering rejection due to unsupported semantic state,
- host-binding emission mismatch,
- verifier rejection of malformed artifact invariants,
- loader rejection directly attributable to malformed or unauthorized PBS-facing artifact usage,
- and artifact-only corruption not attributable to valid PBS source.
## Decisions To Produce
1. The boundary between PBS-facing and artifact-facing diagnostics.
2. The minimum source-mapping obligation for backend failures.
3. Whether verifier/load failures participate in `11` directly.
4. The input contract `13` may assert for these classes.
## Candidate Decisions
### 1. Only Source-Attributable Backend Failures Enter The PBS Diagnostics Contract
Candidate direction:
- if a backend failure is directly attributable to validly analyzed PBS source plus normative lowering rules, it remains part of the PBS-facing diagnostics contract,
- otherwise it is artifact-tool or implementation failure surface.
Rationale:
- This keeps PBS diagnostics user-facing rather than compiler-internal.
### 2. Verifier And Loader Failures Enter `11` Only When Userland Actionability Exists
Candidate direction:
- malformed or unauthorized host-facing artifact usage attributable to source remains in scope,
- purely artifact-internal corruption or implementation bugs remain out of scope.
Rationale:
- This matches the current draft's narrow load-facing baseline.
### 3. Source Mapping Is Useful But Minimal In v1
Candidate direction:
- v1 requires a source-facing location when the failure is source-attributable,
- but does not yet require one standardized artifact offset map or source-map format.
Rationale:
- This keeps the contract implementable while leaving room for richer tooling later.
### 4. Conformance Should Assert Only The Stable External Surface
Candidate direction:
- `13` may assert rejection phase, source attribution, and rejection class for backend-originated PBS diagnostics,
- but not one exact verifier or loader message format.
Rationale:
- This keeps conformance aligned with the rest of `11`.
## Questions To Resolve In The Room
1. Which lowering failures are legitimate user-facing diagnostics versus compiler bugs?
2. Do verifier failures need their own normative phase label, or map into linking/load-facing rejection?
3. Is one source location enough for backend-originated failures?
4. How much of artifact-facing tooling belongs in the PBS language contract at all?
5. What exactly must `13` be able to test once `12` and `15` are closed?
## Expected Outputs
This workshop should produce:
1. a decision record for backend diagnostics boundaries,
2. a source-mapping obligations note,
3. and explicit integration tasks for `11`, `12`, `13`, and `15`.
## Explicit Deferrals
- exact source-map file formats,
- artifact UI presentation,
- implementation bug reporting policy,
- and internal compiler exception handling.
## Inputs
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/12. IR and Lowering Specification.md`
- `docs/pbs/specs/15. Bytecode and PBX Mapping Specification.md`
- `docs/pbs/specs/19. Verification and Safety Checks Specification.md`
- `docs/pbs/agendas/11. Diagnostics Agenda.md`
- `docs/pbs/agendas/11.1. Diagnostics Workshop 1 - Diagnostic Identity and Attribution.md`
- `docs/pbs/agendas/11.3. Diagnostics Workshop 3 - Cost Diagnostics and Warning Policy.md`
@@ -1,116 +0,0 @@
# PBS Conformance Test Agenda
Status: Active
## Purpose
Drive the decisions needed to turn `13. Conformance Test Specification.md` into an executable conformance contract for PBS v1.
## Context
The current conformance spec already defines a source-level baseline, but it still leaves open:
- whether PBS has one conformance level or staged claims,
- how diagnostics participate in conformance,
- when artifact-level golden tests become mandatory,
- how fixtures for stdlib environments, host registries, and capability grants are modeled,
- and how compatibility promises are validated over time.
This agenda should keep conformance practical and layered so the project can evolve from frontend tests to full-toolchain claims without ambiguity.
## Decisions To Produce
1. Decide the conformance-claim model:
one level only or staged levels such as frontend-only and full toolchain.
2. Decide the normative oracle shape for diagnostics.
3. Decide when artifact-level conformance becomes required in addition to source-level behavior.
4. Decide the minimum fixture model for stdlib, host registry, capabilities, and runtime lines.
5. Decide how compatibility and regression claims are encoded in the conformance corpus.
## Core Questions
1. Is a parser plus binder implementation allowed to claim partial conformance, and under what label?
2. Do diagnostics tests assert codes, phases, spans, wording classes, or only acceptance and rejection?
3. Which lowering and host-binding invariants require golden tests once `12` and `15` are closed?
4. What is the smallest reusable fixture set that still exercises host-backed and stdlib-backed surfaces honestly?
5. How should compatibility expectations across language, stdlib, and cartridge domains be tested over time?
## Proposed Workshop Sequence
### Workshop 1: Conformance Claim Levels
Purpose:
- decide whether PBS has one conformance level or staged claims.
Expected decisions:
- claim taxonomy,
- minimum requirements for each claim,
- and naming constraints for partial implementations.
### Workshop 2: Source-Level Oracle and Diagnostic Oracle
Purpose:
- close what source-level behavior must be asserted,
- and decide how diagnostics enter conformance.
Expected decisions:
- positive versus negative suite boundaries,
- diagnostic oracle granularity,
- and minimum deterministic assertions.
### Workshop 3: Artifact-Level Conformance and Fixtures
Purpose:
- decide when artifact-level tests become mandatory,
- and close the fixture model for stdlib, registry, capability, and runtime scenarios.
Expected decisions:
- artifact-golden boundary,
- fixture strategy,
- and environment assumptions for host-backed tests.
### Workshop 4: Regression and Compatibility Matrices
Purpose:
- decide how already-published behavior claims are preserved and tested over time.
Expected decisions:
- regression corpus policy,
- compatibility-matrix expectations,
- and alignment with `17`.
## Expected Spec Material
The resulting spec work should be able to add or close sections for:
- conformance levels or claim classes,
- required positive and negative suites,
- diagnostic oracle rules,
- artifact-level oracle rules,
- fixture model and environment assumptions,
- regression and compatibility matrices,
- and acceptance criteria for claiming PBS v1 support.
## Non-Goals
- Choosing one repository layout or test framework.
- Turning benchmarks into conformance.
- Replacing the normative specs with test precedent.
- Freezing every temporary implementation quirk as a golden artifact.
## Inputs
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/12. IR and Lowering Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/15. Bytecode and PBX Mapping Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/specs/19. Verification and Safety Checks Specification.md`
@@ -1,98 +0,0 @@
# PBS Conformance Workshop 1
Status: Active
## Purpose
Run the first focused discussion for `13. Conformance Test Specification.md` on conformance claims:
- whether PBS has one conformance level or multiple claim tiers,
- what each claim means,
- and how partial implementations must describe themselves.
## Why This Slice First
This slice should come first because every later conformance workshop depends on knowing what kind of claim the tests are intended to validate.
## Proposed Meeting Order
1. Reconfirm the current source-level conformance baseline.
2. Decide whether claim levels exist.
3. Decide minimum requirements for each allowed claim.
4. Decide naming restrictions for partial implementations.
5. Record oracle and fixture consequences for later workshops.
## Decisions To Produce
1. One-level versus staged conformance model.
2. Minimum obligations per conformance claim.
3. Naming policy for partial implementations.
4. The dependency from conformance claims into compatibility policy.
## Candidate Decisions
### 1. Allow Staged Claims
Candidate direction:
- permit staged claims such as:
frontend conformance,
source-runtime conformance,
and full toolchain conformance.
Rationale:
- This lets the project evolve honestly without pretending an unfinished backend is complete.
Alternative to discuss:
- keep only one conformance level to avoid user confusion.
### 2. Each Claim Must Name What It Does Not Cover
Candidate direction:
- every partial claim must explicitly state excluded domains such as artifact emission, loader interaction, or verifier behavior.
Rationale:
- This prevents marketing-language ambiguity.
### 3. Full PBS v1 Claim Requires The Whole Active Spec Set
Candidate direction:
- only the full claim may say “PBS v1 conforming” without qualifier,
- staged claims must remain explicitly qualified.
Rationale:
- This protects the meaning of the top-level claim.
## Questions To Resolve In The Room
1. Are multiple conformance levels helpful or too confusing?
2. What exact names should staged claims use?
3. Can a parser-plus-binder implementation claim anything beyond “frontend”?
4. Must runtime execution without artifact emission count as a distinct level?
5. How does this interact with `17` compatibility labels?
## Expected Outputs
1. a decision record for claim levels,
2. a claim taxonomy draft for `13`,
3. and follow-up requirements for `17`.
## Explicit Deferrals For Workshop 2
- diagnostic oracle granularity,
- source-level suite structure,
- and artifact-level tests.
## Inputs
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/agendas/13. Conformance Test Agenda.md`
- `docs/pbs/agendas/17. Compatibility and Evolution Policy Agenda.md`
@@ -1,96 +0,0 @@
# PBS Conformance Workshop 2
Status: Active
## Purpose
Run the second focused discussion for `13. Conformance Test Specification.md` on the source-level oracle:
- positive and negative suites,
- runtime-oracle scope,
- and how diagnostics participate in conformance.
## Why This Slice Second
This slice follows claim levels because it defines the actual assertions needed for the frontend and source-runtime portions of conformance.
## Proposed Meeting Order
1. Reconfirm the claim taxonomy from Workshop 1.
2. Close the positive and negative source-level suite boundaries.
3. Close the source-level runtime oracle.
4. Close the diagnostic oracle granularity.
5. Record artifact and fixture dependencies for Workshop 3.
## Decisions To Produce
1. The exact source-level oracle categories.
2. The minimum diagnostic assertions conformance may check.
3. The distinction between acceptance/rejection tests and runtime-oracle tests.
4. The boundary between source-level conformance and artifact-level conformance.
## Candidate Decisions
### 1. Keep Source-Level Oracle As The Core Baseline
Candidate direction:
- conformance must at minimum assert parsing, rejection, binding, typing, dynamic semantics, and memory/identity behavior at source level.
Rationale:
- This matches the current maturity of the corpus.
### 2. Diagnostic Oracle Checks Stable External Fields Only
Candidate direction:
- conformance may assert:
acceptance or rejection,
diagnostic phase,
source attribution,
and stable rejection class if adopted,
- but not exact message wording.
Rationale:
- This aligns `13` to the likely direction of `11`.
### 3. Runtime Oracle Remains Language-Observable
Candidate direction:
- conformance asserts only language-observable outcomes at this stage,
- not implementation timing or internal GC behavior.
Rationale:
- This preserves portability across implementations.
## Questions To Resolve In The Room
1. Should diagnostic codes become part of the conformance oracle if `11` later adopts them?
2. Must source-level runtime tests be required for every claim level or only some?
3. How should trap behavior be asserted without over-specifying runtime internals?
4. Which negative tests belong to parsing versus static semantics versus linking?
5. How much source attribution detail is enough for conformance?
## Expected Outputs
1. a decision record for source-level oracle scope,
2. a decision record for diagnostics in conformance,
3. and suite-structure targets for `13`.
## Explicit Deferrals For Workshop 3
- artifact goldens,
- stdlib and host fixtures,
- and runtime-line environment modeling.
## Inputs
- `docs/pbs/specs/11. Diagnostics Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/agendas/11.1. Diagnostics Workshop 1 - Diagnostic Identity and Attribution.md`
- `docs/pbs/agendas/13.1. Conformance Workshop 1 - Conformance Claim Levels.md`
@@ -1,98 +0,0 @@
# PBS Conformance Workshop 3
Status: Active
## Purpose
Run the third focused discussion for `13. Conformance Test Specification.md` on artifact-level testing and fixtures:
- when artifact goldens become mandatory,
- which invariants are asserted,
- and how stdlib, host-registry, capability, and runtime fixtures are modeled.
## Why This Slice Third
This slice should come after the source-level oracle is stable and after lowering discussions have progressed enough to identify meaningful artifact obligations.
## Proposed Meeting Order
1. Reconfirm the claim taxonomy and source-level baseline.
2. Decide when artifact-level conformance becomes required.
3. Decide which artifact invariants are testable at conformance level.
4. Decide the minimum fixture model for stdlib and host-backed scenarios.
5. Record regression and compatibility consequences for Workshop 4.
## Decisions To Produce
1. The role of artifact-level conformance in PBS v1.
2. The minimum fixture model for reserved stdlib and host-backed scenarios.
3. The artifact oracle boundary between `13`, `12`, and `15`.
4. The runtime-line assumptions fixtures must encode.
## Candidate Decisions
### 1. Artifact-Level Conformance Belongs Only To Full Toolchain Claims
Candidate direction:
- frontend-only and source-runtime claims do not require artifact goldens,
- full toolchain claims do.
Rationale:
- This keeps staged conformance honest and tractable.
### 2. Conformance Should Assert Invariants, Not One Entire Binary Snapshot
Candidate direction:
- artifact tests should assert stable invariants such as presence, dedup, ordering rules, and canonical identity mappings,
- not one complete opaque binary image unless later needed.
Rationale:
- This is more robust across legitimate implementation variation.
### 3. Fixtures Must Model Real Resolved Environments
Candidate direction:
- conformance fixtures must explicitly model:
selected stdlib environment,
host registry line,
granted capabilities,
and runtime line where relevant.
Rationale:
- These affect observable acceptance and lowering behavior.
## Questions To Resolve In The Room
1. Does full conformance need binary goldens or only invariant checks?
2. What is the smallest honest fixture model for host-backed tests?
3. Should stdlib fixtures be versioned as part of the conformance corpus?
4. How much loader behavior must be simulated in conformance?
5. Which artifact guarantees are stable enough today to test?
## Expected Outputs
1. a decision record for artifact-level conformance scope,
2. a fixture model draft for `13`,
3. and integration tasks for `12`, `15`, and `17`.
## Explicit Deferrals For Workshop 4
- regression policy over time,
- compatibility-matrix assertions,
- and published behavior preservation.
## Inputs
- `docs/pbs/specs/12. IR and Lowering Specification.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/15. Bytecode and PBX Mapping Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/agendas/12.4. IR and Lowering Workshop 4 - Builtins, Host Bindings, and Artifact Invariants.md`
- `docs/pbs/agendas/13.2. Conformance Workshop 2 - Source-Level Oracle and Diagnostic Oracle.md`
@@ -1,100 +0,0 @@
# PBS Conformance Workshop 4
Status: Active
## Purpose
Run the fourth focused discussion for `13. Conformance Test Specification.md` on long-lived behavior preservation:
- regression corpus policy,
- compatibility matrices,
- and how published claims are tested over time.
## Why This Slice Last
This slice should come last because it depends on:
- claim taxonomy,
- source-level oracle,
- artifact-level scope,
- and compatibility policy direction.
## Proposed Meeting Order
1. Reconfirm the settled claim levels and oracle shapes.
2. Decide what becomes part of the regression corpus.
3. Decide how compatibility matrices are represented in tests.
4. Decide how already-published behavior claims are preserved.
5. Record final spec-integration tasks for `13` and `17`.
## Decisions To Produce
1. Regression corpus policy.
2. Compatibility-matrix testing policy.
3. The relationship between published claims and test obligations.
4. How partial claims and full claims age over time.
## Candidate Decisions
### 1. Published Behavior Claims Must Enter A Regression Corpus
Candidate direction:
- once behavior is claimed as conforming or supported, it should become regression-protected in the corpus appropriate to that claim level.
Rationale:
- This turns compatibility promises into executable checks.
### 2. Compatibility Matrices Should Be Testable, Not Only Documented
Candidate direction:
- the matrix across language line,
stdlib line,
runtime line,
and conformance claim
must have test-backed meaning where support is promised.
Rationale:
- This prevents compatibility tables from becoming marketing-only artifacts.
### 3. Retired Claims Must Be Explicitly Removed, Not Silently Forgotten
Candidate direction:
- when support is dropped, the corresponding claim and tests must be retired deliberately with migration or policy notes.
Rationale:
- This aligns conformance with compatibility governance.
## Questions To Resolve In The Room
1. What exactly enters the regression corpus: only bugs, or every published example and decision?
2. How granular should compatibility matrices be?
3. Can staged claims have separate regression corpora?
4. How are unsupported combinations represented in tests?
5. Which parts of this belong in `13` versus `17`?
## Expected Outputs
1. a decision record for regression policy,
2. a decision record for compatibility-matrix testing,
3. and a final alignment checklist between `13` and `17`.
## Explicit Deferrals
- release tooling implementation,
- repository layout for the test corpus,
- and changelog formatting.
## Inputs
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/agendas/13.1. Conformance Workshop 1 - Conformance Claim Levels.md`
- `docs/pbs/agendas/13.3. Conformance Workshop 3 - Artifact-Level Conformance and Fixtures.md`
- `docs/pbs/agendas/17.3. Compatibility Workshop 3 - Compatibility Matrices and Published Claims.md`
@@ -93,6 +93,5 @@ Rationale:
- `docs/pbs/specs/2. Governance and Versioning.md`
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/agendas/13.1. Conformance Workshop 1 - Conformance Claim Levels.md`
- `docs/pbs/decisions/Conformance Claim Levels Decision.md`
- `docs/pbs/agendas/17. Compatibility and Evolution Policy Agenda.md`
@@ -1,6 +1,6 @@
# PBS Compatibility Workshop 3
Status: Active
Status: Decision recorded
## Purpose
@@ -11,6 +11,17 @@ Run the third focused discussion for `17. Compatibility and Evolution Policy.md`
- published claims,
- and how those claims age or retire.
## Resolution Snapshot
This workshop direction is now recorded in:
- `docs/pbs/decisions/Compatibility Matrix and Published Claims Decision.md`
Integrated spec follow-up belongs to:
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
## Why This Slice Third
This slice follows domain and lifecycle policy because matrix policy is where those choices become operational.
@@ -91,7 +102,6 @@ Rationale:
- `docs/pbs/specs/13. Conformance Test Specification.md`
- `docs/pbs/specs/17. Compatibility and Evolution Policy.md`
- `docs/pbs/agendas/13.4. Conformance Workshop 4 - Regression and Compatibility Matrices.md`
- `docs/pbs/decisions/Compatibility Matrix and Published Claims Decision.md`
- `docs/pbs/agendas/17.1. Compatibility Workshop 1 - Compatibility Domains and Promise Levels.md`
- `docs/pbs/agendas/17.2. Compatibility Workshop 2 - Deprecation, Removal, and Migration Duties.md`