#Finite ACP contract
Part of the Jig standard library. With a contracts parent directory,
copy the installed agreement and its license using
jig import-contract jig:finite-acp contracts/finite-acp.
Finite ACP lets ordinary Flow code conduct one native Agent task without receiving credentials or unrestricted process access. The Flow owns the conversation and checks its answer. Jig independently enforces the approved client, finite dispatch policy, lifetime and cleanup.
https://jig.md/contracts/finite-acp names an interface, not a permission or
discovery service. A package includes its
invocation descriptor and
descriptor-relative request
and response agreements.
Resolution matches that complete identity offline.
- Finite ACP specification: grant, framing, authority, failure and settlement.
- Choose an Agent: use a replaceable implementation.
- Retained native state: explicit retention and restoration under separate reviewed authority. This source candidate requires matching artifacts and installed-client qualification.
Channel receipt does not prove a prompt ran, and a completed prompt does not prove process cleanup. The resource returns actual termination evidence; the Agent Flow separately returns the checked application result. When retention was requested, only clean native exit, validated bounded collection, fencing, cleanup and atomic commit can produce a retained reference in the final output. A forced close reports unavailable retention. Restoration claims that reference once under current authorization and never silently starts a fresh conversation.