Broker & privileged-capability rulings: 2026-08-14
Owner Q&A, 2026-08-14. Rules the open halves of
docs/proposals/2026-08-09-mailbox-reconciler.md (§3),
2026-08-08-tenant-container-runtime.md, 2026-08-08-in-stack-exec-broker.md,
and the keycloakAdmin-socket question from the reconciler/identity-broker
corpus.
| # | ruling | consequence |
|---|---|---|
| K1 | Mailbox reconciler deletion ceiling: DISABLE. Mail kept, login/delivery stop, return reactivates. Full delete stays forbidden until a proven mailcow restore exists. | Closes §3. Probes P6/P7 spec against disable. |
| K2 | Disable auto-revokes the departed user’s app passwords. | Complete deprovisioning in one action. |
| K3 | ★ THE PRIVILEGED-GRANT MODEL (owner-defined): security-sensitive requests from tenant apps (privileged: true, docker.sock mounts, host mounts, dangerous cap_add) are blocked by default and allowed only via a GRANT in global-scope config, exactly like connection grants: master tenant grants per tenant; the key cannot be set at tenant scope; master tenant has it implicitly. One blanket grant surface governs the class. | This is the general answer for every “may this app do something dangerous” question, including nested/dind-shaped requests: allowed for master tenant and any tenant granted it, never self-granted. The former “refuse nested outright” framing is superseded by the grant model. |
| K4 | Job-container broker (apps ask SHC to run per-job containers: gitlab-runner CI, windmill docker jobs): BUILD, gated by GRANT + PRO tier. A container_runtime feature key (born paid, no-rug-safe) AND the K3 master-tenant grant are both required. | Free/Hobby estates keep shell executors. |
| K5 | keycloakAdmin socket: build NOW. Per-consumer service-account clients with named realm-management roles. | Three consumers stop holding full master-admin credentials; built before the reconciler probes so they validate the real credential shape. |
| K6 | Broker order: “do them all” (owner): cert-delivery live proof, reconciler probe campaign, keycloakAdmin socket, and the job-container broker all proceed in parallel lanes. | |
| K7 | (default, not asked) Exec broker stays parked behind its second-live-consumer bar. | Mailcow’s dead UI pages are a separate COMPOSE_PROJECT_NAME issue. |
| K8 | (default, not asked) fusionpbx adopts certs: after the mailcow live proof, one variable at a time. |
shc@docs:~$