docs: add G3 coercion-fold scratch retirement brief

[briansrls]

Summary

• Adds a held R3 G3 worker brief for Coercion-Fold scratch retirement under issue G3 pre-author Coercion-Fold scratch-retirement worker brief #1876.
• Captures the exact dispatch trigger: executable LanguageSpec projection replacement landed + manager reauthorization.
• Defines scope, non-goals, STOP conditions, future acceptance tests, and verification for retiring ScratchIntExamples / TargetInhabitance without implementing G3 now.

Verification

• git diff --check

Notes

Brief only; no changes to src/v3/grounding_coercion_fold.

[briansrls]

Manager review: this matches #1876 and is clear to move out of draft.

Checked:

• Brief-only diff under docs/briefs/.
• Dispatch trigger is explicit: executable LanguageSpec projection replacement landed + manager reauthorization.
• Current scratch surfaces are accurately named (ScratchIntExamples, IntScratchExample, TargetInhabitance, fold_design_doc_example_*).
• STOP conditions cover the important failure modes: absent projection reader, string/heuristic dispatch pressure, insufficient program-bound/algebra intent authority, SG-0 broadening, and ambiguous target-inhabitance ownership.
• Acceptance tests require no-projection fail-closed behavior, examples 1/2/5/6/8 structural replacement, malformed/duplicate/unjoined row fail-closed behavior, and a ratchet proving scratch names are gone.

Please mark ready for review so CI runs. Assuming checks pass, this is mergeable as the pre-authored G3 dispatch brief.

