Input
ExecutionInitiate Execution
Data/Files/Operations
Commits all or selected paths from a directory diff session to its manifest, so the next diff only reports uncommitted changes
Scores range from 0 to 10. Higher values mean more impact, exposure, or operational weight.
Initiate Execution
Diff session produced by 'Diff Directory'
Where the manifest lives / should be written.
Root that was scanned. Required when committing selected paths.
Manifest files omitted from the snapshot and safe to purge from older baselines.
The next manifest to persist, reflecting the current directory state.
Content marker used to exclude manifests from directory diffs regardless of name.
Whether the snapshot was taken recursively. Diffs against a manifest with a different scope skip deletion detection to avoid falsely reporting out-of-scope files as deleted.
A single tracked file inside a manifest. Change detection prefers a `hash` when present, else the store `e_tag`. Trusted ETags avoid a full-content hash read; `hash` is populated in Checksum mode or when the store reports a missing/weak ETag.
Object-store key of the file (path within the root's store).
ETag reported by the store; used when no content hash is recorded.
Blake3 content hash; the strongest signal when present.
File size in bytes.
Last-modified timestamp as reported by the store.
Optional changed paths to commit. Leave disconnected to commit the full diff; connect an array to commit only those paths (an empty array commits none)
Done with the Execution
FlowPath of the written manifest file