Feature hub owns normative contract

Platform spec ADR

Feature hub owns normative contract

Back to FFI and extern ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Contract import syntax How extern contracts declare foreign imports and map to symbols and call shapes. article Standard Reviewed Wed May 20
• Extern attribute schema Normative Extern and per-method interop attributes for contract imports (v0.3). article Standard Reviewed Wed May 20
• FFI and extern — Verification and traceability Conformance strategy for v0.3 FFI spec (fixtures, diagnostics, ignored runtime tests). article Standard Reviewed Wed May 20

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 7 SpecSection(s) · 1 H2 heading(s)

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

Related spec docs

• Feature
  FFI and extern

  Parent feature hub

Context

v0.3 interop split author syntax from execution lowering; articles must not fork MUST tables.

Decision

This feature hub must own normative MUST/SHOULD contract text for foreign import. Sibling articles must not redefine hub requirements.

Consequences

Execution and tooling specs link here for Extern placement and attribute shape.

Verification anchors

/platform-spec/language-meta/interop/ffi-and-extern/; compiler/crates/beskid_analysis contract validation.