In healthcare
For health providers and health-tech companies. Changes touching patient data are raised automatically, routed to the right approvers, frozen around critical dates and proven afterwards.
If this sounds familiar
A release last month touched patient records without a clinical safety review.
- Control
- Path rules raise the risk of anything touching personal or health data, and automation can never lower it.
- How it works
Allow partial refunds from the merchant dashboard
Asked by A. Patel, with Claude Code · change CHG-2291 · 7d3a9c…41fe
- The change, in plain words
- Merchants can refund part of a payment instead of all of it. Adds a
refund_amountcolumn and one endpoint.14 files · +412 −38 · 1 migration - Risk, and why
- Touches payments code
- Includes a database migration
- Written with an AI agent
- Evidence
- 1,284 tests passed
- No secrets, 0 critical CVEs
- Built in CI, signed
- Verified in staging for 26 h
- Blast radius
- Business service Card payments. Impact tolerance: no more than 2 hours of disruption.Canary 5% → 25% → 100%, halts if errors pass 0.5%
- Backout plan
- One-step rollback to v4.17.3. The migration has a tested down-migration; the 06:00 verified backup is the fallback.
2 approvers, never the requester
- R. Lindqvist (you)
- Waiting
- J. Osei, Risk
- Waiting
- Rollout
- Not started
Your signature will cover change 7d3a9c…41fe and nothing else.
What to tell your boss
“Every change to a patient-data system will have the right sign-off, and we can show it.”
Forward the one-page board briefSee what shipped without approval in your last 90 days.
Install the GitHub App and the scan arrives in minutes: every repo scored, every unreviewed merge and unapproved deploy named. Nothing is blocked until you choose.
Ship like a startup. Prove it like a bank.