CONTRACT

- No clear contract violation found against the quoted ADR-014 or ADR-015 binding prose. ADR-026’s potentially tense point is op-log ownership, but it explicitly separates substrate-owned posture-neutral interchange format from ADR-015’s operator-blind Hypercore-compatible/profiled implementation surface. That reading is supported by ADR-014’s statement that the substrate owns “op-log segment format” as a load-bearing format/interface spec and ADR-015’s operator-blind contents being deployment-specific.

CORRECTNESS

- “**ADR-019 EnvelopeSpec ABC … the substrate-side floor-enforcement contract … that the operator-blind sync layer composes above the op-log format.**”  
  This appears directionally inconsistent with later ADR-026 text: “**per-segment AEAD + key non-custody + a small positive cleartext allowlist instantiates the ADR-019 EnvelopeSpec contract**” and “**the capability verifier … encrypted blind-sync server … compose with that envelope (they wrap, schedule, encrypt, or transport its segments)**.” If EnvelopeSpec is the AEAD/envelope contract applied to segments, the blind sync layer seems to compose the op-log payload/segments into or under that envelope, not “above the op-log format.” This is wording-level architecture confusion, not an ADR-014/015 contract breach.

- “**The concrete op-log interchange-format spec, the thin Sync ABC, the conformance suite, and the reference-implementation shape are all deferred…**” versus “**This ADR names current-best-fit references non-bindingly only: Automerge 3 … Yjs … and Hypercore … for the format/op-log axis…**”  
  Not a contradiction by itself, but ADR-026 sometimes speaks as if the envelope already has specific fields: “**segment framing, actor id + monotonic counter, causal/version metadata, content-addressed identity, a model tag, a reserved snapshot-segment type, a forward-compat ‘preserve unknown fields’ rule**.” If the concrete spec is deferred, these should be framed as proposed/minimum candidate fields, not settled contents of the substrate-owned contract.

STYLE

- “**irreversible-if-skipped**” is awkward and overstated. Prefer “hard to retrofit” unless there is a specific irreversible failure mode.

- “**informed/blind multi-vendor research spike across the reused corvidAI roster**” is dense. It may be clearer as “multi-agent research spike using the corvidAI roster.”

- “**The spike was unanimous**” reads too absolute unless every cited dispatch explicitly converged. “The spike converged” is safer.

- “**soft reservation … subject only to normal RFC numbering mechanics, not doubt about whether RFC-003 is the intended home**” is wordy. It can be shortened without losing meaning.
