> ## Documentation Index
> Fetch the complete documentation index at: https://agentapplication.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review the draft

> How to send holes, counterexamples, boundary cases, and prior art for Working Draft 0.7.

This is **Working Draft 0.7**, and the work is now being developed in public at
[agentapplication/agentapplication](https://github.com/agentapplication/agentapplication).
We welcome help with the paper, examples, definitions, and the open contracts
that may follow it.

## Join the work

* Use [GitHub Discussions](https://github.com/agentapplication/agentapplication/discussions)
  for open-ended proposals, architecture questions, boundary cases, and prior
  art.
* Use [GitHub Issues](https://github.com/agentapplication/agentapplication/issues)
  for concrete errors, missing citations, and documentation problems.
* Open a [pull request](https://github.com/agentapplication/agentapplication/pulls)
  when you have a specific edit, example, or correction. The
  [contribution guide](https://github.com/agentapplication/agentapplication/blob/main/CONTRIBUTING.md)
  explains how to prepare one.

## Review the definition

The paper draws a boundary around persistent agent instances, durable
workspaces, and durable work. If a real product crosses that boundary in a way
the definition misses, that is exactly the review we want.

A useful review might:

* Identify a claim that is wrong and give a case that disproves it.
* Point to prior work that already solves or names something the paper treats
  as open. Relevant fields include adaptive software, persistent actors,
  end-user programming, package systems, distributed systems, and autonomous
  agent research.
* Give a real system that the definition wrongly includes or excludes.
* Flag a term that already has a different meaning in another field.

If you would rather send feedback privately, email
[amol@agentapplication.io](mailto:amol@agentapplication.io?subject=Agent%20Applications%20paper%20review)
with the subject "Agent Applications paper review."

The companion contracts will be developed in the same repository. A contract
is ready to become a specification when independent implementations need a
stable boundary. See [Companion documents](/companion-documents) for the planned
sequence.