Repository navigation
docs(traceai): TypeSafe (Jev) decision tracing (TH-8322) - #977
Merged
Merged
Conversation
New page /docs/integrations/traceai/typesafe for traceAI-typesafe (traceAI PR #264): install, env vars, register + instrument, sync and async System One calls, span contents (EVALUATOR, per-question noul / choice / score / box attributes, models, usage), privacy (traceAI TraceConfig convention), errors and retries, not supported, troubleshooting, and how it differs from TH-8183 and traceAI-openai. examples/traceai/typesafe: app.py (the page's code), a local System One stand-in shaped like TypeSafe's published OpenAPI document, run_e2e.sh (stand-in, privacy comparison, real-API invalid-key probe) and tests. No navigation.ts change; the nav PR adds the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 16, 2026
Real api.typesafe.ai run (typesafe-sdk 0.7.5, jev-1.13.0): trace ids, fi_verify excerpt, privacy scan. Drop the no-key/alpha warning; keep STANDIN for the default local run and the paths not seen live (429, box, assets). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…t install (TH-8322) The page goes live only after traceAI-typesafe 0.1.0 is on PyPI. Removes the git+ install Note pinned to traceAI#264's old commit. run_e2e.sh now installs traceAI-typesafe==0.1.0 by default (TRACEAI_TYPESAFE still overrides it); the example README and requirements comment say the same. Example tests: 15 passed with the package from traceAI#264. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings the branch up to date with docs main, including the shared integrations catalog in src/lib/integrations.mjs that now drives the Integrations sidebar and directory. No conflicts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The page used MARKER and TICKET in its snippets without defining them, so the copied example did not run. The questions snippet now defines a concrete ticket, and the privacy-check marker is applied in app.py outside the excerpt the page shows. Live-verification tables, trace IDs, fi_verify output, privacy-scan results and stand-in harness instructions are engineering evidence, not setup steps, so they move out of the customer page (they remain in the example and its tests). The Python limit is now attributed to the released traceAI-typesafe 0.1.0 metadata (>=3.10,<3.14); the old fi-instrumentation-otel explanation no longer holds. The page is registered in src/lib/integrations.mjs as a traceAI model provider so it is discoverable, and a page-contract test runs in test:integrations so CI checks the snippets against app.py. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
New page TypeSafe (Jev) at
/docs/integrations/traceai/typesafefor the releasedtraceAI-typesafe0.1.0 instrumentor. Everysystem_onecall from the officialtypesafe-sdkPython client becomes oneEVALUATORspan with each noul, choice, score and box answer as attributes. Linear: TH-8322 (parent TH-8103).src/pages/docs/integrations/traceai/typesafe.mdx: install, environment, register and instrument, sync and async decisions with a concrete ticket, opening the trace, span attributes, privacy flags, errors and retries, unsupported cases, troubleshooting.src/lib/integrations.mjs: catalog entry (Model providers,traceAI SDK), which also adds the page to the Integrations sidebar.scripts/typesafe-page.test.mjs(runs intest:integrations): page snippets are exact excerpts ofexamples/traceai/typesafe/app.py, every snippet defines what it uses, the Python range matches the released package, and no engineering evidence appears on the page.examples/traceai/typesafe/: runnable companion app, local System One stand-in and tests, kept as engineering evidence and not linked from the setup steps.Versions
traceAI-typesafe0.1.0 (requires Python >=3.10,<3.14) andtypesafe-sdk0.7.5 are on PyPI. The page states Python 3.10 to 3.13 andtypesafe-sdk0.7.0 or later, below 1.0, matching the package metadata.No dependent PRs. The separate nav PR #989 is no longer needed because the catalog entry above registers the page.
🤖 Generated with Claude Code