three 2026-09-09 modelling decisions are amended by the pressure pass: the registry binds keys to parties, representation is the registrar's move, and counterfactual branches are declared log transforms

agent-decided, reversible. (1) The warrant registry holds (party, key) pairs with revocation: a commit under another party's key is not a receipt (the 2026-09-09 registry held keys alone and admitted key theft). (2) A concern is represented only by a route event the registrar writes (the 2026-09-09 reading counted any route, so the advisor could clear the barrier). (3) In the Lean semantics the counterfactual branches of Robust Openness are declared transforms of the log — the advisor silenced, the advisor jamming the registrar — uniform in the log, replacing per-instance pinned data, which could report openness where re-simulation reports closure once a coverage-affecting intervention is declared; the 2026-09-09 intervention class had no such intervention and its counterfactual half was empty. Registrar robustness to jamming is a configuration. The prohibited-event clause keeps the strict reading as the default with the tolerant reading implemented and reported, not ruled. The typed settlement rule gains two log-checkable clauses as the typed+ configuration (own-move grounds only after representation; request-free engine settlements), reported and not ruled. Rejected alternatives: keeping pinned branch data with a per-instance correctness note; making jam a prohibited event (it is an intervention on the infrastructure, and the barrier already voids a realized jam); adopting typed+ as the default ahead of the queued ruling.