92 lines
5.2 KiB
Markdown
92 lines
5.2 KiB
Markdown
|
|
# First real ReichelAg content import — 2026-10-06
|
||
|
|
|
||
|
|
## Result and user milestone
|
||
|
|
|
||
|
|
ReichelAG is now on the live app at
|
||
|
|
https://app.coulomb.social/app/spaces/reichelag/. Existing tegwick can list the
|
||
|
|
space with exactly one owner grant; no other memberships were granted. This
|
||
|
|
addresses the reported empty workspace for the first nominated use case. Other
|
||
|
|
Bubble spaces remain later cohorts; this is not an apex/Bubble cutover receipt.
|
||
|
|
|
||
|
|
Imported36actual source articles, plus a space index reflecting source home
|
||
|
|
metadata/body:37markdown files,36visual assets. Source creation/modification
|
||
|
|
timestamps retained in article frontmatter. Latest dated protocol2026-10-02.
|
||
|
|
All29article IDs in the August rehearsal are present plus7new articles. The
|
||
|
|
current target was explicitly selected from a fresh attended Bubble session,
|
||
|
|
with no August seed mixed in. No private bodies, member mappings, cookies or
|
||
|
|
passwords were committed or emitted into Git/Hub/chat. Private capture remains
|
||
|
|
in protected temporary custody pending retained backup policy.
|
||
|
|
|
||
|
|
## Authorization and release
|
||
|
|
|
||
|
|
Founder instructed “yes go on” for current source capture and first ReichelAg
|
||
|
|
transfer, then confirmed completed attended login and visible protocols. This
|
||
|
|
continues the approved personal-app/brief-interruption work. Authority:
|
||
|
|
ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED. No issuer, Secret,
|
||
|
|
image, chart or persistent deployment setting was changed for this import.
|
||
|
|
App remains Helmrevision11, immutable image digest
|
||
|
|
sha256:bf975939e22b9b0a5d9ac05584ae6265ba201169df6dc48e506ec684b30a9c58.
|
||
|
|
|
||
|
|
Reviewed source package SHA256
|
||
|
|
a0ab5085e63a93fd351a1ffb85a092555cb340d72f9f5f3f510e43952388fbbc.
|
||
|
|
Private manifest maps one existing issuer/subject identity in tenant:platform
|
||
|
|
to owner of new reichelag. No email/password matching, account creation, broader
|
||
|
|
grants, existing-space replacement or production DB restore was performed.
|
||
|
|
|
||
|
|
## Preparation, recovery and execution
|
||
|
|
|
||
|
|
Real-content isolated rehearsal imported37pages/36assets. Every source file
|
||
|
|
hash matches; all37pages render; existing identity owner-only grant verified.
|
||
|
|
Final source index preserves its home description/body/visual rather than
|
||
|
|
a sample/migration description. Native server dry-run accepted the import pod;
|
||
|
|
package/paired-snapshot hashes match; replacement is refused.
|
||
|
|
|
||
|
|
Fresh app-quiesced paired pre-import snapshot started2026-10-06T20:21:30Z,
|
||
|
|
operation53.36seconds, app resumed afterward. Dump49843bytes SHA256
|
||
|
|
a5db7eb392db4315f2b5ded242ac6f6d664b1d348b204b915b145fded42bcaff;
|
||
|
|
content archive186bytes SHA256
|
||
|
|
8ef217f13654931bbd69828ba82181109aa57a9fa1a2c9ec56a2f340643139e1.
|
||
|
|
Artifacts remain private node/workstation/tmp; this is not durable backup custody.
|
||
|
|
|
||
|
|
Bounded scripts/apply-approved-content-import.py paused app writers, verified
|
||
|
|
current logical rows/sequences and content hashes still match the paired point,
|
||
|
|
then ran corpus preflight and import. Manifest not changed between reviewed
|
||
|
|
package and execution. One space only;37pages/36assets copied; all source hashes
|
||
|
|
and page renders checked inside the import pod. Pod removed, original app1
|
||
|
|
replica resumed. Operation52.97seconds. Public health200. Fresh new-pod check:
|
||
|
|
visible spaces1, reichelag visible,37pages,36assets, owner grants1, total grants1.
|
||
|
|
The normal app restart therefore also exercised real-content persistence.
|
||
|
|
|
||
|
|
A real-content paired snapshot of the isolated rehearsal was then restored into
|
||
|
|
a separate internal Docker PostgreSQL instance with no published ports. Result:
|
||
|
|
13tables/104rows, all logical row/sequence state matches;73files, all hashes
|
||
|
|
match; measured DB/content restore4.11seconds. Restored Django checks verify
|
||
|
|
all37rendered pages, owner list/read, and denied read for an ungranted same-tenant
|
||
|
|
actor. This restores the rehearsal composition, not a live production rollback.
|
||
|
|
Earlier synthetic recovery also verified independent full-protocol copy/edit,
|
||
|
|
asset/render fidelity and viewer write denial with validCSRF.
|
||
|
|
|
||
|
|
Full final make check:96passed including established Chromium journeys and
|
||
|
|
source-capture/restore guards; focused Ruff and Node syntax checks pass.
|
||
|
|
|
||
|
|
## User review and remaining work
|
||
|
|
|
||
|
|
User asked to refresh /app/, open ReichelAG and verify the October2protocol
|
||
|
|
contains expected notes. CSOC-WP-0008-T09 records visible-space/content and then
|
||
|
|
full-protocol duplicate/edit/reload/native clipboard/mail-client acceptance.
|
||
|
|
Import/render/hash success does not complete that productive use-case review.
|
||
|
|
|
||
|
|
T03 remains progress for complete inventory/identity reconciliation and explicit
|
||
|
|
later-cohort disposition (historical71spaces; only ReichelAg transferred). T02
|
||
|
|
remains progress for retained backup custody/retention, operational real-data
|
||
|
|
rollback and achieved production recovery policy. T05 retains visual delivery,
|
||
|
|
parent/outline/privacy fidelity gaps. Assets are stored; this basic app does not
|
||
|
|
yet deliver Visual covers as an accepted image-rendering product.
|
||
|
|
|
||
|
|
User prioritizes content migration before UI effort. CSOC-WP-0011 is the live
|
||
|
|
backlog for framework architecture before broad UX rebuild, decision
|
||
|
|
e67cfd2e-e55d-4b42-947a-b279b6287c55. Current page navigation is index-first/
|
||
|
|
alphabetical rather than Bubble latest-change ordering; source timestamps are
|
||
|
|
retained for that subsequent behavior/architecture work. No broad UI redesign
|
||
|
|
or automatic protocol-email sending was performed.
|