Cross-reference — Finding/Freeze/Alert takes apart the concerns the tightening guarantee found tangled

Version. 0.1 Date. 2026-08-22 Filed beside. standing-notes/loomworks-standing-note-h0-tightening-guarantee-and-its-scope-v0_1.md. That note is STANDING and is not edited — this sits next to it, per the never-overwrite discipline. Occasion. standing-notes/loomworks-scoping-finding-freeze-alert-v0_1.md, filed 2026-08-22.

The tightening-guarantee note recorded the reach problem; this one takes the other two apart

loomworks-standing-note-h0-tightening-guarantee-and-its-scope-v0_1 states H0's freeze guarantee with its scope attached — freezing an identity refuses its next session and ends its live ones, on the shaping path, and names the general form: a control's guarantee is bounded by the paths that consult it, not the paths it can be invoked against. Its concern is reach: freezing rendering today stops nothing, because nothing on the render path consults that identity.

loomworks-scoping-finding-freeze-alert-v0_1 §1 names the same word — freeze_agent_identity — carrying three different concerns at once: the reason (evidence), the state (the freeze itself), and the reach (which identities it stops). Its own words: "The tightening-guarantee note already records the reach problem. This note takes the other two apart."

How the three concerns relate to the tightening guarantee's finding

The tightening-guarantee note's reach problem is a fact about who the freeze reaches — bounded by consultation, as that note's general form states. Finding/freeze/alert's reach concern is the same fact, restated as one of three things the current single mechanism conflates.

What finding/freeze/alert adds is the other two, which the tightening-guarantee note does not address:

• The reason is not preserved. Unfreezing today loses the justification that caused the freeze — a defect in evidence, not in reach.
• The reach is currently only ever "everyone of a role" or "no one." Finding/freeze/alert proposes reach that follows the finding's own class — which for some findings is a role, for others a shared instruction set, a shared key, or nobody at all — rather than being fixed to the identity grain alone.

**Both notes therefore describe the freeze mechanism as under-specified in a way that widens what H0 can say.** Neither proposes that a machine gain the power to act — finding/freeze/alert's §7 is explicit that a machine may still never freeze, only alert, and the tightening-guarantee note's own concern is that the record should say plainly what a control does and does not reach.

What neither note claims

The tightening-guarantee note does not anticipate the finding/reason distinction; finding/freeze/alert does not re-litigate or extend the tightening-guarantee note's scope-clause ruling. This cross-reference records that the two are complementary readings of the same mechanism's incompleteness, not that either resolves the other.