Files
rUv 3daca8f628 docs(adr): ADR-322D — accept the cross-repo anchor record (was stale PROPOSED-EXTENSION) (#3127)
While researching a cross-ecosystem architecture question, found that
witness-receipt-contract.md §9 and the ruflo-anchor-record-v1 schema
both still say "PROPOSED-EXTENSION... nothing above is decided" —
but the two consumers that placeholder was gating (ruvnet/rvm#35,
ruvnet/autogenous#10) already merged real implementations against
exactly this shape:

- ruvnet/rvm#37 (merged): verify and anchor ruflo ADR-322C receipts
  into the witness chain
- ruvnet/autogenous#13 (merged): export promotion evidence in the
  ruflo ADR-322C receipt shape
- ruvnet/ruflo#3066, the PIR tracking issue that scoped this work,
  is itself closed with a status comment confirming the schema
  (PR #3067) is canonical on main and both conformance audits cleared

No schema or behavior change — this is a documentation-accuracy fix.
ADR-322D formally promotes the record from PROPOSED-EXTENSION to
Accepted to match what's already shipped and consumed, and explicitly
scopes it against a different, still-unwired "RVM" relationship
(LatentMesh's own aspiration to have RVF/RVM gate its candidate
cognition) so the two aren't conflated in future reads.


Claude-Session: https://claude.ai/code/session_01G3Fkc9qcZ2AkwGPce83yTa
2026-10-22 13:11:47 -04:00
..