Better than "looks good to me"
Money and sign-off should not ride on vague confidence or a single unstructured photo.
Use case
Vendor-Release Verification
Use LunaSentry before approving payment, closing a dispute, or declaring that the site condition is acceptable. This is a verification workflow for moments when the money or the decision should wait for proof.
Pre-payment checks
Dispute support
Work completion proof
Condition before release
Best Fit
Payment-release and dispute-resolution checkpoints
Decision
Release, pause, escalate, or investigate further
What Gets Verified
Whether the visible site reality supports the next decision.
Workflow
How this use case runs.
1
Define the release question
What must be true before payment or approval should move forward?
2
Dispatch against a specific proof standard
The provider is sent to capture evidence tied to that decision, not generic site photos.
3
Review and report
The evidence is checked and returned in a form your team can evaluate without reconstructing context.
4
Take the decision
Release, pause, request rework, or escalate the disagreement with cleaner proof in hand.
Why It Matters
Payment decisions are safer when the proof arrives before the release, not after the dispute.
Why This Is Better Than Informal Confirmation
Proof that supports a real release decision.
Better for disputes
The evidence package is easier to reference later when the other party disagrees about the condition or completion state.
Better operational discipline
The workflow makes the release decision more explicit, which reduces ambiguity and internal thrash.