DRIFT v0.9.0

Tier.FINAL evidence pass — 2026-07-17

• Follow-up Codex session 019f7213-be19-7e50-92ac-a48bd5ecaacb completed the
  evidence cleanup and release-boundary synchronization on 2026-07-18.
• Executed the paid Tier.FINAL capture (gpt-5.6-sol) through the DRIFT Manual
  Run notebook. All eight configured primary sources were sampled (one item
  each); eight clusters produced verifier-passed drafts (IDs 9–16), each drafted
  and separately verified at gpt-5.6-sol.
• After source-excerpt human review, published five Insights: JAX v0.11.0 (10),
  Transformers v5.14.1 (11), vLLM v0.25.1 (13), NCCL v2.30.7-1 (15), and
  TensorRT 11.1 (16). This grows the reviewed corpus to five sources, adding
  JAX v0.11.0 — a substantive release with real breaking changes — alongside the
  four sources first published at the dev / gpt-5.6-luna tier.
• Held three verifier-passed drafts at the human-review gate rather than
  publishing them: a single PyTorch trunk commit (not a release), CUTLASS 4.6.1
  (thin evidence with an interpretive expansion of an upstream typo), and an
  out-of-tree Triton gfx950 tutorial pin (not a mainline release).
• Archived the reviewed evidence and SHA-256 integrity manifest to
  assets/evidence/2026-07-17-all-sources-reviewed.json
  (sha256 df32b3d4315b09fb4a6dbd508d381ca2c8095e25e16f88c4741ce7bc3055a337).
• Recorded a display-only results notebook at
  notebooks/drift_manual_run.sol.results.ipynb (Markdown-only; no executable
  cells, operator configuration, provider/budget logs, or review notes), kept as
  a companion to the earlier gpt-5.6-luna results record rather than replacing
  it.

Operational note

• A Tier.FINAL (gpt-5.6-sol) capture needs a higher per-attempt model timeout
  than the 20-second default; the heavier draft stage otherwise exceeds the
  timeout, exhausts its retries, and aborts the run (a non-ValueError stops the
  capture rather than skipping one cluster). Raising DRIFT_MODEL_TIMEOUT_SECONDS
  to the 120-second maximum let the eight-source capture complete. Local spend for
  the reviewed Sol run stayed within the configured spend guard.

Changed

• Rewrote the submission/DRIFT_FREEZE_PLAN.md score matrix as an honest
  current-vs-target readiness view and added a dated audit addendum; reclassified
  MCP, tool-calling, and IDE items as optional future work that is not shipped.
  Updated docs/INITIATIVES.md, docs/CODEX_PROMPTS.md, and
  submission/SUBMISSION.md, and removed the superseded
  submission/NEXT_STEPS.md.
• Renamed the tracked UI screenshots to a kebab-case set led by the reviewed
  briefing (01-briefing), claim evidence (02-briefing-claim-evidence), the
  Ask DRIFT box (03-ask-drift), two grounded-answer examples
  (04.1-ask-drift-grounded-answer-nccl-example,
  04.2-ask-drift-grounded-answer-tensorRT-example), and the branded API docs
  (05-api-docs); updated the README gallery image paths to match.

Release boundary

• This is a source and reviewed-evidence release. The live Railway store now
  serves exactly five reviewed, verifier-passed Tier.FINAL Insights (IDs 10,
  11, 13, 15, and 16), all produced at gpt-5.6-sol; the four Luna Insights
  (IDs 3, 6, 7, and 8) were retracted to draft on 2026-07-17. Hosted app
  verification remains at v0.8.0 pending redeploy: the deployed Railway
  /health and Vercel frontend are not being described as v0.9.0. The
  reported remaining account balance is planning context, not release
  evidence; the configured spend guard remains authoritative.