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

How to build an acceptance bundle for an outside human signer with Open Work Proof

Generate an Acceptance Bundle from a ledger so an external Acceptor can sign without a private key entering the tool.

Credentials. The Acceptor's private key must stay with the external signer and must never be placed in the tool, the exporter, or any shared folder.

Who it is forA delivery lead who needs a client's authorized person to accept or reject agent work, with the acceptance kept separate from verification.

The problemVerification passing does not mean the client accepted the work, and the acceptor's private key must not be placed in the tooling used to generate evidence.

The outcomeAn Acceptance Bundle directory built from the ledger and surface evidence, ready for an external acceptor to sign and for a third party to verify.

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. Build the bundle with owp acceptance-bundle-build LEDGER SURFACE --evidence-root PATH --output DIRECTORY, replacing the placeholders with your ledger, surface, evidence path, and output folder. (inferred, check the README)
  2. Hand the draft to the external Acceptor, who signs it outside the tool.
  3. Commit the signed object through the append-only transaction the README describes as prepare, sign, commit.
  4. Verify the result with owp acceptance-bundle-verify DIRECTORY.
  5. Record ACCEPTED as exit code 0 or REJECTED as exit code 2, and treat REJECTED as a valid final state.

Prompt for your agent

Using https://github.com/dengyier/OpenWorkProof, run `owp acceptance-bundle-build <LEDGER> <SURFACE> --evidence-root <PATH> --output <DIRECTORY>` and then `owp acceptance-bundle-verify <DIRECTORY>`. Report the exit code and whether it is 0, 2, or 4. Verify that no private key or acceptance receipt was generated by the tool itself.

Caveat. The README says VERIFIED is not the same as ACCEPTED, and ACCEPTED is not the same as paid, settled, legal audit, or adoption.

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