DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path standing-notes/loomworks-scoping-finding-freeze-alert-meets-per-binding-session-minting-v0_1.md

Cross-reference — Finding/Freeze/Alert meets the identity-grain question from the freeze direction

Version. 0.1 Date. 2026-08-22 Filed beside. standing-notes/loomworks-scoping-per-binding-session-minting-v0_2.md. That note 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 two notes arrive at the same junction from opposite directions

Per-binding session minting starts from what identity does a per-binding actor mint against and finds that the answer requires per-identity granularity the seeded roster does not currently offer — one row per role, platform-wide, fixed at migration time.

Finding, freeze, alert starts from can we freeze one agent and alert the rest and arrives at the identical precondition from the opposite side: freezing one and alerting others both require that "one" be freezable on its own, and today only role-grain freezing exists.

Neither note is answering the other's question. Both are blocked on the same fact.

The shared precondition, stated once so it is not restated twice

Both notes' central dependency is the same sentence: the identity roster holds one row per role, seeded by migration 0113, and the SEED ruling forbids runtime minting. Per-binding session minting §1 states this as the blocker between two identity models that do not line up. Finding/freeze/alert §6 states it as the precondition nothing else in that note can build against.

A ruling that answers one note's precondition answers the other's. If the roster exception loomworks-scoping-finding-freeze-alert-v0_1 §6 asks for — an identity row created when an operator declares a Shaping or a render type — is granted, loomworks-scoping-per-binding-session-minting-v0_2's question 1 (do the two registers converge?) gets its converging mechanism, and render_specialist_binding's per-binding identities (§1b of that note) become exactly the kind of human-declared, non-self-minted identity §6 here is asking to be allowed.

What neither note claims

Neither claims the other's ruling is already made. Per-binding session minting's five open questions and finding/freeze/alert's §6 both remain the Operator's. This cross-reference records only that they are, underneath, one question asked twice.