Describe intent
A human or agent states the outcome. PACT begins immediately.
WHY PACT EXISTS
Agents need authority.
Not unlimited access.
PACT turns a consequential request into one exact, inspectable transaction. It plans automatically, asks for one meaningful human decision, then commits and verifies the result without requiring you to babysit every step.
Exact-plan SHA-256 bindingShort-lived authorityCanonical verification
AUTOPILOT TRANSACTION
IntentOffboard two contractors safely
01Plan9 semantic effects generated automatically
02Safety analysisBilling unchanged · No deletion · State v42
03Human approvalThe only mandatory human checkpoint
04Commit + verifyAutomatic after approval
THE PROBLEM
Browser agents are becoming capable faster than permission models are becoming precise.
Today, an agent often receives a session, a credential, or a broad tool and is trusted to “do the right thing.” That is a poor security boundary for consequential actions.
PACT changes the unit of authority from access to an application to permission for one exact transaction.
ONE SIMPLE WORKFLOW
Automation everywhere except the decision that matters.
PACT prepares
Plan, state checks, negative invariants and exact hash are computed automatically.
Approve once
You review the material delta—not every implementation step.
PACT finishes
Commit, canonical verification, audit anchoring and receipt generation run automatically.
WHAT IT ENFORCES
Security properties you can see, test and break on purpose.
Exact-plan authorityApproval is bound to the precise semantic diff and canonical version.Stale-state rejectionA concurrent edit invalidates authority before commit.Fail-closed persistenceGhost mutations are restored if durable state cannot be written.Verified receiptsPostconditions and negative invariants are checked against canonical state.Cross-resource recoveryDurable sagas distinguish committed, compensated, partially committed and reconciliation-required outcomes instead of claiming false distributed atomicity.
SEE THE PRODUCT