Skip to main content
Working Draft 0.9.1. Public at agentapplication/agentapplication.

​
First review

You do not need the whole paper.
  1. Read the overview through Four properties and the product table.
  2. Take one product you know well.
  3. Using those four properties, say whether it is an Agent Application, not one, or a boundary case.
  4. If the definition is too tight, too vague, or missing something you need in order to make that call, say what. A missing facet only counts if you need it to tell Agent Applications from chatbots, workflows, or task runners.
Post in discussion 1. Private notes: amol@agentapplication.io.

​
Other ways to help

​
After that

If a real product does not fit the four properties, send it. The same for a system the table wrongly includes, a term that already means something else in another field, or prior work that already names something the paper treats as open. The paper assigns responsibilities to frameworks, projects, releases, instances, platforms, and stores. Name a missing responsibility, one assigned to the wrong element, or a real system whose boundaries do not fit. Companion contracts belong in the repo only when two independent implementations need to exchange information across a stable boundary. See Companion documents.