the-custodian/workplans/CUST-WP-0058-business-platform-enablement.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	state_hub_workstream_id
CUST-WP-0058	workplan	Business platform enablement — decisions, service contract, client plane	infotech	the-custodian	proposed	codex	custodian	2026-07-10	2026-07-10	13a991a3-6d98-4749-9639-dd4687cce55e

CUST-WP-0058 — Business Platform Enablement

Goal

Enable Binky Hedgehog GmbH commercial offerings on the coulomb/HelixForge platform by (a) resolving the three gating platform decisions, (b) codifying what every client-facing business application must provide, and (c) scoping the missing client/commercial management plane — so that vergabe-teilnahme (first business project) and the coulomb.social rebuild (second) land on a governed, extensible path rather than ad hoc wiring.

This is a coordination workplan: implementation lands in the owning repos (vergabe-teilnahme, fin-hub, ops-hub, core-hub, railiance repos). The Custodian owns decisions, canon, and cross-repo sequencing per ADR-001.

Background

• Hub-ecosystem review 2026-07-09: architecture sound (hub-core / state-hub / core-hub compose-don't-merge, CUST-WP-0057); gaps are a missing client/commercial plane and three unrecorded decisions.
• Decision framing: docs/business-platform-decision-records.md (DR-1 tenancy, DR-2 coulomb.social shape, DR-3 external identity).
• fin-hub MVP (cost tracking, runway, RaaS pricing MVP) shipped via FIN-WP-0000/0001; client-facing billing remains open.
• Delivery lane pattern proven for Core Hub (docs/core-hub-helixforge-build-alignment.md): commit-SHA images → gitea.coulomb.social registry → railiance-apps release values → evidence gates.

Non-goals

• Implementing vergabe-teilnahme features (owned by that repo)
• Rebuilding coulomb.social (blocked on DR-2; owned by its future repo)
• Building client-hub (this plan only scopes it; implementation gets its own workplan in the owning repo)
• Payment execution / invoicing mechanics (fin-hub scope decision)

Tasks

T01 — Facilitate and record DR-1: tenancy model

id: CUST-WP-0058-T01
status: todo
priority: high
state_hub_task_id: "b7130553-a3d9-4dfd-91d7-6edb503bab58"

Register DR-1 as a pending State Hub decision (custodian topic); present options to Bernd; on resolution update docs/business-platform-decision-records.md and resolve_decision(). Propagate the outcome into vergabe-teilnahme's SCOPE if it changes.

T02 — Facilitate and record DR-2: coulomb.social architecture

id: CUST-WP-0058-T02
status: todo
priority: medium
state_hub_task_id: "ec09753e-ecef-4368-af5d-5e295cdbda1e"

Register DR-2 as a pending State Hub decision. If resolution is "defer until pilot" (recommended), set the revisit condition to T07 completion and keep the decision open with that note. Include a pointer to the required bubble.io data-migration assessment either way.

T03 — Facilitate and record DR-3: external identity path

id: CUST-WP-0058-T03
status: todo
priority: high
state_hub_task_id: "ffead70c-2179-46ba-a70a-cf13be87eef8"

Register DR-3 as a pending State Hub decision. On resolution, message the NetKingdom lane so NK-WP-0011 gains concrete activation triggers (or is activated). Record the identity mode required per app class for T04.

T04 — Author business-app service contract (canon standard)

id: CUST-WP-0058-T04
status: wait
priority: high
state_hub_task_id: "a3cec70c-04a1-42a9-a6b0-3d2943b73968"

Draft canon/standards/business-app-service-contract_v0.1.md (proposal → human review, per canon gating): obligations every client-facing app must meet — build evidence (commit-SHA images, registry), backup/restore hooks into ops-hub, incident/runbook registration, cost attribution keys for fin-hub, identity mode (from DR-3), data-protection baseline, and instance provisioning/upgrade duties (from DR-1). vergabe-teilnahme is the reference implementation. Waits on: DR-1 and DR-3 resolution (T01, T03).

T05 — Scope client-hub (client/commercial plane)

id: CUST-WP-0058-T05
status: wait
priority: medium
state_hub_task_id: "442b7f81-44c7-4301-9466-c99c240c4e49"

Write a scoping note (docs/client-hub-scoping.md) for the missing fourth management plane: client registry, contracts/entitlements, client↔instance mapping, support/SLA state. Default shape: core-hub extension (ops-hub pattern) reusing hub-core primitives — justify any deviation. Output is a draft workplan skeleton for the owning repo, not implementation. Waits on: DR-1 resolution (T01) — tenancy determines the client↔instance model.

T06 — fin-hub client-billing gap assessment

id: CUST-WP-0058-T06
status: todo
priority: medium
state_hub_task_id: "3a63f122-2398-4149-8458-eb5a3a54627c"

Review FIN-WP-0000/0001 outcomes against what commercial clients need: per-client cost attribution, price-to-invoice data flow, and where the fin-hub "no payment execution / no multi-tenant billing" boundary should move (or which external system owns billing). Output: gap list + proposed FIN-WP workplan skeleton posted to the fin-hub lane.

T07 — Delivery-lane pilot: vergabe-teilnahme end-to-end

id: CUST-WP-0058-T07
status: wait
priority: high
state_hub_task_id: "d07443ab-76b1-4d66-981c-e83fcb915c0d"

Coordinate one full pass of the business delivery lane with a real (or pilot) client instance: vergabe-teilnahme build → immutable image in gitea.coulomb.social registry → railiance-apps release values → deployed instance → ops-hub evidence (endpoint, backup, smoke) → fin-hub cost attribution. Implementation tasks live in the owning repos; this task tracks sequencing and captures the evidence bundle under docs/evidence/. Feeds DR-2 resolution. Waits on: T01 (tenancy) and T04 (contract draft — may proceed in parallel once DR-1 is resolved).

T08 — Closeout: decisions recorded, downstream workplans seeded

id: CUST-WP-0058-T08
status: wait
priority: low
state_hub_task_id: "203f7afa-0162-4906-a4f2-c4789cd127bc"

Verify all three DRs resolved (or explicitly deferred with revisit conditions), the service contract standard is merged in canon, and downstream workplan skeletons (client-hub, fin-hub billing, coulomb.social rebuild + bubble.io migration) are handed to their owning repos. Update SCOPE.md Current State; archive this plan.

Sequencing

T01 (DR-1) ──┬──> T04 (contract) ──> T07 (pilot) ──> DR-2 evidence ──> T02 closes
             └──> T05 (client-hub scope)
T03 (DR-3) ──┘
T06 (fin-hub gap) — independent, anytime
T08 — last

References

• docs/business-platform-decision-records.md — DR-1/2/3 framing
• docs/hub-ecosystem-architecture.md — three-layer hub canon
• docs/core-hub-helixforge-build-alignment.md — delivery lane pattern
• /home/worsch/vergabe-teilnahme/SCOPE.md — first business app
• /home/worsch/fin-hub/workplans/ — FIN-WP-0000/0001 (finished)