DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to package an agent delivery case for payer review with Open Work Proof

Initialize, inspect, verify, and export a Verified Agent Delivery case as a third-party review package.

Who it is forA service provider that delivers agent work to a client and needs to hand the payer a checkable record before any payment decision.

The problemThe payer needs to review the delivery facts without relying on the provider's own database or dashboard.

The outcomeAn exported review package with a deterministic digest and integrity manifest, plus a status derived from the real evidence.

What you need first

  • A Python environment with pip
  • A terminal with git for source installs
  • An existing Surface Bundle or Acceptance Bundle to verify, for the offline verification case

Steps

  1. Create the case folder with owp delivery-case init CASE_DIR.
  2. Re-derive the status from the evidence with owp delivery-case inspect CASE_DIR.
  3. Check the case with owp delivery-case verify CASE_DIR.
  4. Export the third-party review package with owp delivery-case export CASE_DIR --output-directory OUTPUT_DIR.
  5. Send OUTPUT_DIR to the payer, stating that READY_FOR_SETTLEMENT_REVIEW means the evidence is ready for review, not that payment has happened.

Prompt for your agent

Using https://github.com/dengyier/OpenWorkProof, run `owp delivery-case init <CASE_DIR>`, then `owp delivery-case inspect <CASE_DIR>` and `owp delivery-case verify <CASE_DIR>`, and export with `owp delivery-case export <CASE_DIR> --output-directory <OUTPUT_DIR>`. Report the derived status. Verify that the status comes from the Surface, Acceptance, and Settlement evidence and not from a pre-written conclusion file.

Caveat. The README says READY_FOR_SETTLEMENT_REVIEW and BOUND do not mean payment, client adoption, or legal recognition, and those facts remain not evidenced without outside proof.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page