I was the worker following a familiar weekly ritual across an infrastructure change. Bernd wanted to leave Bubble without leaving behind the work that made coulomb.social useful. The concrete ritual was small enough to understand: find the previous ReichelAg call protocol, duplicate the whole entry, edit it by hand, then copy its content into an external email draft.
I kept discovering that the useful unit of migration was that sequence, rather than a deployment or a collection of Markdown files. The workload could be healthy while the account could not log in. The account could reach its workspace while the workspace was empty. The content could be present while the copied protocol still lacked its title. Each observation changed what I needed to finish.
The session rewarded persistence, but the founder's ordinary reports were its best instruments. "Server Error," "No spaces yet," and "the file kept the default" each pointed to a specific boundary I had not yet made usable.
## Session identity
| Field | Value |
| --- | --- |
| Who | Codex agent session; exact model and session identifier not exposed |
| When | Substantive work and founder review recorded on 2026-10-06–07 |
| Where the work lived | coulomb-social product, owning Railiance deployment and identity/mail services |
| Closing scope | Record this session and sync its work; the wider Bubble exit remains active |
## Contribution
I brought SCOPE.md back toward the implemented product and carried the first use-case transfer through CSOC-WP-0008. The use-case catalogue and its mandatory fast/browser regression gate now protect the weekly-call journey with synthetic notes. The founder established the important detail early: duplicate the full previous protocol, including completed points, then edit the copy manually.
The personal account reached the new workload. Its missing OIDC client, password-reset mail wiring and post-login server error each needed their own correction and evidence. The reset message arrived and the founder confirmed workspace access. I kept the mail responsibility with its owners and the protocol-distribution step in the user's external email client.
A renewed, attended Bubble browser session let me capture the current ReichelAg cohort. The first live transfer brought 36 source articles plus the index and 36 assets into retained content storage, with one explicit owner grant. I rejected expired/public-only captures and prepared paired database/content recovery points. Isolated restores checked rows, sequences, files, rendering and access; temporary snapshot custody was never described as durable backup operations.
The clipboard review caught my largest mistaken assumption. I had exported the rendered body and tested the formatting I had designed. The old action actually copied the title, italic subtitle, original Markdown and a final legacy marker. Authenticated observation established the exact text. I corrected the export, compared it character for character privately, and protected that contract in rich, plain and manually selected fallback modes. Private business notes stayed out of the regression fixtures.
The next review found a naming problem: entering a new title while duplicating left the prefilled original-copy filename behind. I made the filename derive from the new title unless explicitly chosen, surfaced Rename page, and preserved source metadata during rename and subsequent editing. Collision checks, the fixed index filename, attachments, original independence and reader-denied writes are covered.
The final substantive release is Helm revision 13, source b13ba9c5815e. The mandatory application/browser gate passes 98 tests. A fresh paired recovery point preceded the image-only upgrade; read-only live verification found all 75 stored content files unchanged. The founder confirmed editing and clipboard copying. The naming correction is deployed for the next review.
## What I would want remembered
I want the clipboard mistake remembered plainly. A passing browser test can faithfully protect the wrong contract. Before replacing a user's copy action, inspect what it actually puts on the clipboard, including the title, subtitle, syntax and seemingly incidental footer. The user had supplied a concrete example; its exactness mattered.
I also want the difference between preservation and usefulness remembered. Keeping a protocol's bytes did not make its new name produce a useful file name, and placing editable fields in a form did not make renaming discoverable. The fix was small because the founder had kept the workflow concrete. I did not need to redesign the whole interface to make the next call easier.
Content came before broad UX work, at the founder's direction. CSOC-WP-0011 retains the later framework and navigation phase. That sequencing gave us real protocols and real review findings to design around.
Recovery evidence has a scope too. I proved isolated paired restores and kept release-time snapshots. I did not establish long-term custody, retention, recovery ownership or a production rollback policy by doing those things. Those remain live work.
## Durable legacy
- coulomb-social source b13ba9c5815e: title-derived duplicate filename, visible rename and preserved metadata; closing implementation receipt at 53b206f.
- coulomb-social d521ddc: full original clipboard export; source comparison and synthetic failure-path protection.
- CSOC-WP-0008, especially T09, T10 and T12: ongoing founder review, clipboard correction and naming correction. The workplan remains active.
- CSOC-WP-0009 and docs/usecases/registry.json: use-case catalogue and mandatory regression infrastructure.
- CSOC-WP-0010: working account-recovery mail and the remaining platform communication facilities.
- CSOC-WP-0011: UI framework architecture and latest-change navigation remain backlog.
- docs/release/reichelag-imported-2026-10-06.md, reichelag-clipboard-2026-10-07.md and reichelag-naming-2026-10-07.md: bounded live receipts without private protocol content.
- railiance-apps 4a80793 and RAPPS-WP-0015: final immutable release pin and revision 13 verification.
- scripts/snapshot-content-and-db.py and scripts/restore-paired-snapshot.py: paired recovery and isolated restore tooling, with failure/resumption checks.
## PQRST estimate
```text
PQRST-Estimate
P: 30%
Q: 25%
R: 15%
S: 20%
T: 10%
Sum: 100%
Confidence: medium
Signature: P30 Q25 R15 S20 T10
Dominant factors: Deploying the personal workspace, importing the first ReichelAg cohort and correcting clipboard/naming behavior drove implementation. Paired recovery rehearsals, exact original-clipboard comparison and the mandatory browser suite drove validation.
Notes: Authentication, password-reset mail and explicit private-space grants account for security work. Earlier phases are retained through session summaries; the closing routine is excluded.
```
## Visual prompt
> Use case: stylized-concept. Asset type: square Hall of Helix session portrait. House dialect: Constellation — precise pale-gold and gold-wire technical illustration on dark indigo. Scene: a small working desk at the near end of a narrow luminous bridge between two modest archive shelves. On the desk, an open notebook and its independent copied notebook show exactly matching abstract rows of strokes and bullet-like dots; a small clipboard preserves the full outline, including top and bottom rows. A quiet pale-gold outline of a worker checks the copy beside a human hand resting at the desk. A restrained helix of light links a small locked gate, a mail envelope, an archive box and the notebooks, representing a usable weekly workflow carried across infrastructure. Several dim unfinished threads extend toward the far shelf to acknowledge the larger migration still ahead. Composition: square, clear central notebooks, precise fine linework and generous dark negative space, warm patient light, tangible care rather than triumph. No logos, no readable text, no letters, no numerals, no watermarks. Opaque background.
The portrait was generated with the built-in image_gen tool from the prompt above.
## Portrait
## Handoff
Resume with the existing duplicated protocol: use Rename page, choose its title and filename, save, reopen, and complete the weekly-call/email-draft review. Record the founder's verdict in CSOC-WP-0008-T09 before treating the use case as accepted for transfer.
Continue durable recovery operations under T02 and remaining content/access reconciliation under the existing workplan. Describe and select the next real Bubble use case once this one is accepted. The broader social product, other spaces, navigation framework and apex retirement remain unfinished. This session's implemented corrections and deployment receipts are committed and synced; the migration itself is handed forward.
