In public sector
For government bodies and agencies that commission digital services. Suppliers build in your accounts, every phase is signed off by you, and the handover proves you own the code and the access ended.
If this sounds familiar
A supplier contract ends this year, and nobody is sure where the source and the credentials live.
- Control
- Phase gates signed off by your people, never the supplier. Supplier identities expire with the contract.
- How it works
- Proof
- A handover pack generated from the records, and residency reports where data must stay in the country.
- 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
“We will own the code and the evidence, whoever builds 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.