# 490d C334 — Shem two-year source dependency and scope audit

24 September2026. Step1 of10 in the C334–C343 authorization.

**The sources give the two choices a shared Shem-ambiguity origin, but the reviewed passages do not prescribe their particular C319 pairing.** This is a narrower result than saying the choices are unrelated.

File_18 §1.5 and File_02 §6 distinguish three operations: the local Noah/Shem binding ambiguity, ordinary coherent regular Gear transport, and propagation of the same ambiguity through the cumulative lifespan chain. File_00 §§3.5–3.6.1 additionally requires opposite Normal-to-Ideal BC directions for Noah and Shem. A common “two years” label does not erase those distinctions.

| Source dependency | Positive instruction | What it does not establish in this audit |
|---|---|---|
| File_02 §6.2 and §6.4; File_18 §1.5 | Local regular ambiguity; chain-wide cumulative propagation from the same ambiguity | A rule selecting only ON-Shem i+2 while holding the OFF-Flood member |
| File_18 §3.1.4; File_11 §1.1 | An admitted three-Gear Flood register; Gear steps of two | A binding to this cumulative member or to a 529 target |
| File_00 §§3.5–3.6.1 | Valid father/son states with opposite BC shift directions | One uniform +2 state operation across figures and coordinate conventions |
| File_09 seven-year anatomy and cumulative/regular guard | 2+3+2 is a declared margin anatomy; substitution needs a declared dependency | Permission to identify every equal two-year displacement |

The exact pending claim is `a=b` in C319: S=p−460+a and R=f−460+b, with a,b∈{0,2}, while q and n remain held. The source passages establish shared origin and permitted state families, but no reviewed instruction binds precisely those endpoint choices and held quantities. C332's death partition continues to select b=2 without selecting a.

Ten targeted passage ranges in File_00, File_02, File_09, File_11 and File_18 are frozen with exact line locators and text in DATA.json. A literal search index for 529,1058,8993 and i+2 is also retained. It is a locator aid, not a proof of repository-wide absence. No historical report series was re-read wholesale. Source statements allowing broader pre-Flood Gear applications do not expand the user's Noah/Shem/Flood-only scope.

The useful next move is to resolve the coordinate semantics: does equal displayed +2 mean the same underlying motion, and which companion endpoints would move under a whole source operation?

## Verification and limits

14 main checks and 19 frozen-input/predecessor authentication checks passed. A second main replay produced byte-identical DATA/RESULTS. These checks and the source interpretation were performed by the root agent; no new independent-agent review is claimed. All frozen originals and standing controls remain unchanged. Verification counts are not independent-witness counts.

Bounded textual dependency audit only. Neither absence across all archives nor a prohibition of the source constructions is asserted. No numerical selector or new endpoint is adopted.

Mirror/529 focus: K=529, E=25/23, P=70/69. Global paired Mirror January AD1; local junction January AD2; no civil year zero. Regular Gears are Noah/Shem/Flood only. SP minus-one person companions remain local to SP Noah/Shem; Flood close is a separate boundary. No upstream/cumulative Gear, new endpoint or phase, fitted anchor, global axis, primer reopening, canonical or graph edit. Capture now; canonize later. Source identity, context, modal binding, generated coordinates and phase ancestry stay distinct.

## Decision after this result

**C335, proposed and unexecuted:** Translate C319 a and b into their source-coordinate directions and endpoint footprints. Check the admitted configurations and inherited phases without extending the annual or Gear domain.

C334 locates a real shared origin but not the exact coupling. A sign-and-scope audit can show whether the displayed +2 values even represent the same source operation.