# Round 11 disposition

Input: revision 17, SHA-256 `44df7a57e03b986728d9c3e6d082a7a43293b0a2e47a9dfaec2493bdfaec2380`.

All three reviewers completed with nonempty reports. Opus reported one low–medium finding, K3 three low findings, and GLM one low finding. Opus and K3 overlap on gateway mapping authority.

## Corrections in revision 18

| Finding | Disposition |
| --- | --- |
| Opus 1 / K3 3: gateway mapping authority | Accepted. Initial deployment is user-operated. A protected setup controller bootstraps owner-scoped gateway trust; root-signed typed control updates derive mappings from existing enrollment. The submission credential cannot change mappings. Phone tokens bind to enrollment and prove possession without biometrics. Epochs, revisions, acknowledgments, a durable outbox, and uninstall tombstones define replay and offline-revocation behavior. No manual operator step is allowed during normal lifecycle operations after setup. |
| GLM 1: cloudflared executable placement | Accepted. Protect all service-account executables, dependencies, configurations, registrations, and update paths against same-user replacement. Use approved absolute paths and protected updates, with a signed third-party release inventory. |
| K3 1: audit scope versus secret exclusions | Accepted. Audit uses closed action/scope classes. It never serializes actual destination, item, port, or UI values; the full signed scope remains memory-only. |
| K3 2: persistent local-routing override cannot be changed remotely | Accepted. Add phone controls for Automatic/At my Mac/Away under a separate narrow signed routing purpose. Preserve persistent overrides, no extra biometric or confirmation. Revision checks prevent stale controls from overriding concurrent choices. |

Explicitly distinguish immediate Mac revocation from gateway acknowledgment and already-queued provider delivery. Retries regenerate expired control envelopes from current desired state; they never resurrect obsolete mappings. Root signatures cannot be requested for arbitrary cloud bytes.

These changes preserve the existing approval UX and improve remote recovery. No forced pairing, physical access, command restriction, deadline reduction, or new biometric was introduced.