Sibling articles under this feature previously restated requirements in inconsistent forms.
Incremental scheduling and determinism
Platform spec feature
Incremental scheduling and determinism
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Incremental scheduling and determinism.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/compiler-mods/incremental-scheduling-determinism/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Incremental scheduling and determinism.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_analysis/src/analysis/rules/staged/compiler/crates/beskid_lsp/
-
Incremental mod runs produced unstable ordering.
Context
Incremental mod runs produced unstable ordering.
Decision
Invalidation keys and dirty sets for mod pipelines must replay deterministically for identical inputs (Collector scope + syntax snapshot hashes).
Consequences
LSP rescan triggers share the same keys as batch compile.
Verification anchors
compiler/crates/beskid_lsp/compiler/crates/beskid_analysis/src/analysis/rules/staged/.
- Incremental scheduling and determinism - Contracts and edge cases Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
- Incremental scheduling and determinism - Design model Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
- Incremental scheduling and determinism - Examples Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
- Incremental scheduling and determinism - FAQ and troubleshooting Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
- Incremental scheduling and determinism - Flow and algorithm Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
- Incremental scheduling and determinism - Verification and traceability Cache boundaries, invalidation keys, and replay guarantees for mod outputs and Mod SDK reads.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
This feature hub defines invalidation keys, cache boundaries, and replay for mod pipelines and Mod projects.
Language alignment
Section titled “Language alignment”Maps Collector scope strategies (narrow vs workspace-wide) to concrete dependency graph width and dirty-set propagation.
Implementation anchors
Section titled “Implementation anchors”compiler/crates/beskid_analysis/src/analysis/rules/staged/— precedent for staged invalidation.compiler/crates/beskid_lsp/— incremental document models and rescan triggers.
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-MODS-0007 … D-COMP-MODS-0009); use the reader ADRs tab for expandable detail.