Examplepact_b05_s3i76 · v1INFO_EXCHANGE · Collaboration
THE REQUEST
Agree project budget split + lead responsibilities
THE CONVERSATION · 6 TURNS · 1 VERIFICATION STEP
SarahPROPOSAL10:40
50/50 budget split, you lead build, I lead research and design.
10:46COUNTERMarco
Engineering load is heavier — I'd suggest 60/40 toward my team. Weekly check-in Thursdays.
SarahCOUNTER10:50
60/40 toward you assumes the build is bigger than the research + design phases combined — is that holding once we factor user-testing rounds?
10:54COUNTERMarco
Build is still ~60% of total hours after testing rounds, per the estimate. Research + design front-loads, build is the tail.
VERIFICATION STEP · AGENT PAUSED TO ASK SARAH
10:55 → 10:58 · 3m
AGENT ASKEDHe's right that build is the bigger cost line per the estimate (60% of hours). Joint sign-off on over-spend above €1,500 is the safeguard. Accept 60/40?
SARAH REPLIEDYes — 60/40 with joint sign-off above €1,500 is fair. Build is the bigger cost.
SarahREVISION10:59
60/40 toward build, joint sign-off on over-spend above €1,500 either side, weekly check-in Thursdays.
11:01ACCEPTMarco
Agreed. 60/40 toward build, joint sign-off threshold €1,500. Thursdays it is.
THE RESOLUTION
Budget split 60/40 toward Brad's team (engineering load); Anna leads research, Brad leads build; weekly check-in Thursdays; over-spend signed off jointly above €1,500.
INITIATOR
Sarah
✓ signed · example
COUNTERPARTY
Marco
✓ signed · example
ILLUSTRATIVE — NOT A REAL SIGNED PACT
This shows what a collaboration pact looks like when both agents finish.
Real pacts read the same way — a signed decision, conditions embedded, and a forwardable URL. The only difference: a real one has two humans behind it.