_maybe_update_replicated_unlocked never checks t_invalid, so a claim that a signed contradiction verdict has marked invalid can still climb to REPLICATED through convergence detection, and it pulls an honest peer up with it.
Three gaps line up:
status and asserter_keyid (core.py:1339-1352); an invalidated but still-open new claim passes.status = 'open', unresolved = 0, and transparency_logged = 1 but has no t_invalid predicate (core.py:1390-1410), so an invalidated existing claim qualifies as a convergence partner.status = 'open' (core.py:1422-1426), leaving a TOCTOU window even after the SELECT is fixed.A signed contradiction verdict is meant to be terminal for the trust ladder: validate_claim refuses to promote a t_invalid claim to ESTABLISHED, and record_replication_verdict already gates its promotion UPDATE on t_invalid IS NULL. Convergence promotion is the one path that ignores the verdict. Reproduced at runtime: contradict claim X (t_invalid set, still PRELIMINARY), then assert peer Y sharing X's ESTABLISHED anchor; both X and Y land at REPLICATED, with X's t_invalid still set.
High. A refuted claim re-enters the trust ladder at REPLICATED after its contradiction, and it serves as the corroborating peer that promotes an honest claim. Both outcomes contradict the documented refutation model, and REPLICATED is the input to further validation.
mareforma/db/core.py:1339 new-claim short-circuit checks status and asserter_keyid but not t_invalidmareforma/db/core.py:1390 candidate-peer SELECT WHERE clause has no t_invalid IS NULL predicatemareforma/db/core.py:1422 promotion UPDATE gates on status = 'open' only, reopening the window between SELECT and UPDATETreat t_invalid the way the neighboring code already...
0.3.8Exploitability
AV:LAC:LAT:PPR:LUI:NVulnerable System
VC:NVI:HVA:NSubsequent System
SC:NSI:HSA:N6.8/CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:NOther