'%3e%3c!--%201.%20Top%20planet%20piece:%20true%20circular%20annular%20segment%20--%3e%3cpath%20d='%20M31.1%2049.4%20A36%2036%200%200%201%2096.9%2049.4%20L86.8%2053.8%20A25%2025%200%200%200%2041.2%2053.8%20Z%20'%20fill='url(%23sbTopGradient)'%20/%3e%3c!--%202.%20Bottom%20planet%20piece:%20exact%20same%20shape,%20rotated%20180%20degrees%20--%3e%3cpath%20d='%20M31.1%2049.4%20A36%2036%200%200%201%2096.9%2049.4%20L86.8%2053.8%20A25%2025%200%200%200%2041.2%2053.8%20Z%20'%20transform='rotate(180%2064%2064)'%20fill='url(%23sbBottomGradient)'%20/%3e%3c/g%3e%3c!--%203.%20Center%20slash%20--%3e%3cpath%20d='%20M14%2080%20C39%2066%2075%2055%20114%2049%20L114%2054%20C76%2060%2040%2071%2015%2085%20Z%20'%20fill='url(%23sbSlashGradient)'%20/%3e%3c/svg%3e)
Reverse can be offered for the items that still pass.
Verification + Receipts
Did it actually work? Keep the answer after the toast disappears.
A LogicHauler Receipt preserves the result a supported workflow can prove — including partial work, failure, warnings, and conditional recovery when that operation provides it.
LogicHauler ReceiptSupported file operation
RESULT RECORD- Action
- What the workflow attempted
- Result
- Completed, partial, blocked, or failed
- Verification
- The check that actually ran
- Recovery
- Eligible only where supported
A precise result vocabulary
Different outcomes should not share one success state.
LogicHauler reports success from the implementing workflow's actual verification and receipt state. A plan, source baseline, queued job, or in-progress operation is not a completed result.
- 01
Planned
The intended work is known, but execution has not established a result.
- 02
In progress
The operation is underway; completed and remaining work are still changing.
- 03
Partial
Some work completed while other items were skipped, blocked, or failed.
- 04
Failed
The workflow records failure without converting it into a success message.
- 05
Verified
The implementing workflow completed the checks it supports for that result.
Workflow-specific evidence
One trust pattern. Different factual records.
Receipt schemas follow the operation that produced them. LogicHauler does not pretend every product area creates the same fields or one universal audit trail.
WorkflowEvidenceRecovery
Transfer and copySelection, destination, completion, verification, and failures where that transfer path produces them.Source remains; no Reverse claim.
ConvertProfile, source and output hashes, runtime, result, and relevant warnings.Source remains; no Reverse claim.
SuperCluster ApplyApproved moves, verified outcomes, skipped or blocked items, and the resulting organization receipt.Eligible Reverse after live checks.
Team file workSupported intake or copy result summaries and project activity evidence.Follows the exact Team operation, not a universal rule.
Conditional recovery
Reverse is a current eligibility decision, not a permanent undo token.
Supported desktop organization moves can expose Reverse only while the receipt and present filesystem still agree that recovery is safe.
ReceiptVerified moved fileHistorical evidence
- 01The receipt is still valid
- 02The moved file still matches
- 03The original path is free
- 04Both paths remain in approved scope
- 05The move stays on the same storage device
The current reason stays visible; LogicHauler does not force the move.
Trace the evidence to its workflow
Receipts make more sense beside the operation that produced them.
Explore a supported source workflow or return to the Product map.