Capability + backlog rulings: 2026-08-14 (evening Q&A)
Owner Q&A, 2026-08-14. Closes the missing-capabilities register and most of the scattered-rulings docket.
Missing capabilities (C-series)
Section titled “Missing capabilities (C-series)”★ AMENDED same evening, owner reclassification: “these are insurance
policies that belong in scripts that can eventually be removed once things
are stable enough where these type of issues don’t happen.” Reapers and
logscan are campaign insurance, script-tier, sunsetable, never product
surface. They live in scripts//test tooling, grow no product verbs, join
no CI gates, and each carries an explicit retirement condition:
- Reapers retire per-cloud once the product teardown path is trustworthy there (flag-day-3 teardown jobs + M7 destroy protections proven, and N consecutive campaigns leak-free on that cloud). The product answer to leaked resources is the armed teardown path; the reaper only bridges until it has earned trust. (Portal/managed provisioning relies on the product path, never the reaper.)
- logscan downgrades to on-demand (and eventually retires) once its rule classes stop firing; each rule that fires is a defect to fix at the source (package/convergence), and a rule that stays quiet for months is a candidate for deletion with its fixed defect.
| # | ruling | consequence |
|---|---|---|
| C1 | Build all three missing reapers (proxmox, cloudstack, alibaba) as script-tier campaign tooling (amended). No CI parity guard. | CS/alibaba live-verified when credentials exist; retirement per the sunset condition above. |
| C2 | logscan runs SCHEDULED (daily) on both estates via script + timer, report persisted, loud non-zero on new dirty findings. Not a release gate; not product surface (amended). | Standing detector for the unstable era; every firing rule feeds a source fix; sunset per above. |
| C3 | Block-volume snapshots: build for the LIVE six clouds (hetzner, aws, azure, do, scaleway, exoscale). | Pre-move safety points + faster restores; complements restic. |
| C4 | Live host-change machinery W2–W9: build now. | The only path to changing an estate’s domain without re-genesis. |
| C5 | hostinger firewall: REFUSE the variable: loud plan-time error naming the upstream limitation. | No silently-open boxes. |
| C6 | Sequencing ratified: (1) reapers + hostinger refusal + logscan scheduling → (2) snapshots → (3) host-change W2–W9. |
The DNS magic socket (ruled, owner-defined)
Section titled “The DNS magic socket (ruled, owner-defined)”SHC writes DNS records (mail DNS first: MX/SPF/DKIM/DMARC) via a dns
magic socket: an app declares a dns.plug.yaml (e.g. mailcow), the
operator binds it (-i dns=DNS), and the socket performs the provider
writes on the app’s behalf; an app never touches provider credentials.
Grant-gated: the DNS provider must be granted to the particular
realm/tenant through the same global-scope grant machinery as connection
grants (K3 family). No bare general-purpose shc dns create/update/delete
verbs; writes happen only through the socket; the detect-only audit stays.
System-app split (ruled)
Section titled “System-app split (ruled)”★ SCOPE CLARIFIED 2026-08-18: this ruling is about VISIBILITY, not
placement. kind: tells a catalogue walker who may SEE a package; it never
meant “vendor infra”. The orthogonal placement axis (builtin/ = every
cluster, deploy/ = BitSpur’s own infra deployments) is ruled separately in
docs/decisions/2026-08-18-builtin-vs-deploy-placement.md, which also records
why builtin/license cannot move to deploy/ without deleting the license
socket.
The catalogue app and the system app split into distinct kinds; “pinned” means the recorded package digest. keycloak/traefik/openobserve/branding become builtin-only system apps invisible to catalogue walkers; postgres keeps its ruled dual nature (builtin AND published catalogue app). The §0.2 materialised-builtin false-red trap dies structurally.
2026-08-07 brief ledger, closed
Section titled “2026-08-07 brief ledger, closed”| brief | ruling |
|---|---|
| Backup creds + retention | 7/4/12/5 retention RATIFIED. Per-estate Hetzner object-storage credentials are the owner’s console action (B6); vault swap + verification prepared on his signal. |
| Entitlements | Grant-then-roll: issue branding/white_label grants first, then roll the license-broker image on both estates. |
| x9s HUD | Build the 8 missing views in x9s NOW, then remove the old HUD in the same program. No parity wait, no capability loss. |
| Launcher cookie | Widening Domain is REJECTED permanently: the cookie carries a live Keycloak access token forward-auth accepts as a bearer; host-scoped forever. This section is the decision record. |
| Legal entity | ”BitSpur” (not “BitSpur, Inc”). LICENSE placeholder is replaced; the EE license text and ce contributor grant unblock. |
Integration/bridge rulings
Section titled “Integration/bridge rulings”| topic | ruling |
|---|---|
| Frappe app delivery | Owner asked for the no-legacy long-term shape: bakeApps=true is the target: apps/ IS the image every boot, no drifting volume seed. New installs get it as default; the two live benches (bit/ffx) converge via a consented reinstall/migration scheduled with the owner, not a hot patch. (Directional per the no-legacy doctrine M12; confirm the bench migration window before executing.) |
| Calendar effector | Long-term no-fallback shape: rung B (login-time convergence, zero stored credentials). Prove the audience-mapper/bearer-CalDAV probes; if a probe fails, fix the blocker rather than shipping helper-app A. |
| Notification bus | Hookshot for everything: one delivery path: wazuh, gitlab, and GlitchTip all route through the hookshot bridge (owner overrode the phase-0-native recommendation). First deployment proves it. |
| Flag days | All three blessed: wire-dialect flag day (in flight, M12), config-vs-state migration on its verdict table, and teardown arming (the 21 dead provider-side teardown jobs go live) gated behind the M7 destroy protections. |
| Ingress | shc move traefik becomes SUPPORTED: lift the refusal, build the explicit DNS re-point step and the ACME-store answer. |
Archive registers, closed
Section titled “Archive registers, closed”| register | ruling |
|---|---|
| §20.5 | Fix the backup-completed-on-nothing sibling now; node-affinity waits for a multi-node-placement estate (trigger named). |
| §25.4 | Resolve LeaderNodeID + delete the structurally-unanswerable Term field. Rollup/HUD residue stays registered. |
| §27.7 | Departure-time warning and the full promote-before-departure orchestration: build both now. |
| §29.3 | Suffrage back-fill at boot + delete the unreachable promote fence. |
| §45.6 | The three by-construction package fixes (nginx worker_processes auto ×6, jvb -Xmx3072m, wazuh-indexer 512M-vs-1G) plus the ~60-app vendor-minimum sweep. |
| §52.4/§52.6 | Probe one node per estate read-only; both clean (epoch 2, zero legacy) → delete shc vault migrate --crypto-format 1 per the no-legacy doctrine. Unclean/unreadable → verb stays, report back. |
Still open from the docket: mail-DNS is now designed (socket above); frappe bench migration window and any remaining transcript-only briefs are tracked in their own lanes.