Build and run orchestration - Verification and traceability

Platform spec article

Build and run orchestration - Verification and traceability

Back to Build and run orchestration ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (3)

1. 0001-feature-hub-authority Feature hub authority Accepted

   This feature hub owns normative MUST/SHOULD contract text for Build and run orchestration.

   Context

   Sibling articles under this feature previously restated requirements in inconsistent forms.

   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/build-pipeline/build-and-run-orchestration/index.mdx
   • article bundle under the same feature directory.

   Open full ADR page

2. 0002-spec-over-implementation-notes Specification over implementation notes Accepted

   Platform-spec text supersedes informal crate comments for Build and run orchestration.

   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_cli/src/commands/
   • compiler/crates/beskid_engine/src/jit_module.rs
   • compiler/crates/beskid_tests/src/runtime/jit.rs

   Open full ADR page

3. 0003-primary-contract-choice Primary contract for Build and run orchestration Accepted

   This feature hub defines the normative contract for **build and run orchestration** and links newcomer-oriented referenc

   Context

   This feature hub defines the normative contract for build and run orchestration and links newcomer-oriented reference articles.

   Decision

   The reference compiler must implement Build and run orchestration as documented in this feature hub and its article bundle.

   Consequences

   Changes require hub/ADR updates and verification anchor extensions.

   Verification anchors

   • compiler/crates/beskid_cli/src/commands/
   • compiler/crates/beskid_engine/src/jit_module.rs
   • compiler/crates/beskid_tests/src/runtime/jit.rs

   Open full ADR page

Articles

• Build and run orchestration - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges. article Standard
• Build and run orchestration - Design model Explains the persistent concepts, entities, and boundaries this feature relies on. article Standard
• Build and run orchestration - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths. article Standard
• Build and run orchestration - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks. article Standard
• Build and run orchestration - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation. article Standard
• Build and run orchestration - Verification and traceability Shows how the team proves this feature works and where evidence lives. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 2 H2 heading(s)

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Build and run orchestration

  Parent feature hub

This article documents verification and traceability for build and run orchestration in the reference compiler.

What this covers

For newcomers, this page explains where the contract shows up in day-to-day compiler work and which code paths are most useful first reads.

Anchored code paths

• compiler/crates/beskid_cli/src/commands/ coordinates compile, run, and doc commands.
• compiler/crates/beskid_engine/src/jit_module.rs executes JIT pipelines from compiled artifacts.
• compiler/crates/beskid_tests/src/runtime/jit.rs and e2e fixtures verify orchestration behavior.

Practical notes

• Prefer tracing from CLI/test entry points into analysis/codegen crates before changing internals.
• Treat diagnostics and tests as part of the contract, not optional implementation details.
• If behavior changes, update this article and add/adjust tests in compiler/crates/beskid_tests or compiler/crates/beskid_e2e_tests.