INT-4812 ~~Pull request~~ → Intent Attempts closing in 14 min

Partial refunds on split-tender payments

A payment paid partly by card and partly by gift balance can be refunded in part, leg by leg, without ever returning more than was captured. Opened by Jonas Weber today at 08:21. Scope: refunds/splitTender.ts, refunds/Refund.ts, ledger/Posting.ts.

64 attempts 41 passing acceptance 13 partial 10 failing Spec v3

Compute budget

$38.20 of $60.00 used

Avg per attempt: $0.60
Closes: 10:04 today
Cap per attempt: $1.50
Active agents: 9 still running

The spec

v3 · edited by Jonas Weber 08:52

Editing the spec re-runs every attempt against the new version. Estimated cost $11.40, about 9 minutes. Attempts keep their forks.

Acceptance criteria, in plain language

Executable checks

Approach map

The system diffed 64 designs and found 4 approaches. One square is one attempt.

Passes 7 of 7 Partial Fails Selected for graft

Leaderboard

Select	#	Attempt	Agent	Approach	Accept	Mutation	p99 Δ	Symbols	Cost	Evidence

Why this is different

The unit of change is a goal. An intent states what must be true and how to check it. A pull request only holds one person's answer, and the goal lives in a description nobody can run.
Agents race, so attempts are cheap. Sixty-four forks try the same intent in parallel. GitHub assumes one branch per task and shows 64 near-identical pull requests as 64 separate threads.
Review moves from diffs to approaches. The signaller reads the spec, the evidence and a map of how the attempts differ. At 100,000 agents, reading every diff would take longer than writing the code did.
Pick or graft. The best implementation, the strongest tests and the safest migration often come from different attempts. A pull request can only be merged whole or rewritten by hand.
Editing the spec is the steering wheel. Change a criterion and every attempt re-runs. Today a change of mind means closing branches and starting over.