Safe decides whether your agent may spend. Recourse decides on what terms.

1 · A Safe with the Safe7579 adapter — install the module

Safe becomes an ERC-7579 account through the Safe7579 adapter (a Safe module plus fallback handler by Rhinestone). Once the Safe is 7579-enabled, installing Recourse is one installModule from the Safe — executed like any other Safe transaction, by the owners' threshold — with the policy as init data:

// from the Safe (owners sign; Safe{Wallet} tx builder, the Safe SDK, or permissionless.js)
bytes memory policy = abi.encode(
  agentKey,          // the key your agent holds
  [USDC],            // tokens it may commit
  1_000e6,           // per transaction
  5_000e6, 1 days,   // per period
  1 hours            // never an inspection window shorter than this
);
safe.installModule(2 /* executor */, RECOURSE_MODULE, policy);

// the agent, later — the Safe is the payer of record
uint256 id = module.commit(safe, seller, USDC, 500e6, keccak256(terms), "ipfs://terms", deadline, 2 hours);
module.dispute(safe, id, ref);   // or release / proposeSettlement

Revoke the agent with uninstallModule; tighten the caps with setPolicy. The module only ever calls executeFromExecutor on the Safe and only ever targets the token approval and the escrow. It is not Safe-exclusive: the same module runs on Kernel, Nexus, and any other ERC-7579 account, which is why it is built to the standard rather than as a Safe-only module.

2 · A plain Safe with Zodiac Roles — point the agent at the escrow

No adapter, no module: the Safe itself is the payer. Give the agent a Zodiac Roles policy scoped to USDC.approve(escrow, ≤cap) and RecourseEscrow.open / release / dispute / proposeSettlement with parameter conditions (payee allow-list, amount ≤ cap, acceptWindow ≥ minimum). Roles enforces which calls; the escrow contract enforces what happens next. This works today on any Safe with Zodiac installed, and the commercial protection is identical: the funds sit in the transaction contract, and a dispute is decided by the venue and executed by the contract.

Roles and the Recourse module are complementary, not competing: Roles is the authority layer, Recourse is the terms-and-enforcement layer. Teams already on Roles can start with path 2 and move to the module when they adopt Safe7579.