Source and view have different jobs.
The original stays exact. The display can be smaller, segmented, and replaceable.
From a recorded drive to a durable system
One drive. Three different responsibilities.
Preserve what happened.
Prepare what the app needs.
Be deliberate about what is shared.
Follow the responsibility
01 / ON THE PHONE
Exact samples commit locally.
Sync can catch up later.
Current Mobile: owner-only point backup.
Complete-file handoff awaits integration.
02 / MOBILE-OWNED BACKEND Locally qualified
Reserve a stable drive identity.
One exact, verified drive file.
Durable jobs. Leases. Safe retries.
Summary, thumbnail, detail route.
Fresh point + authorized audience.
Private recording can continue when visibility ends.
Trace the next complete-file path from local capture to a saved Library view.
The original stays exact. The display can be smaller, segmented, and replaceable.
Receipt, processing, publication, and deletion each need an explicit state.
Live consent never grants an audience the owner’s route history.
Add one responsibility at a time
The phone owns exact capture.
Transfer a complete, private file.
The current phone path backs up points.
A durable queue survives a request.
Processing is added in stage 02.
Give the app a prepared view.
12 schematic samples. Counts illustrate behavior; they are not production measurements.
Beside the recording · independent state
Current Mobile Event presence is approximate. Exact-current Events belong to the locally qualified LIVE-1 path, with hosted and Mobile acceptance still separate.
The work that remains after the request
Keep the previous successful view until its replacement is ready.
Remove private objects, verify absence, and retain a minimal cleanup receipt.
Reading the Library does not open raw Storage or put work on the queue.
0 jobs added by reads