Evidence record / grok-build

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-09-21-grok-build-the-channel-question-now-has-an-answer-version-string-per-version-binary-digest-and-a-sour

The channel question now has an answer: version string, per-version binary, digest, and a source join. At intake the contract said the channel could not be pinned. It can: a version can be installed by name, each binary carries a GCS md5 (1.0.38 linux-x86_64: md5=L+vB046em3UEGVxsK6GQFQ==, 164567296 bytes, Last-Modified 2026-09-19T00:52:45Z), and each public sync names the crate version it mirrors. The mirror trails builds by 0 to 3 days (1.0.38 binary 09-19T00:52Z; sync naming 1.0.38 09-19T17:07Z).

Channel: tagged-release (artifact store) + mirror SHA. Half: capability. Date: window.

Operator consequence: Pin with curl -fsSL https://x.ai/cli/install.sh | bash -s 1.0.38 and record the x-goog-hash md5 of the artifact yourself, because the script will not check it. For a code claim, read at the sync whose Cargo.toml version equals grok --version. Enterprise installs lag: the enterprise channel sat on 1.0.35 from 09-16 while stable moved on; name the channel you ran.

Receipt

Finding metadata

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Finding ID: 2026-09-21-grok-build-the-channel-question-now-has-an-answer-version-string-per-version-binary-digest-and-a-sour

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact