Expand description
Capability-rooted revalidation and trusted commit engine for VSH.
The committer is the only core component that can mutate a host workspace. It consumes a non-cloneable reservation, revalidates only recorded dependencies, persists an intent journal, moves replaced nodes into quarantine, installs content with create-new semantics, and verifies the final state before marking a commit.
Structs§
- Commit
Config - Hard bounds applied before durable commit work begins.
- Commit
Plan - Borrowed exact transaction artifact accepted by the trusted committer.
- Commit
Receipt - Compact proof that an exact transaction reached verified durable state.
- Committer
- Capability-rooted workspace snapshot, revalidation, commit, and recovery engine.
- NoFaults
- Production fault injector that never interrupts work.
- Recovery
Conflict - Fail-closed recovery result requiring operator resolution.
- Recovery
Report - Aggregate result of scanning durable commit journals.
- Snapshot
Limits - Bounds for eager host metadata traversal; file and link bytes remain lazy.
- Verification
Failure - Expected and observed state for a failed operation or final-state check.
Enums§
- Commit
Error - Trusted-commit, revalidation, or recovery failure.
- Commit
Plan Error - Invalid or unbounded immutable commit artifact.
- Fault
Point - Deterministic crash boundary exposed to fault-injection tests.
- Host
Error - Capability-scoped host filesystem observation failure.
- Journal
Error - Durable operation-journal or commit-marker validation failure.
- Plan
Decode Error - Durable commit-plan decoding failure.
- Revalidation
Conflict - One exact dependency mismatch detected before the first host mutation.
Traits§
- Fault
Injector - Test seam for simulating process loss at durable boundaries.