DEV Community

aurumflux20
aurumflux20

Posted on

Required CI proof for agent PRs that touch billing

#ai #github #cicd #python

Required CI proof for agent PRs that touch billing

Agents say "tests passed" in chat. That is not an exit code.

If a PR touches Stripe, billing, or payouts, merge policy should treat unproven claims as open work — not green.

What Coherence does

Coherence records claim + evidence + next. In CI you run the real command and attach the exit code:

python -m coherence prove-cmd "pytest -q" --claim "unit tests"
python -m coherence check
python -m coherence report --out coherence-report.md
Enter fullscreen mode Exit fullscreen mode

The GitHub Action fails the PR when claims are open, empty, or tampered (hash-chain exit 3). The check must run as a step the agent does not control.

We dogfood this on https://github.com/aurumflux20/coherence (see docs/CI.md).

What this is not

  • Not a runtime admission fence for live payment keys
  • Not "banks require Coherence" — your branch protection does
  • Not a free LLM honesty essay — a required status check with deterministic exits

Offer

Money-Path CI Proof Gate — $2,500 prepaid
Async install on one pilot repo. 5 business days. Email only. No calls. Full refund if fail-then-pass demo doesn’t land.

Pay: https://buy.stripe.com/bJecN5elWfLy9lMgWfdIA0p
Repo: https://github.com/aurumflux20/coherence

Top comments (0)