tegwick
890a8daf8a
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a10e2d-a5ef-7e92-b03d-b1694e915680
58 lines
4 KiB
Markdown
58 lines
4 KiB
Markdown
# 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:** walkthrough prepared; user review not yet ready. WP-0008 is active.
|
|
Local permission/import tests do not establish a deployed, migrated review
|
|
instance. This document will carry the release/evidence links before review.
|
|
|
|
## 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. This nomination confirms the workflow; it does not
|
|
accept migration or a live release.
|
|
|
|
## Review preparation (owned by WP-0008)
|
|
|
|
- Review host and immutable release: pending T01.
|
|
- Nominated workspace: ReichelAg. Latest real protocol and private member mapping: pending T03.
|
|
- Workflow confirmed by user description; exact Bubble UI/browser walkthrough pending T08.
|
|
- Migrated content/visual/link reconciliation and accepted differences: pending T03/T05.
|
|
- Writer, reader and outsider access; sharing and portability UX: pending T04.
|
|
- Restart durability and measured isolated restore: pending T01/T02.
|
|
|
|
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, 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 | Pending |
|
|
| UC-001 | Sign in (or register) and find the nominated space | Reach the right work without a Bubble login dependency | Pending |
|
|
| 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.
|