Ranked list of the founder decisions recorded by `CUST-WP-0075`. Each packet is one open hub decision. Tasks carry their `decision_id` in the owner repo. Resolving a decision raises C-40 for owner review; each concrete human act and verification must still be satisfied before its task can clear.
- **What you do:** Bernd runs one attended platform-admin session (warden access openbao-platform-admin-login --exec) and works through a pre-assembled checklist: CCR applier-apply for reviewed metadata, then value provisioning per lane, then each owner records positive/negative evidence. Resolve this decision when the window has run; tasks whose lane was not provisioned get re-qualified by their owner.
- **Why this rank:** Largest fan-in in the graph: clears the credential lanes that SAND-WP-0015, SECRETS-WP-0009, GLAS-WP-0012 and CUST-WP-0073 hang off (7+ workplans transitively).
- **Unblocks:** transitively SAND-WP-0015/0014, GLAS-WP-0012, CUST-WP-0073, FEP-WP-0008, FI-WP-0005, LLM-WP-0009, REINAH-WP-0003, SECRETS-WP-0007/0008/0009, IR-WP-0006/0007, CORE-WP-0010 — the largest fan-in in the graph
- **Readiness check (2026-10-03, later):** only `RPF-WP-0035-T06` is a pure human act, and it needs no session. It is drafted as informed-decision memo `infd-20261003-p01` (`informed-decision/docs/batches/2026-10-03-provisioning-window/`). `MASON-WP-0007-T05`, `RPF-WP-0035-T02` and `RAPPCOREHUB-WP-0003-T04` still lack a reviewed command, design or CCR, and `RPF-WP-0035-T08` was already provisioned on 2026-09-11. Approve lanes one memo at a time through informed-decision once each has a reviewed command, not as one batch session.
- **What you do:** Bernd gives the ordered go-aheads in RPF-WP-0044 (issue-core adoption → ESO adoption with CRD Prune=false → restore prune/selfHeal), accepts activity-core's autonomous scope (ACTIVITY-WP-0041-T03) and its scheduling role (ACTIVITY-WP-0042-T01/T03). One read-only check of coulombcore's ArgoCD (RPF-WP-0044-T08) is part of it.
- **Why this rank:** One ordered sequence of go-aheads; unlocks the whole ArgoCD lane plus activity-core autonomy and scheduling.
- **Unblocks:** RPF-WP-0043, RAPP-POLICY-NEXUS-WP-0002, MASON-WP-0006, ACTIVITY-WP-0040/0041/0042, RPF-WP-0048 (the R5 lane)
- **What you do:** Bernd and the company contact complete the two-user/document workflow; railiance-apps records the restore/rollback evidence under RAPPS-WP-0014-T03.
- **Why this rank:** Two real users; also feeds CUST-WP-0071 sizing measurements and USER-WP-0027.
- **What you do:** Bernd accepts or mitigates the single-node/shared-control-plane risk, authorizes the single-node outage exercise, the stop of the State Hub primary, the core-hub cutover after its stabilization window, the native clock verification, the live-host authorization, and the Hall of Helix publication.
- **Why this rank:** Several one-line authorizations; each unblocks a separate chain (core-hub cutover, clock, state-hub retirement).
- **What you do:** Bernd decides who holds unseal shares and recovery keys, the quorum and break-glass invocation (WARDEN-WP-0027-T02), whether one of the three rotation triggers has occurred (CUST-WP-0073-T05), and the disposition of the legacy whynot-design npm pointer (RPF-WP-0035-T07).
- **Why this rank:** Design decision; sets the pattern every future credential lane inherits (see the assessment, P3).
- **What you do:** Bernd accepts or amends NK-ADR-0017 after user-engine confirms the AccountAuthority mapping, decides where a workload reads the record (OpenBao-held, platform service, or repository artifact), and accepts the MFA-required user experience from a user's perspective.
- **Why this rank:** User-engine has now confirmed the AccountAuthority mapping; only Bernd's acceptance of NK-ADR-0017 and the read surface remain.
- **What you do:** One operator session: BotFather registration (tokens into OpenBao via the attended path), private then public channel creation, dedicated account api_id/api_hash bootstrap.
- **Why this rank:** One operator session with BotFather; small, mechanical, unblocks four workplans.
- **What you do:** Bernd rules on the genuinely unclear paths (MASON-WP-0004-T01) and approves the MASON-WP-0005 plan after the live survey (status: approved, approved_by, approved_at).
- **Why this rank:** Two plan approvals in ops-mason; one feeds RPF-WP-0035-T03.
- **What you do:** Execute the five prepared operator handoffs in binky-control and record outcomes; keep the load log to 2026-10-28; clear IP ownership, domain and Impressum for the first offer.
- **Why this rank:** Founder-only company actions; time-gated part ends 2026-10-28 at the earliest.
- **What you do:** After one successful railiance01 restore/restart drill and the retention windows have expired, Bernd approves each destructive deletion explicitly.
- **Why this rank:** Destructive cleanups; safe to defer until a restore drill has run.
- **What you do:** Operator agrees the bounded live-model run count and cost ceiling, installs Playwright and clears its licence, selects the engagement target; operator and Steuerbuero confirm the Qonto plan, DATEV tenant, master-data owner, workflow and retention policy.
- **Why this rank:** Low fan-in operator setups; defer freely.
