All 8 tasks done. Handoffs delivered to fin-hub, core-hub, vergabe-teilnahme, ops-hub, railiance-apps (backup HIGH), NetKingdom. coulomb.social rebuild seeded (docs/coulomb-social-rebuild-seed.md). SCOPE.md Current State updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
47 lines
1.9 KiB
Markdown
47 lines
1.9 KiB
Markdown
# 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
|
||
|
||
Seed only — **no owning repo exists yet.** When the rebuild starts, create
|
||
the repo (suggested slug `coulomb-social`), register it
|
||
(`custodian register-project`, domain `coulomb_social`), and originate the
|
||
workplan files there per ADR-001. This document then becomes a pointer.
|
||
|
||
## 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)
|