FAQ and troubleshooting

Platform spec article

FAQ and troubleshooting

Back to Crate-to-spec anchors ◎ 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 Crate-to-spec anchors.

   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/implementation-map/crate-to-spec-anchors/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 Crate-to-spec anchors.

   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/

   Open full ADR page

3. 0003-crate-map-single-index Crate-to-spec anchor map is canonical index Accepted

   Canonical index from compiler crates to platform-spec features.

   Context

   Crate references were scattered across hubs without a single ownership surface.

   Decision

   This feature hub is the canonical map from compiler/crates/* to platform-spec features; other pages link here instead of duplicating tables.

   Consequences

   New crates require anchor rows before Standard promotion of dependent features.

   Verification anchors

   • Implementation-map articles and compiler/Cargo.toml workspace layout.

   Open full ADR page

Articles

• Contracts and edge cases Normative guarantees and known edge cases for `Crate-to-spec anchors`. article Standard
• Design model Conceptual model for `Crate-to-spec anchors` and its subsystem boundaries. article Standard
• Examples Practical examples that demonstrate `Crate-to-spec anchors` behavior. article Standard
• FAQ and troubleshooting Common questions and debugging guidance for `Crate-to-spec anchors`. article Standard
• Flow and algorithm End-to-end control flow and major algorithmic steps for `Crate-to-spec anchors`. article Standard
• Verification and traceability How `Crate-to-spec anchors` requirements map to tests and implementation anchors. 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 · 2 SpecSection(s) · 1 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

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

Related spec docs

• Area
  Implementation map

  Parent area

• Domain
  Compiler

  Crate ownership boundaries are maintained inside the compiler domain

• Area
  Conformance

  The map is enforced by tests and review policy

• Feature
  Crate-to-spec anchors

  Parent feature hub

Why did a change pass locally but fail in CI?

Most often, one crate boundary changed but the corresponding fixture or downstream consumer was not updated. Re-run the nearest conformance suite and inspect cross-crate handoff points.

Where should I start debugging?

1. Confirm the target requirement in this feature hub.
2. Step through beskid_analysis` -> parser/resolution/semantic leaves` and beskid_codegen -> lowering contract leaves.
3. Validate consumer behavior at “beskid_abiandbeskid_runtime -> execution ABI/runtime leaves.
4. Reproduce with “beskid_testsandbeskid_e2e_tests -> conformance leaves.

How do I add a new rule safely?

Document the new contract in the relevant article, update implementation in the owning crate, and add a fixture proving both happy-path and failure-path behavior.