Skip to content

docs(spec): mandate fp32 graph I/O in IMF v1 - #440

Merged
ronaldtse merged 1 commit into
mainfrom
spec/fp32-io
Nov 14, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
spec/fp32-io

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

The owner-flagged follow-up from the ts #111 close-out (models #438 documents the root cause): SPEC §3 now mandates fp32 graph I/O normatively — every ONNX graph's inputs and outputs MUST be fp32; weight tensors MAY pack to any precision; fp16-IO artifacts are nonconforming and a conforming runtime MUST reject them by name. The §3 reject list gains the non-fp32-edges clause. The matching runtime guard already ships (interscript-ts #134).

The runtime guard shipped in interscript-ts #134 (fp16 feeds rejected
with a named artifact-contract error, locked by a 1KB dual-branch
fixture); the WO17 close-out owner-flagged the SPEC line that makes
the contract normative. Weight packing stays free; the mandate is on
graph edges.
@ronaldtse
ronaldtse merged commit 3665463 into main Nov 14, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant