coulomb-social/docs/usecases/first-transfer-review.md

First use-case transfer — user review

Milestone: I can continue a nominated piece of my existing work on the new app, recognize the content, organize it, share it with the intended people and trust it to remain available. I can see exactly which old use cases can move and which still need rebuilding.

Status: ReichelAg weekly calls (UC-008) accepted for productive use on 2026-10-08, Helm revision16. User accepts duplication/naming, editing, clipboard paste into the usual mail client, and page/list visuals. See the acceptance receipt. WP-0008 is finished. Broader cohort, sharing/portability and recovery requirements are owned by WP-0014, WP-0013 and WP-0012 respectively. Bubble retirement remains a separate decision.

First nominated workflow — ReichelAg weekly founder call

The user's first concrete use case is documented in reichelag-weekly-call.md (UC-008). Prepare a new weekly-call agenda by duplicating the full latest protocol, edit it by hand, record the call, then copy its content and paste into an external email draft for manual distribution. Page duplication and clipboard copy are separate actions. The nominated weekly-call workflow is now accepted on the live release.

Review preparation (prepared in WP-0008; follow-ups in WP-0012–0014)

• Review host: https://app.coulomb.social/; retained one-writer content release is live. Current immutable release: sharing/portability revision16 receipt.
• Nominated workspace: ReichelAg; latest real protocol and explicit personal-owner grant imported. Wider Bubble-space reconciliation remains WP-0014-T01.
• Workflow confirmed by user description and ongoing review. Original clipboard observed directly and matched exactly; wider Bubble UI inventory remains WP-0014-T02.
• Migrated content/visual/link reconciliation and accepted differences: pending WP-0014-T01 / WP-0013-T02. Private page covers are visible per founder review. Missing Spaces-list preview is corrected in revision15; live owner preview/hash preservation and actual production-pair isolated recovery pass. Page/list visuals are accepted for weekly calls.
• Writer, reader and outsider access; owner sharing/revocation, personal export and retained-content exit UI are deployed as revision16 and browser-tested. Productive user review remains WP-0013-T03; see implementation review.
• Content restart durability and paired real-content isolated restore verified. Durable backup custody/retention and operational rollback remain WP-0012.

Use a private companion record for real content and account identities. Record only non-secret receipts, stable journey IDs and user verdicts here.

Walkthrough and expected user results

Journey	What you do	What you should experience	Review verdict
UC-008	Duplicate the latest ReichelAg protocol, name it, edit/write the new call notes, copy content, paste into your usual email client	Previous entry intact; new agenda/protocol editable; pasted notes usable without app chrome	Accepted for weekly calls, 2026-10-08 (revision16)
UC-001	Sign in (or register) and find the nominated space	Reach the right work without a Bubble login dependency	Existing personal sign-in accepted; first space visible; broader registration review remains separate
UC-002	Open the same representative page in Bubble and the new app	Recognizable title, abstract, visual, body and useful navigation; differences clearly disclosed	Pending
UC-003	Edit a page, make a new page and update space details; revisit after restart	Changes remain readable and usable without manual Git/database actions	Pending
UC-004	Copy into a second space, edit the copy, then move another page	Copy is independent; moved page leaves source and appears intact at destination; permissions remain correct	Pending
UC-005	Repeat as reader, then outsider; try editing/copy/move URLs directly	Reader sees shared content and read-only controls; changes denied; outsider sees no private content	Pending
UC-006	Export app-local account information; review leaving/ownership outcome	Understand what can be taken away and what deletion retains/transfers before confirming it	Pending
UC-007	Inspect the restored isolated workspace and permission checks	Content and access match the agreed recovery point; recovery delay is known	Pending

For each row record: original steps observed, new steps performed, release/date, result (pass, gap, not tested), gap work-record ID, user verdict (accepted for transfer, needs rebuilding, deferred) and explicit acceptance reference. Prepared/implemented/tested never automatically means accepted.

After your review

Move only accepted use cases and their agreed content/cohort. Decide where new work happens for each accepted journey; keep the Bubble equivalent available according to the agreed rollback/reference policy. File rejected differences as live work, select the next user-prioritized cohort and repeat. Retiring Bubble entirely is a separate final decision after every retained use case has been transferred or explicitly discontinued by you.