docs: Libraries + How-we-measure - #176
Merged
Merged
Conversation
Libraries: install and first-run code for all three runtimes, the CLI (deterministic + neural), the REST API, the playground, and the model catalog pointer — one entry point for every way to use Interscript. How we measure: where numbers come from, how to re-derive them (benchmark, tool, predictions, teachers), the corrected-number example, the cross-runtime guarantee and its measured boundary, and the negative results — plain language, no claims without a link.
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.
What
Two new docs pages, auto-listed in the docs index:
Python, Ruby; the CLI for both layers; the REST API; the in-browser
playground; where the model catalog lives
public re-derivation chain, the 4.82→5.08 correction told as the
example of the process working, the byte-parity guarantee and its
precision-scoped boundary, and the negative-results policy
Plain technical language for the API parts, plain user language for
the rest. Every claim links to its artifact.
Verification
commands, release links)