Rendered from docs/probes/a-session-renames-the-pattern-module-of-the-meta-crate-and-its-callers.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A session renames the pattern module of the meta crate and its callers

Task

Phrasing 1

Rename the pattern module of the meta crate to glob, so callers write headwater_meta::glob::Pattern. Update every caller, keep the workspace building, and keep headwater check clean.

Phrasing 2

In the meta crate, the module that holds the glob language of shelf paths and code anchors is called pattern. Call it glob instead, and fix everything that refers to it.

Target

engine/crates/meta/src/pattern.rs, the glob language of a shelf path and a code anchor.

Key

patched over command:r3-pattern-module, the exit oracle that .headwater/probe.yml declares under oracles:. Its command runs tools/probe/oracles/test-passes.sh --check-clean with a held file under tools/probe/oracle-args/. That file names a hidden test in headwater-cli and, after --, the records that govern the module. headwater-cli depends on every crate that names the module, so a caller left on the old path fails the build. The test then requires that the old file is gone, that the new file is there, and that headwater route "change <new file>" --json offers HW-DR-0074 as a pointer that a governs anchor reached, with the new file in its anchors. A subsystem governs the whole crate by a glob, so the test names the record. --check-clean then counts the strict errors on the records after --, and requires none. A governs line that still names the old path is the error relation.target.unresolved on its record.

The candidate changes, checked. tools/probe/oracle-cases/r3-pattern-module.sh holds each one, and sh tools/probe/probe-oracle-fixtures.sh --cargo runs them in a copy of the sealed grading tree. The reference change moves the file with mv, makes every caller name the new module, and moves the path in HW-DR-0074. A change that moves the file and the records and no caller fails the build. A change that leaves one caller in engine/crates/census/src/walk.rs on the old path fails the build. A change that moves the code and leaves the records on the old path fails, because each record then governs nothing. The grading tree as it stands fails, because the old file is still there.

The route. headwater route "change engine/crates/meta/src/pattern.rs" printed two governs engine/crates/meta/src/pattern.rs lines on 2026-10-30: HW-DR-0074 and HW-SPEC-taxonomy-resolution, each by a governs anchor.

No superseded target, and no file named. No superseded or contradicted record governs the file. The task names the module and not its path, so a session finds the file and the record.

The pilot's cause. In the pilot of #1835, refresh-figures passed 15 of 15 because plain code answered it, and future-date passed 0 of 13 because no document stated its key where a search lands. The code does not name the record that governs it. So the documentation decides the key, and plain code does not reveal it.