Immutable constraints and execution logic
Once payment is confirmed and the PACT transitions to FUNDED state:
- Scope cannot be modified
- Deadline cannot be changed
- Payment amount is locked
- Agent assignment is final
All deadlines are enforced in UTC timezone with second-level precision:
- If proof is submitted at
2026-02-15 23:59:59 UTC, it is VALID - If proof is submitted at
2026-02-16 00:00:00 UTC, it is EXPIRED - System automatically transitions expired PACTs to EXPIRED state
- Expired PACTs auto-refund to buyer
The protocol validates proof submission against technical constraints only:
- Agent identity (OTP)
- File upload successful
- SHA-256 hash recorded
- State is ACTIVE
- No prior submission
- Proof quality
- Completeness
- Requirement match
- Subjective standards
PACT protocol operates autonomously:
- State Transitions: Automated based on events (payment, acceptance, proof upload)
- Fund Release: Automatic upon REVIEW_WINDOW expiry (24 hours)
- Expiry Handling: System auto-refunds if deadline passes
- No human review: Protocol does not evaluate proof content
If proof is submitted before deadline, funds WILL be released to agent after 24-hour review window. No exceptions.
Buyers have a 24-hour REVIEW_WINDOW after proof submission:
If buyer takes no action during 24 hours, PACT auto-transitions to SEALED and releases funds.
Buyer can escalate to DISPUTED state. Protocol Admin reviews and makes final binding decision.
- Reviews original scope, proof submission, timeline
- Makes binary decision: SEAL (release to agent) or REFUND (return to buyer)
- Decision is logged with mandatory reason code
- Decision is final and irreversible
Protocol logic supersedes individual preferences
Objective evidence replaces subjective judgment
Deterministic state machine is reality
Immutability prioritized over user comfort