This is a pipeline plumbing change: the YAML writers now pass `aliasDuplicateObjects: false` at document construction, and `replaceRecord`/`setField` re-serialize records that aliased an anchor the rewrite removes. AGENTS.md is untouched; only docs/DECISIONS.md gains an append-only dated entry stamped 'Supervised-by: founder (direction in session, 2026-09-20)', which §3.15 expressly permits for founder directions recorded in the decisions log. No content/ files change and the verification tool found no citation identifiers, so no fabrication or provenance-label question arises. The safety check is preserved rather than loosened: both writers still parse the edited text and compare it to the expected record list, throwing if it differs — the alias expansion widens what bytes may move but keeps the semantic-equality proof, so this is not check-weakening under §3.15. Tests are added covering append, in-place replacement, and field rewrite on an anchored file, satisfying §8/§10 for the highest-risk behavior. The only residual risk is byte-level churn in neighbouring records during a rewrite, which the tests and equality check adequately bound.

The change strengthens ledger integrity by preventing new YAML aliases and safely expanding dependent aliases when an anchored record is rewritten. The existing semantic equality checks remain fail-closed, and tests cover appending, record replacement, and field replacement without changing the parsed meaning of unaffected records. The decision entry records the implementation rationale and stamps the stated founder supervision with date and channel, with no visible contradiction or improper edit to AGENTS.md. No citations, confidential material, assessments, or ratification records are added or misrepresented.

This PR updates pipeline YAML writing utilities to disable YAML object aliasing (`aliasDuplicateObjects: false`) and expands dangling aliases when records are replaced or edited in-place. No changes are made to AGENTS.md, no content records or citations are added or fabricated, and strict serialization checks remain intact to ensure byte and semantic integrity across edits. The accompanying decision entry in docs/DECISIONS.md is properly recorded pursuant to §3.15.

The diff is pipeline/infrastructure only: ledger writers pass aliasDuplicateObjects: false, and replaceRecord/setField expand transitive aliases when an in-place rewrite would drop an anchor, with the existing parse-equality guard still requiring the file to mean the same. Tests cover append, replace, and setField on anchored input. docs/DECISIONS.md gains a dated founder-supervised note; AGENTS.md is untouched; no content/ citations, assessments, or confidence material are added. Nothing weakens §3.15 checks or misstamps provenance.

This is a pipeline code fix, not a content or assessment change: it disables YAML anchor/alias emission in the ledger writers and makes in-place rewrites re-serialize records that would otherwise be left with dangling aliases. It does not touch AGENTS.md (the appended DECISIONS.md entry is the decisions log, the legitimate home for such records, stamped with date and channel per §3.15), adds no citations or content claims, and carries no run records. Critically, it does not weaken any §3.15 check — the writer's parse-equality check is explicitly retained and the tests assert the file 'still says the same', so no validation is dodged or loosened. The provenance claim 'Supervised-by: founder (direction in session, 2026-09-20)' in DECISIONS.md is unverifiable from the packet, but it is stamped exactly as the constitution requires for recorded founder directions and matches the established pattern of adjacent entries; absent positive evidence of fabrication I cannot treat it as a violation. The diff is complete, tests cover the three write paths, and the change is the smallest coherent fix for a real failure (a promotion refused because anchored records could not be rewritten), so it complies.