This is a code-and-tests change: a single id issuer (`freshEvidenceIds`) whose `taken` set is re-read per call and now includes the split record's own id, plus a new `duplicateIdErrors` check wired into the prospective-ledger validation before anything is written. Both effects tighten rather than loosen the §3.15 checks (fail-closed CI, no ambiguous/dangling ids) — a collision now fails the run instead of reaching the ledger. AGENTS.md is untouched; the only doc change appends a dated entry to docs/DECISIONS.md describing the defect (#353's duplicate AMZ-E110), the fix, and the manual renumbering, stamped with the founder's in-session direction, which the constitution explicitly permits as operating record. No citations, DOIs, or URLs are added under content/, so no fabrication surface; the verification section confirms none were found. Test fixtures use obviously synthetic ids and dates (GEO-E9xx, 2099-01-01) inside test files, not published content, so they are not fabricated provenance. Nothing here publishes an unratified draft as ratified or touches confidence material.

The change strengthens rather than weakens fail-closed validity: `freshEvidenceIds` tracks issued IDs and dynamically includes IDs already taken, while the prospective-ledger check now catches duplicate source, evidence, and claim IDs, including provisional records. The added tests cover repeated issuance, a three-way directional split, duplicate detection, and correct exclusion of rejected/provisional evidence from admitted counts. The decision-log entry records the stated founder supervision with a date and channel, and the change does not edit AGENTS.md or introduce citations, confidential material, or assessment provenance claims.

The change is a pure tooling and domain test fix addressing ID collisions during record splitting in the verification pipeline. It implements `freshEvidenceIds` and a pre-write duplicate ID check across prospective ledgers, directly supporting the schema uniqueness and integrity guarantees required by §8 and §3.15. No content files or citations are added or fabricated, and AGENTS.md is untouched.

The diff fixes a real pipeline bug: split-part evidence could reuse the part’s own id because the issuer did not count that id or ids already handed out. freshEvidenceIds closes that hole; duplicateIdErrors fails the prospective ledger before write, which tightens rather than weakens §3.15/§8 uniqueness. Tests cover the issuer, a three-way split, and the duplicate check. DECISIONS.md only logs the fix under founder direction; AGENTS.md is untouched; no citations or content records are fabricated. The view.test adjustment (tombstones out, provisional counted apart) matches §4 provisional-no-weight and does not reclassify checks.

This is a defensive pipeline fix: it repairs an id-collision bug (AMZ-E110 written twice on sitting #353) by giving each record's reading a single fresh-id issuer that counts the record's own id, and it adds a prospective duplicate-id check to verify — which strengthens, not weakens, the §3.15 checks. The AGENTS.md file is untouched, so §3.15's constitution rule is not implicated; no citations or locators are added (verification confirms none), so §3.7–§3.8 are not engaged. The hand-renumbering of the sitting's second record to AMZ-E112 is described as done on #353 (a separate change), and the DECISIONS.md entry is an append-only history record with date, channel, and supervision stamp, consistent with §3.14. The in-code comment citing '§8, no ambiguous ids' is a loose paraphrase of 'No dangling IDs' but is a style note, not an epistemic violation. No omitted files hide anything material, and no fabricated records or provenance stamps are visible in the diff.