# Round 22 review — GLM compatibility scope (sections 1, 2, 17, 18)

## Prior disposition verification (revision 28)

**Opus F1 (witness-fault ordering):** Present. §18 acceptance ("Inject transient witness faults… immediate restrictive enforcement, delayed permissive effects, automatic intent reconciliation, and accurate pending status") matches the accepted design; the phased-intent mechanism itself lives in out-of-scope sections and is not contradicted here.

**Opus F2 (starting-state submission):** Correctly merged. §17 defines the authenticated, submission-bound "Mac authority starting" no-admission result alongside "Update installing", with the same bounded readiness wait, distinct caller-deadline status, stdin/PTY preservation, fresh submission, and GUI recapture-while-present rules; the §18 acceptance bullet covers deadline exhaustion and unverified health hints. Timeouts and lost acknowledgments still never prove no-admission.

## Independent checks performed

- **Binding UX (§1):** Biometric table matches the frozen exceptions (LS allow-once/deny-once/cancel/dismiss without biometrics; every reusable rule, session/timed rules, and Forever with biometrics). No path in §17/§18 adds confirmations, forced physical access, re-pairing, shortened response windows, or manual steps; §18 explicitly preserves pairing across version drift, and update waits never shorten admitted requests' approval lifetimes.
- **Admission atomicity and retry safety (§17):** Quiescence check plus admission close is atomic with request creation and permit dispatch; only authenticated submission-bound no-admission results trigger transparent wait/resubmit; uncertain outcomes reconcile or report, never replay. Recapture after unexpected restart is restricted to established-never-consumed identities, preserves first-seen age and original expiry, and requires a fresh decision — consistent with the restart matrix and §1's one-decision-per-captured-action rule.
- **Floors and identity (§17):** Generation checks derive from OS-validated metadata on every privileged RPC; floor commits only via the activation transaction; anti-rollback is required to exist independently of the candidate binary, with the placement/key-custody gates carrying explicit failure/consultation paths rather than silent weakening.
- **Drain and automatic activation:** The automatic path never freezes admission while work is pending; user-initiated drain is cancellable from Mac and phone, shows blockers, and preserves normal request/command/permit lifetimes. No contradiction between the two paths.
- **§18 negotiation and contract selection:** Envelope and request-contract selection are separately authenticated; floor/feature exclusion precedes the maximize-eligible-phones tie-break (consistent with the v1/v1+v2 acceptance case); stale capability records can only reduce reachability; domain separation prevents status/approval cross-verification; canonical-byte and unknown-field rules are coherent.
- **Cross-references (§3 protected placement, §5–7 keys, §6 restart rule, §12 ledger recovery):** No conflicts introduced by the in-scope text.

No substantive actionable defects found; no correction needed, so none can worsen UX.

NO SUBSTANTIVE FINDINGS