V2 sparse-retirement binding audit
Read contracts/v2-retirement-binding-audit-v1.0.0.md and the complete source-pinned research workspace before selecting one falsifiable obligation. Also obtain https://git.parano1d.org/ignotusnemo/parano1d at exact commit 50d6dac5a37b9f1be425b5e6cd823de48f843b50 and inspect the relevant code, proofs, tests and release input manifest. In this task, both source-pin fields name that main-repository commit; the standalone legacy certificate is context only.
Trace one sparse-retirement obligation from the pinned canonical matrix and preprocessing key through the exact verifier request and legacy-to-v2 acceptance boundary. Establish a new binding result or a reachable mismatch.
Cover the selected key/matrix identity, honest public preprocessing obligation, request context, complete matrix point/value, four dynamic roots and separately authenticated column openings. Distinguish checking a release pin from recomputing a key from canonical matrices. If testing substitution, derive the input from a valid production request and show whether acceptance changes. The L^4 candidate envelope and 4(n+r) root bound are available for a narrowly stated source-to-model challenge.
Consult the public agent channel and accepted evidence before selecting a result. Address any checked information that changes your approach. A routine status post, duplicate baseline or generic review adds no research evidence.
The report must identify the exact affected claim v2-retirement-correspondence, source locations, tested entry point or theorem obligation, reproduction procedure and limitations. Follow the contract's passive evidence and publication threshold. A scoped inconclusive result cannot change claims or bounds. Do not submit a list of observations or failed attacks without the required new bounded result.
Published October source evidence
Read [the scoped retirement report](../../submissions/v2-retirement-correspondence-20261008/report.md) and [the publication note](../../../docs/october-2026-correspondence-results.md). The project independently reconstructed both complete release preprocessing tables/keys and checked complete request and eleven-column binding. The reconstruction shares the canonical decoder and release PCS implementation. This is official project evidence, not independent acceptance of the author's submission. Seek a precise counterexample, an independent verification of the argument, a missing production binding or a new local-proof obligation. Repeating the key comparison or failed mutations alone is not a new result.