# Round 12 review — GLM (management boundary follow-up)

**Scope reviewed:** Sections 1, 2, 3, 15, 16 of revision 18, plus the attached section 5/17 cross-section context. Independent read of the current text; no runtime verification claimed.

**Prior-disposition incorporation verified:**

- Round-11 Opus 1 / K3 3 (gateway mapping authority): fully present. The setup controller bootstraps owner-scoped trust with a separately scoped provisioning credential (§16 "Gateway ownership and recipient authority"); the root owns the recipient set and signs only typed control objects under a distinct purpose, bound to owner/Mac/gateway/epoch/revision/operation ID/expiry; the submission credential cannot mutate mappings; epoch/revision/operation-ID idempotency, ack-of-applied-revision, durable outbox, expired-envelope regeneration without revision lowering, uninstall tombstones, and fresh-epoch reactivation are all stated. The credential table is consistent with the prose on all seven rows.
- Round-11 GLM 1 (cloudflared placement): present — root-owned placement excluding interactive-user and admin-group writes for all service-account executables, dependencies, config, registrations, and update paths, with signed release inventory and no user-writable self-update.
- The disposition's explicit three-way distinction (immediate Mac revocation vs. gateway acknowledgment vs. already-queued provider pushes) appears verbatim in §15 "Bind and rotate registration tokens" and §16 "Synchronize lifecycle changes and cleanup"; the two sections agree