Repository navigation
docs(site): Thu blog — signed models on every host (v0.15.0) + 3 SEO Q&As - #159
Merged
Merged
Conversation
…Q&As Editorial for 2026-10-15: v0.15.0 signed exact-ref on Swift, Kotlin/Android, and .NET as well as native and web; breaking model_usage; ONNX packaging via traverse-cli-rs with the onnx-runner-v0.15.0 asset; ABI v3; opt-in Core ML. Caveats: traverse#1685, #1686, #1661, #1630, #1567, #1598; no host Certified. Adds Q&As: what-is-model-usage-in-traverse, how-do-i-package-an-onnx-model-for-traverse, what-happens-when-a-host-marks-a-model-package-revoked. Wired into blog index, questions hub, llms.txt. Drift fixes: Package.swift on main now pins swift-host-v0.15.0-1 (traverse#1695), not swift-host-v0.15.0; the CLI Q&A now points package-onnx at the published onnx-runner-v0.15.0 runner.wasm + sha256 (traverse#1687).
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
1 participant
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.
Thursday editorial for 2026-10-15: the planned v0.15.0 post, "Signed models on every host", plus three SEO Q&As. Claims are limited to the v0.15.0 release notes,
docs/upgrade-to-v0.15.0.md,docs/model-packaging-guide.mdat the tag, and Announcement #1683.New pages
/blog/signed-models-on-every-host.html: discover → execute → trace. Covers signed exact-ref on Swift, Kotlin/Android, and .NET (small audited boundaries, a sharedtraverse-model-host-frame, byte-identical conformance vectors, and one 21-case rights suite), the breakingmodel_usagechange, ONNX packaging (traverse-cli-rsplus theonnx-runner-v0.15.0asset and its sha256), ABI v3 prepare-once, and opt-in Core ML on Apple./questions/what-is-model-usage-in-traverse.html/questions/how-do-i-package-an-onnx-model-for-traverse.html/questions/what-happens-when-a-host-marks-a-model-package-revoked.htmlThe new pages are linked from the blog index, the questions hub, and
llms.txt.Caveats stated on the pages
modelUsageaccepts any string: traverse#1685, with the fix in #1698, not released.model verifyhas no usage flag: traverse#1686, fixed on main only.model.execute. Not Hugging Face.Drift fixes
Package.swifton main now pins theswift-host-v0.15.0-1rebuild (traverse#1695 / #1692), notswift-host-v0.15.0. Fixed in platforms, what-is-real-today, changelog, three exact-ref Q&As, andllms.txt.package-onnx's runner "isn't shipped yet". It now points to the publishedonnx-runner-v0.15.0runner.wasmand its sha256 (traverse#1687).Validation
npm run buildon Node 22 built 218 pages, including the 4 new ones.npm test: 11 pass, 0 fail.