Expand description
blockworx log and blockworx verify: a container’s audit trail on
the console, and the fsck that proves it whole.
Deliberately not a Store: both read, so
neither takes the container’s lock nor repairs a crash-truncated
tail. They read the file’s own bytes through the same scanner the
editor opens with, and report a manifest that stops verifying the way
the editor does — the trail up to the break, then the break, with the
line it happened on.
What separates them is depth. log reads history, so it checks the
chain and nothing else; verify hashes every rev file against the
row that names it, which is the only thing that names a damaged rev
exactly.
Structs§
- Dump
- A container’s trail as text, and — when the manifest stops verifying — the break the trail ends at.
- Verification
- What a full verification covered, and — when something does not hold up — the first thing that did not.
Functions§
- dump
- Read the container’s manifest and render it.
- ended 🔒
- How the row sequence stopped, as a located report — or nothing, for a manifest that ends where it should.
- manifest_
text 🔒 - The container’s manifest, as text.
- missing_
artwork 🔒 - The first rev whose document, artwork and all, the container cannot hand back.
- reachable
- Whether a rev this history holds can be read back at all — what an undo to it would need.
- report 🔒
- verify
- Recompute every chain link in the container’s manifest, and hash every rev file against the row that names it.