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-10-13-grok-build-invalid-policy-now-has-distinct-startup-errors-skipped-entries-and-retained-rules

Invalid policy now has distinct startup errors, skipped entries and retained rules. Some invalid policy now stops startup; other invalid entries are skipped while valid entries remain. The requirements-file startup refusal is documented by 1.0.50, absent from the inspected 1.0.46 guide, with its exact implementation debut unproven. Signed-file edits and parse failures have different consequences; the prior blanket fail-closed account was too broad.

Channel: tagged-release (1.0.50 and 1.0.52); preview-or-beta (disabled-hooks-file fix in enterprise/non-stable 1.0.53). Half: defect. Date: 2026-10-06..2026-10-12 (notes; requirements behavior documented by 1.0.50).

Operator consequence: Use stable 1.0.52 or the separately tested enterprise channel, run grok inspect and read skipped entries. Keep fail_closed=true for signed requirements. Exercise wrong types, malformed individual rules, unreadable files and environment-table errors independently; a typo does not have one universal policy result.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-grok-build-invalid-policy-now-has-distinct-startup-errors-skipped-entries-and-retained-rules

Profile citations

  • grok-build / claim / invalid-policy-distinct-outcomes

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact