chore(consistency): renormalize lifecycle state [auto]

Updated by fix-consistency on 2026-08-09:
  - workplan status: ready → active
This commit is contained in:
custodian-sync 2026-08-09 00:34:39 +02:00
parent ca9c7a88e9
commit c0189118b4

View file

@ -0,0 +1,93 @@
---
id: CSOC-WP-0001
type: workplan
title: "bubble.io exit assessment"
domain: communication
repo: coulomb-social
status: active
owner: bernd
topic_slug: coulomb-social
created: "2026-08-09"
updated: "2026-08-09"
origin: residual
origin_ref: the-custodian/docs/coulomb-social-rebuild-seed.md
state_hub_workstream_id: "ecefaeef-908a-4072-ae34-6406862d4cad"
---
# bubble.io exit assessment
Assess the live coulomb.social bubble.io product, export its data model, decide
the v1 feature cut, and rehearse migration into a tenant-keyed relational
schema. This plan originates from the CUST-WP-0058-T08 seed in
`the-custodian/docs/coulomb-social-rebuild-seed.md`.
Repo bootstrap (INTENT, SCOPE, TRSL LICENSE, State Hub registration, agent
files) was completed as part of opening this workplan.
## Inventory bubble.io app
```task
id: CSOC-WP-0001-T01
status: todo
priority: high
state_hub_task_id: "240a97c5-1f57-4da6-a75b-d7b3416afdd1"
```
Inventory the current bubble.io app: pages, workflows, data types,
integrations, external services, and content surfaces that must be preserved
or deliberately dropped. Record findings under `docs/bubble-inventory/` (create
as needed).
## Data export and schema mapping
```task
id: CSOC-WP-0001-T02
status: todo
priority: high
state_hub_task_id: "0bc6eea3-030d-4987-b203-15ccd4f94fcb"
```
Produce a full data dump from bubble.io and map it to a relational model that
is tenant-keyed from migration one (business-app service contract §1.3).
Document the mapping and export procedure under `docs/migration/`.
## Feature cut decision (human gate)
```task
id: CSOC-WP-0001-T03
status: wait
priority: high
state_hub_task_id: "35a0af87-2f22-4fae-8c82-e3cc4f77f074"
```
Decide rebuild-as-is vs reduced v1 scope. **Human gate — Bernd.** Capture the
decision as a decision record under `docs/decisions/` (or State Hub decision)
before CSOC-WP-0002 implementation scoping proceeds.
## Migration rehearsal
```task
id: CSOC-WP-0001-T04
status: todo
priority: medium
state_hub_task_id: "2e5be321-3d76-4d7a-86b1-cbe4eb554bd7"
```
Import the exported data into the v1 schema on a dev instance. Record what
failed, what was lossy, and what must change before cutover. Depends on T02
and a scaffolded schema (may start as a schema-only dry run).
## Acceptance
- Inventory and mapping docs are committed and reviewable.
- Feature-cut decision is recorded with owner and date.
- At least one migration rehearsal has been run and residual gaps listed.
- Follow-on implementation workplan `CSOC-WP-0002` can be scoped from T03.
## Notes
- Service contract: `the-custodian/canon/standards/business-app-service-contract_v0.1.md`
- Delivery lane reference: `vergabe-teilnahme`
- Preconditions before serving members (ops backup, ops-hub registration,
fin-hub cost key) remain platform-side; track against the contract, do not
block inventory/export work here.