coulomb-social is registered under domain communication / topic coulomb-social; CSOC-WP-0001 lives in that repo. Convert the seed doc from "no owning repo" to a historical pointer.
2 KiB
coulomb.social Rebuild — Workplan Seed
Created: 2026-07-10 (CUST-WP-0058-T08 closeout)
Decision basis: DR-2 B — standalone application; DR-1 C tenancy;
DR-3 A app-local accounts. Contract:
canon/standards/business-app-service-contract_v0.1.md.
Status
Owning repo exists: coulomb-social
(forgejo-remote:coulomb/coulomb-social.git, local ~/coulomb-social).
Registered in State Hub under domain communication, topic coulomb-social
(topic id 36c7421b-c537-4723-bf75-42a3ebc6a1dc). Workplans originate there
per ADR-001 — start with CSOC-WP-0001-bubble-io-exit-assessment.md.
This document is a historical seed / pointer; do not open new work here.
Shape (decided)
Standalone service on the proven business delivery lane
(vergabe-teilnahme evidence:
docs/evidence/vergabe-teilnahme-delivery-lane-20260710.json):
own repo → commit-SHA images → gitea.coulomb.social/coulomb/coulomb-social
→ railiance-apps release values → railiance01. Binky Hedgehog GmbH is the
client (client #1 model). App-local member accounts (DR-3 A; §2.3 bounded
auth module for a later OIDC switch).
Proposed workplan skeletons
CSOC-WP-0001 — bubble.io exit assessment
T01 Inventory current bubble.io app: pages, workflows, data types,
integrations, external services (todo, high)
T02 Data export: full dump from bubble.io, schema mapping to a
relational model (todo, high)
T03 Feature cut decision: rebuild-as-is vs reduced v1 scope
(human gate — Bernd) (wait, high)
T04 Migration rehearsal: import exported data into the v1 schema on a
dev instance (todo, medium)
CSOC-WP-0002 — coulomb.social v1 implementation
(scoped after CSOC-WP-0001-T03; must satisfy service contract §1–§6,
incl. tenant keying from migration one and member-account export/delete)
Preconditions before serving members
- railiance-apps backup gap closed (§4.2 — HIGH, msg
a1957cce…) - ops-hub registration at deploy (§4.1)
- fin-hub cost attribution key (§5.1, FIN-WP-0002)