Skip to content

feat(WO83): GraphIoGate — fp32-only graph boundary - #337

Merged
ronaldtse merged 2 commits into
mainfrom
feat/graph-io-gate
Oct 22, 2026
Merged

ronaldtse merged 2 commits into
mainfrom
feat/graph-io-gate

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

The pipeline-side half of WO83 (the exporter-side default landed in interscript-train#138): a registry gate that opens the artifact zip and refuses fp16 at any ONNX graph input/output. Together they close the loop opened by WO79 — the exporter normalizes by default, and the publish path refuses anything that slips through.

TDD: tests written first (synthetic fp16/fp32 artifacts, including the legal fp16-weights + fp32-IO shape); the end-to-end gate-set expectation in test_pipeline_plan_gate.py gains graph_io.

Ronald Tse added 2 commits October 22, 2026 15:41
Registry gate 'graph_io': inspects the artifact zip's ONNX members and
refuses any fp16 graph input/output (weights may stay fp16 — the WO79
owner decision; ruby has no Float16 materialization and node ORT
corrupts the boundary). Tests build synthetic artifacts at both
boundaries, including the legal fp16-weights/fp32-IO shape.
@ronaldtse
ronaldtse merged commit 479e087 into main Oct 22, 2026
11 checks passed
@ronaldtse
ronaldtse deleted the feat/graph-io-gate branch October 22, 2026 08:01
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