Checkout and reference.
Accepts a rail product request plus payment, credit, invoice, purchase order, or waiver reference.
DiligenceOps product-to-proof loop
One DiligenceOps run now has a visible path from product request to proof package.
The Product-to-Proof Loop connects the commercial request to the operating record: checkout, payment or credit reference, controlled loop validation, runtime proof, workspace binding, proof review, return package, and attestation. Agents can see the path. Operators still hold the gate.
{
"rail": "diligenceops",
"sequence": [
"checkout_request",
"payment_or_credit_reference",
"controlled_operating_loop",
"runtime_proof_run",
"workspace_binding",
"proof_review",
"return_package_gate",
"attestation"
],
"operator_approval_required": true
}
Why this matters
The loop makes DiligenceOps feel like a product, not a page.
DiligenceOps already has a rail card and a runtime proof surface. This layer connects the dots so an agent or operator can understand the full operating route from buying or crediting the run to reviewing the evidence package before release.
Validation before runtime.
Checks required DiligenceOps inputs before allowing the proof run to advance.
Runtime package.
Creates the work order, result contract, usage receipt, callback record, ledger reference, and attestation markers.
Operator review.
Returns evidence inventory, missing-item report, risk summary, readiness score, and attestation only after review.
Test path
Two tests prove the loop has a spine.
A complete request should reach proof-ready operator review. A missing-evidence request should not fake success. It should open an exception and tell the operator what must be supplied or waived.
Complete request
POST a diligence scope, available evidence, and payment reference. Expected state: proof_ready_for_operator_review.
Missing evidence
POST a diligence scope without available evidence. Expected state: exception_open.
Operator decision
Add operator_decision when review is complete. Expected state: ready_to_return.
Operator review
DiligenceOps prepares the package. The operator releases it.
This is the Wever Labs pattern in miniature: agent-readable, machine-testable, and proof-backed.