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

How to attach a four-question evidence report to pull requests with Open Work Proof

Use the GitHub Action to report what was claimed, what evidence exists, what limits applied, and the conclusion.

Who it is forA team that already runs a pull request delivery process and receives code changes from AI agents, and wants a standard verification report on each change.

The problemA pull request that says the agent finished and tests passed does not show the authorization, the evidence chain, or whether anyone has accepted the change.

The outcomeA report on each pull request with the claim checked, the evidence seen, the constraints on execution, and a VERIFIED, REFUTED, or UNKNOWN conclusion.

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. Open the integration file at integrations/github/action.yml in the Open Work Proof repo.
  2. Add the action to the pull request workflow of the target repository, following the file's inputs.
  3. Open a test pull request and read the four-question report it produces.
  4. Confirm that the report states whether the change only reached READY_FOR_ACCEPTANCE and does not claim the client accepted or paid.

Prompt for your agent

Review the GitHub Action definition at integrations/github/action.yml in https://github.com/dengyier/OpenWorkProof and add it to the pull request workflow of <TARGET_REPO>. Open a test pull request and report the conclusion in the four-question report. Verify that the report does not describe the change as accepted or paid.

Caveat. The README does not list the action's inputs or workflow settings, so the exact configuration must be read from integrations/github/action.yml.

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