# R1 reconciliation — Codex response, not a provider verdict

Claude R1 REVISE: D1 is addressed by an explicit same-master/writer/access correction restriction in the authoritative contract, lifecycle and question route, with refusal tests. Separate-actor correction is deferred, not misreported as tampering. D2 now isolates a valid quantity path versus valid conversion path and renames the previous native-path mutation. D3 validates nonblank string host master/writer and integer authority rank. D4 requires nonempty distinct current/previous IDs and refuses a directly visible two-cycle. D5 validates only bound host-object fields; actual installed fixtures include a Cyrillic host name and outer V3 validates the full object. D6 documents signed character limits. D7 makes shared anchor origin/unit and all-role equality explicit. D8 restricts preservation claims to accepted normalized decimal notation and keeps raw source externally. D9 corrects non-observation facet statuses. D10 improves unsupported-operation evidence and action wording; question routes remain bounded guidance, not an authority workflow.

New meaningful unit/native checks cover changed-writer refusal, malformed host context, native binding fields, true correction-path conflict, IDs/cycle, unadmitted target and right-hand unknown comparison. The full contract adds a rejection handling table and subject/purpose evidence duties. The 201-case Decimal oracle remains a separately calculated finite-precision comparison, not exact physical or domain proof. No unchanged R1 file is falsely claimed to be the final reviewed candidate; a new full freeze is required.

Grok R1 ACCEPT WITH LIMITS independently found the missing current/standalone fact ID guard and native quantity.value coverage gap. Both are now addressed: standalone IDs are nonempty strings, both native paths are exercised, and explicit unknown magnitude is stored and read back. Grok's numerical-cap note is a documented fail-closed boundary, not a reachable wrong-value defect for admitted inputs. R1 provider disagreement is preserved: Claude REVISE versus Grok ACCEPT WITH LIMITS; neither is rewritten as approval of the changed files.


Claude R2 REVISE: D1 exposed a missing native slot qualification. The minimal bounded fix states one semantic quantity per existing host, one value and one conversion slot, with host-enforced inventory and no artificial host creation. Multi-field native binding is deferred explicitly. Pairwise correction now preserves input kind/dimension/anchor/role/context, and tests refuse an unrelated quantity even when each individual envelope validates. Historical conversion staleness remains host work. This narrows the tested native binding while preserving the pure embedded value API.

D2 now captures the predecessor bytes before appending the correction and separately reports preservation after append, pair checking and tamper restoration. D3 demands explicit null unit/validTo keys. D4 disallows whitespace in revision tokens and updates the sibling schema pin. D5 explains unsupported-transform schema refusals separately from schema-pin corruption. D6 aligns helper facets, makes optional artifacts conditional, removes permission wording from the refusal, names canonical/digest helpers and clarifies synthetic publication declarations. D7 adds reverse point/difference, negative-offset and scalar-anchor checks. The unreachable 256-character output cap remains a fail-closed bound; no claim of boundary execution is added. R2's previous frozen bytes and raw verdict are preserved unchanged.

Grok R2 ACCEPT WITH LIMITS is preserved separately from Claude R2 REVISE. R3 also addresses Grok L1/L3/L4 by rejecting blank native IDs, returning a defensive correction copy and distinguishing malformed predecessor links from a direct cycle. R2 L5 and reverse-direction coverage were covered by the Claude remediation. Result-bound diagnostics and broader provider suggestions remain explicit bounded/deferred scope. For R2, Grok received the same complete candidate with Markdown table cells rendered as text to avoid browser indentation loss; both exact prompts and editor capture are retained. R3 uses that representation for both providers.