Skip to content

docs: correct backup.md blob reference description #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wesm merged 1 commit into from
Sep 6, 2026
Merged

docs: correct backup.md blob reference description #277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/architecture/backup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ runtime records are not archive state. A restored copy is not trusted until
## Kit integration status

The internal `backupapp` adapter supplies Kit with Docbank's frozen logical
view: every authoritative `blobs` row, representation-neutral fidelity stats,
view: the backup-authorized blob closure, representation-neutral fidelity stats,
and mixed loose/packed content reads. A short operation-owner freeze opens and
pins one deferred SQLite read transaction; the freeze then ends, writers resume
into the WAL, and metadata, content membership, and fidelity statistics
Expand Down Expand Up @@ -165,10 +165,10 @@ terminal typed proof, with the SQLite scan and manifest-stat comparison
reported separately; the non-streaming endpoint keeps agent output to one JSON
document.

Backup reachability is intentionally broader than GC reachability: every
`blobs` row is captured, including a row that has become a GC candidate but has
not yet been reclaimed. This preserves the deletion pipeline's regret window
inside the snapshot.
Backup captures every blob still referenced by a retained content version,
rendition artifact, visual preview, or staged rendition source. A blob with no
remaining reference is a GC candidate, and the snapshot excludes it rather than
preserving it.

The current JSONL authority round-trips the node allocator high-water mark,
blobs, tree and trash state, content versions and current pointers, ingests,
Expand Down