# Use-case catalogue — Bubble off-ramp

This is the working product backlog for finding, describing, rebuilding and
transferring use cases. A capability name or exported type does not prove an
actual current user workflow. Candidate journeys below derive from the dated
Bubble inventory/capability map; no fresh authenticated Bubble observation has
been performed in this session. All transfer decisions are **pending user review**. ReichelAg weekly founder
calls are now the first user-confirmed workflow: see reichelag-weekly-call.md.

Executable regression protection for established cases: registry.json and
[the test infrastructure](README.md). `make check` includes required browser
journeys; candidate entries below are not all established or protected yet.

## Transfer workflow

For every journey: capture a real example and original steps → describe actor,
goal, inputs/results and privacy → implement equivalent behavior → rehearse
representative data → compare old/new from the user's perspective → record the
user's acceptance or gaps → move that use case and monitor it. Record follow-up
gaps in live work records before claiming completion. Bubble remains available
for journeys not yet accepted; full off-ramp follows their disposition.

Evidence labels: `inferred` (inventory/package signals), `observed` (dated actual
workflow), `confirmed` (user validates goal/steps). Implementation and acceptance
are separate: tests can prove new behavior, not the original workflow or user
acceptance. Do not mark transfer accepted on the strength of tests alone.

## First review cohort — candidate journeys

| ID | Actor and user goal | Bubble evidence / confidence | Rebuild and remaining gaps | Owner / transfer |
|---|---|---|---|---|
| CSOC-UC-001 | Returning/new member signs in and reaches their work | Login/signup strings and historical identity evidence; original transfer journey inferred | OIDC + registration entry implemented; current cohort onboarding and live Case B need review | WP-0008-T01/T03; pending |
| CSOC-UC-002 | Writer finds an existing space and opens a page to continue work | `vw_spaces`, `vw_pages`, space/page fields; inferred; one historical import rehearsal | Space/page navigation and markdown implemented; nominated real content, visuals, missing hierarchy and recognizability need review | T03/T05; pending |
| CSOC-UC-003 | Writer creates and maintains a space/page with Title, Abstractor, Visual and body | Space/page create/edit symbols and captured card UI; inferred | Metadata/body forms implemented; Visual serving, safe content versioning and restart persistence outstanding | T01/T04/T05; pending |
| CSOC-UC-004 | Writer makes an independent copy, or moves a page to another workspace | Copy icons captured; exact Bubble transfer action unresolved | Copy/move implemented; arbitrary assets/links and actual original semantics need comparison | T04/T05; pending |
| CSOC-UC-005 | Reader sees shared work; outsider cannot access it; writer remains able to edit | Members/Guests/IsPrivate fields; original privacy rules inferred | First slice enforces viewer write denial and explicit membership/creator reads; membership management and exact Bubble privacy still outstanding | T04; pending |
| CSOC-UC-006 | Member can take their app-local information with them or leave with a clear content outcome | Platform-contract portability need; Bubble equivalent **unknown** | Export/delete not implemented; ownership/retention UX requires definition | T04; pending |
| CSOC-UC-007 | Member returns after a restart/incident and their work is still there | Continuity requirement, not a captured Bubble action | Persistent volume and paired DB/content restore evidence outstanding | T01/T02; pending |
| CSOC-UC-008 | Prepare the next ReichelAg founder call from the full previous protocol, write the new notes, copy them for manual email distribution | User-confirmed 2026-10-06; exact Bubble UI not freshly observed | Duplicate/edit implemented; clipboard action added; latest real protocol, mail-client paste and persistence review pending | T03/T05/T08/T09/T10; pending |

### Concrete scenario specification for the first review

First nomination is **ReichelAg weekly calls (UC-008)**: copy the full previous
protocol and edit it by hand. Use its nominated real latest entry. Broader
checks below remain additional cohort acceptance criteria.

Use a user-nominated existing space, a representative page with actual Visual and
body-linked assets, a second destination space, a writer, a reader and an
ungranted same-tenant member. Keep all private names/content/account mappings
outside git. Confirm the original paths and whether “page” means a page, chunk
or article before import. Until nominated, synthetic examples prove mechanics
only and cannot be labelled the real transfer cohort.

For UC-002/003: open the original page, note navigation and what is visible;
open its migrated equivalent, compare Title/Abstractor/Visual/body and essential
links; edit it, reopen it, and verify the change survives restart.
For UC-004: confirm original copy/move semantics; copy into the second space,
edit the copy and confirm the source is independent; move another page and
verify source removal, destination content and access.
For UC-005: reader can open the shared page, sees read-only access and cannot
change it by direct requests; outsider gets no content; destination write
permission is checked before copy/move. Exact sharing UI remains part of T04.
For UC-006: compare the app-local export and proposed leaving behavior before
confirming deletion; platform account handling is explicitly separate.
For UC-007: compare the pre-incident content and access with an isolated restore.

## Later candidates to discover, not silently discard

| Candidate | Evidence and unresolved user question |
|---|---|
| Research hierarchy / chunks / cards | `vw_pages`, `vw_chunks`, parent/chunk/card signals. Which actual workflows require these rather than page bodies? |
| Find work by search / featured spaces / feed | `vw_search`, `vw_feed`, featured labels. Which discovery tasks are actively used? |
| Invite people and manage membership | Invite/member/guest signals. Who shares with whom, with which permissions and confirmation? |
| Follow/favorite/interact | Likes/follow/social type signals. Which workflows are used rather than abandoned UI? |
| Work tracking / ventures / challenges | Tasklet/venture/challenge types. Capture a real complete journey before choosing its rebuild form. |
| Marketplace and payments | Marketing and checkout symbols. Confirm whether there is any active end-to-end use before prioritizing. |

Historical source: `docs/capability/existing-bubble-capability-map.md`,
`docs/bubble-inventory/2026-08-12-surface-inventory.md`, migration rehearsal and
accepted stage-1 cut. Unknowns remain open; this catalogue does not change that
cut or claim full parity.