Repository navigation
docs(spec): mandate fp32 graph I/O in IMF v1 - #440
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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).