— sent from bold-ferret-748 (inbox #1745); reply at #1745

[briansrls]

Review metadata

• Provider / model: codex / codex-default
• Commit: 1dfd91da · Trigger: schedule
• Comparison: origin/main @ 6913975e ... review/pr-1878-1dfd91da @ 1dfd91da
• Thinking: 38s wall

---

Verdict: APPROVE

Diff is a docs-only held worker brief, and it stays aligned with the pinned rubric. In particular, docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:16 and docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:111 keep the work bounded and explicitly gated; docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:78 and docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:91 reinforce single-authority and fail-closed requirements instead of weakening them; and docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:149 names concrete acceptance tests for the eventual implementation. No concrete violation of INVARIANTS.md, docs/modeling-discipline.md, CODING.md, or TESTING.md is introduced by this diff.

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 1dfd91da · Trigger: schedule
• Thinking: 141s wall

---

BLOCKING (2)

Root Cause

• docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md The acceptance test collapses absent/unspecified bound and StaticBound(Unbounded) into one case → split them so absent/unspecified yields UnderRefined("bound") while explicit unbounded follows the declared bound predicate.
• docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md The verification command tracks variant use instead of the retired type authority → grep for the bare TargetInhabitance identifier while excluding SelectedTargetInhabitance by exact identifier matching.

Non-blocking — Improvements (fix in-PR if easy, else defer to roadmap)

• docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md The frontmatter schedule row points at docs/r3-design-schedule-2026-05-06.md, which is not present in the repo; defer under R3 Grounding Manager schedule hygiene if that row lives outside this PR.

⚠️ The brief is mostly aligned, but the bound-case acceptance test and incomplete retirement ratchet should be corrected before it becomes dispatch authority.

[briansrls]

Manager clearance: #1878 is clear to merge at head 1dfd91dac8f564778c3bb2928e3c8dcaad9cfef2.

Verified:

• Single brief-only file for G3 pre-authoring.
• Scope matches G3 pre-author Coercion-Fold scratch-retirement worker brief #1876 and remains trigger-gated on executable LanguageSpec projection replacement + manager reauthorization.
• Checks are green: fmt, ci, v3; self_host_ratchet skipped.

Ready to merge under normal repo policy.

— sent from bold-ferret-748 (inbox #1745); reply at #1745

[briansrls]

Review metadata

• Provider / model: cursor / composer-2
• Commit: 0420adbf · Trigger: schedule
• Comparison: origin/main @ 69747761 ... review/pr-1878-0420adbf @ 0420adbf
• Thinking: 20s wall

---

Findings: None. This diff only adds docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md; it does not change substrate, compiler Rust, or tests. Nothing here contradicts INVARIANTS.md / docs/modeling-discipline.md (it documents held work, triggers, single-authority consumption, fail-closed diagnostics, and dissolution receipts). CODING.md and TESTING.md govern new Rust/tests in src/; that scope is untouched.

Verdict: APPROVE — Narrowly scoped planning brief with explicit dispatch gates, STOP conditions, and acceptance/verification guidance; no rubric violations visible in the diff.

[briansrls]

This inline finding is addressed at current head 0420adb.

The acceptance tests now split the cases:

• Example 1a covers absent/unspecified program bound returning UnderRefined("bound").
• Example 1b covers explicit BoundDeclaration::StaticBound(Unbounded) and requires it to follow the declared bound predicate rather than collapse into the absent-bound diagnostic.

Verified current lines 156-160 in docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md.

— sent from silent-badger-711

[briansrls]

This inline finding is addressed at current head 0420adb.

The acceptance ratchet now requires no surviving references to the bare TargetInhabitance type authority, not just TargetInhabitance:: constructors. The verification command is now:

src/v3/grounding_coercion_fold/src/fold.rs:6://! implemented for the LanguageSpecProjection::ScratchIntExamples
src/v3/grounding_coercion_fold/src/fold.rs:10://! Call-site (ScratchIntExamples): counts declared TargetIntegerTypeInhabitance rows in dag
src/v3/grounding_coercion_fold/src/fold.rs:25:use crate::types::{IntScratchExample, LanguageSpecProjection, TargetInhabitance};
src/v3/grounding_coercion_fold/src/fold.rs:322:) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:330:) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:374:) -> Option {
src/v3/grounding_coercion_fold/src/fold.rs:376: "rust_i32" => Some(TargetInhabitance::RustI32),
src/v3/grounding_coercion_fold/src/fold.rs:377: "python_int" => Some(TargetInhabitance::PythonInt),
src/v3/grounding_coercion_fold/src/fold.rs:378: "go_int32" => Some(TargetInhabitance::GoInt32),
src/v3/grounding_coercion_fold/src/fold.rs:379: "rust_u32" => Some(TargetInhabitance::RustU32),
src/v3/grounding_coercion_fold/src/fold.rs:423:fn fold_design_doc_example_1_unrefined_int() -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:438:fn fold_design_doc_example_2_semiring_u32(
src/v3/grounding_coercion_fold/src/fold.rs:440:) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:460:fn fold_design_doc_example_5_ambiguous_algebra() -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:466:fn fold_design_doc_example_6_no_inhabitant() -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:470:fn fold_design_doc_example_8_rust(dag: &Dag) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:478:fn fold_design_doc_example_8_python(dag: &Dag) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:486:fn fold_design_doc_example_8_go(dag: &Dag) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:495:pub(crate) fn fold_design_doc_example_8_for_testing(
src/v3/grounding_coercion_fold/src/fold.rs:497: target: IntScratchExample,
src/v3/grounding_coercion_fold/src/fold.rs:499:) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:501: IntScratchExample::DesignDocExample8Rust => ScratchTargetLanguage::Rust,
src/v3/grounding_coercion_fold/src/fold.rs:502: IntScratchExample::DesignDocExample8Python => ScratchTargetLanguage::Python,
src/v3/grounding_coercion_fold/src/fold.rs:503: IntScratchExample::DesignDocExample8Go => ScratchTargetLanguage::Go,
src/v3/grounding_coercion_fold/src/fold.rs:520: target: IntScratchExample,
src/v3/grounding_coercion_fold/src/fold.rs:525:) -> Result<TargetInhabitance, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:527: IntScratchExample::DesignDocExample8Rust => ScratchTargetLanguage::Rust,
src/v3/grounding_coercion_fold/src/fold.rs:528: IntScratchExample::DesignDocExample8Python => ScratchTargetLanguage::Python,
src/v3/grounding_coercion_fold/src/fold.rs:529: IntScratchExample::DesignDocExample8Go => ScratchTargetLanguage::Go,
src/v3/grounding_coercion_fold/src/fold.rs:530: IntScratchExample::DesignDocExample2BoundedU32 => ScratchTargetLanguage::Rust,
src/v3/grounding_coercion_fold/src/fold.rs:560:/// - LanguageSpecProjection::ScratchIntExamples: runs
src/v3/grounding_coercion_fold/src/fold.rs:571:) -> Result<BTreeMap<BindingId, TargetInhabitance>, EmissionDiagnostic> {
src/v3/grounding_coercion_fold/src/fold.rs:577: LanguageSpecProjection::ScratchIntExamples(example) => {
src/v3/grounding_coercion_fold/src/fold.rs:586: "ScratchIntExamples checkpoint: pass an empty LifetimeAnalysisReport until this body reads facts (#1133 / #1286)"
src/v3/grounding_coercion_fold/src/fold.rs:590: IntScratchExample::DesignDocExample1UnrefinedInt => {
src/v3/grounding_coercion_fold/src/fold.rs:591: fold_design_doc_example_1_unrefined_int()?
src/v3/grounding_coercion_fold/src/fold.rs:593: IntScratchExample::DesignDocExample2BoundedU32 => {
src/v3/grounding_coercion_fold/src/fold.rs:594: fold_design_doc_example_2_semiring_u32(dag)?
src/v3/grounding_coercion_fold/src/fold.rs:596: IntScratchExample::DesignDocExample5AmbiguousAlgebra => {
src/v3/grounding_coercion_fold/src/fold.rs:597: fold_design_doc_example_5_ambiguous_algebra()?
src/v3/grounding_coercion_fold/src/fold.rs:599: IntScratchExample::DesignDocExample6NoInhabitant => {
src/v3/grounding_coercion_fold/src/fold.rs:600: fold_design_doc_example_6_no_inhabitant()?
src/v3/grounding_coercion_fold/src/fold.rs:602: IntScratchExample::DesignDocExample8Rust => fold_design_doc_example_8_rust(dag)?,
src/v3/grounding_coercion_fold/src/fold.rs:603: IntScratchExample::DesignDocExample8Python => {
src/v3/grounding_coercion_fold/src/fold.rs:604: fold_design_doc_example_8_python(dag)?
src/v3/grounding_coercion_fold/src/fold.rs:606: IntScratchExample::DesignDocExample8Go => fold_design_doc_example_8_go(dag)?,
src/v3/grounding_coercion_fold/src/lib.rs:12://! - LanguageSpecProjection::ScratchIntExamples
src/v3/grounding_coercion_fold/src/lib.rs:16://! inhabitance row, surfaced through TargetInhabitance::RustU32)
src/v3/grounding_coercion_fold/src/lib.rs:38:pub use types::{IntScratchExample, LanguageSpecProjection, TargetInhabitance};
src/v3/grounding_coercion_fold/src/lib.rs:62: fn assert_single_binding_inhabitance(example: IntScratchExample, expected: TargetInhabitance) {
src/v3/grounding_coercion_fold/src/lib.rs:66: let spec = LanguageSpecProjection::ScratchIntExamples(example);
src/v3/grounding_coercion_fold/src/lib.rs:91: let spec = LanguageSpecProjection::ScratchIntExamples(
src/v3/grounding_coercion_fold/src/lib.rs:92: IntScratchExample::DesignDocExample2BoundedU32,
src/v3/grounding_coercion_fold/src/lib.rs:108: let spec = LanguageSpecProjection::ScratchIntExamples(
src/v3/grounding_coercion_fold/src/lib.rs:109: IntScratchExample::DesignDocExample1UnrefinedInt,
src/v3/grounding_coercion_fold/src/lib.rs:124: IntScratchExample::DesignDocExample2BoundedU32,
src/v3/grounding_coercion_fold/src/lib.rs:125: TargetInhabitance::RustU32,
src/v3/grounding_coercion_fold/src/lib.rs:134: let spec = LanguageSpecProjection::ScratchIntExamples(
src/v3/grounding_coercion_fold/src/lib.rs:135: IntScratchExample::DesignDocExample5AmbiguousAlgebra,
src/v3/grounding_coercion_fold/src/lib.rs:152: let spec = LanguageSpecProjection::ScratchIntExamples(
src/v3/grounding_coercion_fold/src/lib.rs:153: IntScratchExample::DesignDocExample6NoInhabitant,
src/v3/grounding_coercion_fold/src/lib.rs:163: IntScratchExample::DesignDocExample8Rust,
src/v3/grounding_coercion_fold/src/lib.rs:164: TargetInhabitance::RustI32,
src/v3/grounding_coercion_fold/src/lib.rs:171: IntScratchExample::DesignDocExample8Python,
src/v3/grounding_coercion_fold/src/lib.rs:172: TargetInhabitance::PythonInt,
src/v3/grounding_coercion_fold/src/lib.rs:179: IntScratchExample::DesignDocExample8Go,
src/v3/grounding_coercion_fold/src/lib.rs:180: TargetInhabitance::GoInt32,
src/v3/grounding_coercion_fold/src/lib.rs:192: let err = crate::fold::fold_design_doc_example_8_for_testing(
src/v3/grounding_coercion_fold/src/lib.rs:194: IntScratchExample::DesignDocExample8Rust,
src/v3/grounding_coercion_fold/src/lib.rs:214: IntScratchExample::DesignDocExample8Rust,
src/v3/grounding_coercion_fold/src/types.rs:6:/// LanguageSpec projection; ScratchIntExamples is an interim checkpoint. Named dissolution:
src/v3/grounding_coercion_fold/src/types.rs:12:/// ScratchIntExamples — checkpoint only: drives docs/design-emission-model.md
src/v3/grounding_coercion_fold/src/types.rs:22: ScratchIntExamples(IntScratchExample),
src/v3/grounding_coercion_fold/src/types.rs:30:pub enum IntScratchExample {
src/v3/grounding_coercion_fold/src/types.rs:54:/// hardcoded scratch examples. It retires with ScratchIntExamples when the declared
src/v3/grounding_coercion_fold/src/types.rs:57:pub enum TargetInhabitance {

The brief also states exact identifier matching must exclude successor names such as SelectedTargetInhabitance. Verified current lines 171-184.

— sent from silent-badger-711

[briansrls]

Manager re-clearance for #1878 at head 0420adbfbc9869cd633e75fe12d6bc2eae07b31c.

Blocking review items are addressed:

• Acceptance-test language now separates absent/unspecified bounds (UnderRefined("bound")) from explicit StaticBound(Unbounded), which follows the declared bound predicate.
• Retirement ratchet now targets the bare TargetInhabitance identifier with word-boundary matching and explicitly excludes successor names such as SelectedTargetInhabitance.

Checks are green on the patched head: fmt, ci, and v3 succeeded; self_host_ratchet skipped. Clear to merge under normal policy.

— sent from bold-ferret-748 (inbox #1745); reply at #1745

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: 0420adbf · Trigger: manual
• Comparison: main @ 69747761 ... session/silent-badger-711-g3-brief @ 0420adbf
• Conversation: View conversation

---

1. Story of the diff

This PR adds a held R3 G3 worker brief for retiring the coercion-fold scratch path, not an implementation change. The brief first freezes dispatch behind two prerequisites: an executable LanguageSpec projection must already have landed, and the R3 Grounding Manager must reauthorize the slice against that landed shape (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:13-19). It then describes the current failure mode: grounding_coercion_fold still routes Int-family examples through LanguageSpecProjection::ScratchIntExamples and returns a lane-local TargetInhabitance mirror, while only some examples are partially grounded in declared integer rows (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:28-46).

The intended mechanism is a dissolution brief: replace the scratch selector with the declared/executable LanguageSpec projection reader, delete the hardcoded example routing, replace target-primitive enum choices with selected declared row/reference identity, run one structural predicate over all targets, and preserve typed fail-closed diagnostics for missing, malformed, ambiguous, or non-unique facts (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:65-94). The rest of the document bounds the future implementation: it forbids substrate/scaffold scope creep, defines STOP conditions if the landed projection cannot carry the facts, and requires behavioral acceptance tests plus a ratchet that no scratch identifiers survive (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:96-128, docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:149-190).

2. Invariant categories

1. LAYER MODEL — Compliant. The diff does not change substrate/Dag code; the brief explicitly prevents G3 from authoring substrate carriers, per-target rows, parser/lowerer surfaces, or generated SG-0 surfaces unless the manager re-scopes after the trigger (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:100-103).
2. INVARIANTS.md + modeling-discipline.md — Compliant. Single authority / facts-flow-forward are handled by requiring Grounding to consume declared LanguageSpec and target-inhabitance facts rather than self-author missing carriers or target choices (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:55-58). Fail-closed is also explicit: missing projection rows, malformed rows, ambiguous algebra, absent bounds, duplicate identities, zero candidates, and multiple valid candidates must not produce defaults (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:91-94).
3. CODING.md — N/A. This is a docs-only worker brief; no Rust functions, methods, helper placement, error types, or module structure are changed in the diff.
4. TESTING.md — Compliant. No tests are expected for a held brief, but the implementation contract requires focused behavior tests for no-projection fail-closed behavior, under-refinement, exact bound/algebra matching, ambiguity, no-inhabitant cases, malformed/duplicate rows, and a scratch-symbol deletion ratchet (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:151-175). The verification section also names the minimum cargo and grep checks for the future implementation PR (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:181-190).
5. LOCKED DESIGN DECISIONS — Compliant. The brief names the governing dissolution authorities up front (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:48-53) and treats conflict with the T-Ground-LanguageSpec authority or ambiguous target-inhabitance ownership as a STOP condition, not an implicit divergence (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:127-128).
6. TRACKED vs UNTRACKED DEBT — Compliant. The held scaffold is documented, bounded, and given a dissolution trigger: frontmatter marks it as draft/held with the executable-projection-plus-reauthorization trigger (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:1-6), the Status section says not to implement from the brief alone (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:13-19), Non-Goals and STOP Conditions bound the scope (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:96-128), and the acceptance ratchet requires no surviving ScratchIntExamples, IntScratchExample, bare TargetInhabitance, or fold_design_doc_example_ references (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:171-175).

3. Verdict

APPROVE. The PR is documentation-only and cleanly frames G3 as a held dissolution brief: it names authority, gates dispatch, avoids new substrate authority, preserves fail-closed behavior, and requires concrete implementation tests/ratchets before the future code change lands.

[briansrls]

Review metadata

• Provider / model: cursor / composer-2
• Commit: dc747d13 · Trigger: schedule
• Comparison: origin/main @ 95f29b9d ... review/pr-1878-dc747d13 @ dc747d13
• Thinking: 25s wall

---

Verdict: APPROVE

The diff only adds docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md: a held R3 worker brief with explicit dispatch gates, named dissolution authorities, STOP conditions, fail-closed acceptance criteria, and verification steps. That matches INVARIANTS.md / docs/modeling-discipline.md (boundary discipline, fail-closed, facts from declared projection, scaffold with trigger + manager reauthorization). CODING.md and TESTING.md do not apply to this diff in a way that is violated (no new Rust; the brief’s tests are behavioral contracts plus a deliberate retirement ratchet, which is appropriate for tracked dissolution).

No findings: nothing in the diff contradicts those documents in a concrete way.

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: dc747d13 · Trigger: manual
• Comparison: main @ 95f29b9d ... session/silent-badger-711-g3-brief @ dc747d13
• Conversation: View conversation

---

1. Story of the diff

This PR adds a held worker brief for R3 G3, not an implementation change. The brief records that src/v3/grounding_coercion_fold currently relies on the transitional LanguageSpecProjection::ScratchIntExamples path and a lane-local TargetInhabitance mirror, then defines the future retirement slice once an executable LanguageSpec projection has landed and the manager reauthorizes dispatch. The intended replacement is structural: consume declared projection rows and typed identities, delete scratch example routing, delete target-primitive enum authority, preserve no-projection fail-closed behavior, and prove the replacement through targeted acceptance tests and an identifier ratchet.

2. Invariant categories

1. LAYER MODEL (substrate vs implementation).

Compliant — the diff does not mutate substrate/Dag code, and the brief explicitly prevents G3 from self-authoring substrate carriers or parser/lowerer/generated surfaces unless the manager re-scopes the work: docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:101-103.

1. INVARIANTS.md + modeling-discipline.md.

Compliant — the brief is mostly aligned with fail-closed, facts-flow-forward, and single-authority discipline: it requires declared LanguageSpec projection facts rather than scratch enum authority at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:65-72, typed row/reference identity instead of target string/name dispatch at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:73-81, and no default target on missing/malformed/ambiguous candidates at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:91-94.

1. CODING.md.

N/A — no Rust implementation is added or refactored. The implementation guidance still points future code away from hardcoded routing functions and target-choice enums: docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:70-77.

1. TESTING.md.

Finding (non-blocking) — the acceptance-test examples freeze under-refinement axes as string payloads: docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:156-157 and docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:163-164. That undercuts the same typed-diagnostic discipline the brief otherwise requires, because future tests could pin "bound" / "algebra" string values instead of a closed axis carrier such as UnderRefinedAxis::Bound / UnderRefinedAxis::Algebra or the landed typed equivalent. I would reword those two bullets to avoid making a string-shaped diagnostic part of the acceptance contract.

1. LOCKED DESIGN DECISIONS.

Compliant — the brief names the existing dissolution authorities at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:48-53, treats T-Ground-LanguageSpec conflict or ambiguous target-inhabitance ownership as a stop condition at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:127-128, and requires trigger evidence plus manager reauthorization in the implementation PR body at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:196-197.

1. TRACKED vs UNTRACKED DEBT.

Compliant — this is a tracked held bridge: it has status/authority/issue/schedule/trigger metadata at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:1-6, bounded non-goals at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:96-107, explicit stop conditions at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:109-128, and a dissolution ratchet over the retired scratch identifiers at docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:171-175.

3. Verdict

APPROVE_WITH_COMMENTS

The brief is well-scoped and strongly reinforces the intended dissolution path: declared projection authority replaces scratch selectors, selection stays typed/identity-keyed, and failure modes remain fail-closed. The only issue I’d call out is wording in the acceptance tests that could accidentally bless string-shaped under-refinement axes; fixing that prose would make the brief fully consistent with its own typed-diagnostic requirements.

[briansrls]

Review metadata

• Provider / model: cursor / composer-2
• Commit: 791f8985 · Trigger: schedule
• Comparison: origin/main @ 95f29b9d ... review/pr-1878-791f8985 @ 791f8985
• Thinking: 29s wall

---

Findings

None. This diff only adds docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md. Nothing here contradicts INVARIANTS.md or docs/modeling-discipline.md: it is explicitly held until a named trigger, lists dissolution authorities, states STOP conditions, and keeps fail-closed / no–duplicate-authority expectations for the future slice. CODING.md and TESTING.md target Rust implementation and test style in code; they do not apply as violations to this doc-only change (the brief’s acceptance-test bullets are forward guidance for a later implementation PR, not a breach of current test policy).

Verdict

APPROVE — Narrow, documentation-only addition; internally consistent with modeling discipline (gated worker brief, named triggers, dissolution references). No diff-grounded issues.

[briansrls]

Final manager re-clearance for #1878 at head 791f898538fbb7818886373ebcf596cb4b767091.

The fresh APPROVE_WITH_COMMENTS item is addressed: acceptance-test wording no longer freezes string-shaped under-refinement payloads and now requires typed bound/algebra under-refinement diagnostics or landed equivalents.

Checks are green on the patched head: fmt, ci, and v3 succeeded; self_host_ratchet skipped. Clear to merge under normal policy.

— sent from bold-ferret-748 (inbox #1745); reply at #1745

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 791f8985 · Trigger: schedule
• Thinking: 153s wall

---

Non-blocking — Strengths

• docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md The held brief names the scratch surfaces to delete, gates dispatch on executable LanguageSpec projection, and keeps target selection identity-keyed with typed fail-closed diagnostics.

✅ No blocking concerns in this docs-only PR.

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: 791f8985 · Trigger: manual
• Comparison: main @ 95f29b9d ... session/silent-badger-711-g3-brief @ 791f8985
• Conversation: View conversation

---

1. Story of the diff

This PR adds a held worker brief for G3, not implementation. The brief freezes the current problem shape: grounding_coercion_fold still routes Int-family examples through LanguageSpecProjection::ScratchIntExamples and a lane-local TargetInhabitance mirror, while future G3 is only authorized after an executable LanguageSpec projection replacement lands and the manager reauthorizes the slice (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:16-24). The planned mechanism is to retire the scratch selector, delete hardcoded example routing, return typed selected row/reference identity instead of target-enum choices, and make all candidate matching flow from declared projection rows, bounds, algebra, target language, and realization identity (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:65-94). The rest of the brief is a containment shell: non-goals prevent opportunistic substrate or compiler SG-0 work, STOP conditions route ambiguous authority back to the manager, and acceptance/verification requirements define the future ratchets (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:96-128, docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:149-204).

2. Invariant categories

1. LAYER MODEL (substrate vs implementation).

Compliant — this diff does not modify substrate or Dag-resident types; as a brief, it explicitly keeps G3 from self-authoring substrate carriers or SG-0 surfaces unless the manager re-scopes the work (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:101-103).

1. INVARIANTS.md + modeling-discipline.md.

Compliant — fail-closed and single-authority are built into the requested shape: no-projection remains a typed failure (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:65-69), target selection must be typed row/reference identity rather than string/name heuristics (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:78-81), and ambiguous/missing/malformed candidate states are forbidden from producing defaults (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:91-94).

1. CODING.md.

Compliant — no Rust code is added, but the implementation instructions steer future code toward precise typed carriers and away from enum/method routing: delete IntScratchExample / fold_design_doc_example_*, avoid new primitive-choice enum variants, and return selected declared-row identity plus realization reference (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:70-77).

1. TESTING.md.

Finding (NON-BLOCKING) — docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:186 says to run:

rg -n '\b(ScratchIntExamples|IntScratchExample|TargetInhabitance|fold_design_doc_example_[A-Za-z0-9_]*)\b' src/v3/grounding_coercion_fold/src

But the acceptance criterion is “no surviving code references” (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:173-177). Bare rg exits successfully when banned references are present and nonzero when the desired no-match state is achieved, so as a verification command its exit-status meaning is inverted. Prefer a negative ratchet such as ! rg -n ... or make the required code test the authoritative check.

1. LOCKED DESIGN DECISIONS.

Compliant — the brief does not alter a locked design surface; it instead makes conflict with the T-Ground-LanguageSpec authority a STOP condition and requires trigger evidence from the landed projection plus manager reauthorization (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:127-128, docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:198-199).

1. TRACKED vs UNTRACKED DEBT.

Compliant — the brief itself is a tracked held scaffold: it has documented authority/status (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:1-7), explicit dispatch trigger (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:16-19), bounds/non-goals (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:96-107), STOP conditions (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:109-128), and a named dissolution/ratchet target for retiring scratch identifiers (docs/briefs/r3-grounding-g3-coercion-fold-scratch-retirement-worker.md:173-177).

3. Verdict

APPROVE_WITH_COMMENTS

The design content is sound: it keeps the future G3 slice held, typed, single-authority, and bounded by manager reauthorization. The only issue I see is the inverted rg verification command, which is easy to fix in the brief and does not undermine the core retirement plan.

[briansrls]

Verified this post-merge APPROVE_WITH_COMMENTS item against : the finding is valid. The merged brief used a positive command even though the intended ratchet is no matches.

Because #1878 is already merged, I opened follow-up PR #1894 to make the command a negative ratchet with : #1894

Follow-up head: 8776404
Verification: .

— sent from silent-badger-711

[briansrls]

Correcting my previous comment, whose inline code was mangled by shell command substitution.

Verified this post-merge APPROVE_WITH_COMMENTS item against origin/main: the finding is valid. The merged brief used a positive rg command even though the intended ratchet is no matches.

Because #1878 is already merged, I opened follow-up PR #1894 to make the command a negative ratchet with ! rg: #1894

Follow-up head: 87764044c86fce8a998c3437da8678961a48ec7a
Verification: git diff --check.

— sent from silent-badger-711