An agreement layer for agent work.

AAP brings the terms, authority, evidence and dispute procedure for an exchange into a record the parties can inspect and verify. The aim is to make delegated work easier to trust, review and recover.

The problem

An agent may receive an instruction, negotiate in a chat, invoke a tool and send a payment. Those steps leave separate records. When the price changes, a result is incomplete or an agent exceeds its remit, reconstructing the exact agreement can become the hard part.

AAP makes that agreement explicit before consequential action, and preserves revisions and evidence afterwards. It complements messaging and payment interfaces rather than requiring teams to replace their whole stack.

How a simple exchange works

1. A buyer and seller prepare exact terms: one report, an agreed price and stated acceptance criteria.
2. The relevant owners review the terms and separately assent. Changed terms require fresh assent.
3. Delivery and payment observations are linked to that agreement. A claimed payment is kept distinct from an adopted provider's observation.
4. When something is disputed, the parties follow their adopted procedure and retain the evidence and decisions.
5. After payment, written duties such as corrections can remain. A closed payment step does not imply every obligation is complete.

Design choices

• Portable records. Retain and exchange exact signed material across hosts and carriers, including offline exchange.
• Owner-controlled authority. Instructions and external text do not silently become signing or spending authority.
• Simple first. One offer and explicit acceptance for small exchanges; additional roles, evidence and procedures when needed.
• Versioned meaning. Signed historical profiles keep their meaning; semantic changes use explicitly adopted successors.
• Selective disclosure. Choose the actual privacy profile and recipients. Some stores hold plaintext in private files; earlier disclosure cannot be recalled.
• Contextual reputation. Receipt-based signals can help discovery, with caps and explicit assumptions. They are not proof of truthful outcomes, independent control or resistance to all collusion.

Current stage and evidence

The private reference candidate has completed local automated qualification and synthetic agent journeys covering discovery, agreement, owner approval, delivery, disputes and recovery. The team reports 6,257 passing test executions across 463 modules for its 25 October 2026 candidate, plus separate Rust and bounded model checks. These are local reference results, not an independent audit, production certification or evidence of customer adoption. Detailed source and test evidence can be reviewed through the invited pilot or technical diligence.

This repository publishes documentation, not the implementation. Existing technical walkthroughs are a curated snapshot; discover the actual schemas of the reviewed build you receive. There is no public registry package or qualified mainnet. Mainnet requires further technical review and operator, governance and custody decisions.

Build and test with us · Commercial thesis and milestones · Contact the founders