brief: ratify managed-store-of-record (own the store, rent the fork)#130
Merged
Conversation
Ratifies the managed-tier workspace-store decision (draft -> active, published @ v0001): rustic-over-R2 stays the store of record; CF createBackup/restoreBackup (and ArtifactFS/mountBucket) may be used only as a transient fork mechanism derived from a rustic snapshot, never as the store. Criterion is dev ergonomics for personal-first use, not moat/defensibility: rustic already backs both planes, gives one handle space + permanence + dedup; the remote materialize-once bridge is a deferred optimization (don't pre-build). Refines managed-tier-do-gateway; mirrors workspace-cow-fork on the remote plane. Claude-Session: https://claude.ai/code/session_0164SS87ADPU2EBoGjyhVfej
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ratifies the managed-tier workspace-store decision as a brief governance doc (
draft→active, published @ v0001).Decision: rustic-over-R2 is the managed store of record; CF
createBackup/restoreBackup(and ArtifactFS /mountBucket) may be used only as a transient fork mechanism derived from a rustic snapshot — never the store, never the sole copy.Criterion: dev ergonomics for personal-first use, not moat/defensibility. Rustic already backs both planes (local libkrun + the managed R2 transfer), gives one handle space + permanence + dedup, and switching would be more work + handle-space fragmentation. The remote materialize-once fork bridge is a deferred optimization — the plain per-session rustic restore is fine until managed k-worker dispatch exists.
Grounded in verified CF docs (2026-07-03):
createBackup= mksquashfs → R2,restoreBackup= squashfs-lower + fuse-overlayfs-upper CoW; backups are TTL-3d + ephemeral. One residual noted in-doc (CF multi-sandboxrestoreBackup, architecturally implied, not documented).managed-tier-do-gateway; mirrorsworkspace-cow-forkon the remote plane..brief/);brief checkgreen locally.https://claude.ai/code/session_0164SS87ADPU2EBoGjyhVfej