Roadmap search

Versions, deliverables, workstreams, tasks, and pages

Beskid

Jump to a Beskid service

Typed emitter and transforms - Verification and traceability

articleStandard

src/content/docs/platform-spec/compiler/compiler-mods/typed-emitter-and-transforms/verification-and-traceability.mdx

import SpecArticleChrome from '@beskid/beskid-ui/platform-spec/SpecArticleChrome.astro';

<SpecArticleChrome />

This article documents verification and traceability for Typed emitter and transforms.

Traceability matrix

  • Anchor: compiler/crates/beskid_analysis/src/syntax/items/ — patterns for well-formed item emission.
  • Anchor: compiler/crates/beskid_codegen/ — downstream expectations after merge.

Verification expectations

  • Merge conflicts — Tests assert two generator contributors targeting the same declaration identity emit deterministic E1836–E1850 diagnostics and leave the syntax tree unchanged (see Diagnostic code registry).
  • Lowering guard — Tests ensure lower.ready (or equivalent sequencing) never fires between partial emit and rollback.
  • Golden traces (optional) — Same as Incremental scheduling / verification when emit drives invalidation.

Review cadence

  • Update this bundle whenever public Beskid.Compiler.* shapes or host policies change.