Browse documentation
Architecture
Roles, trust boundaries, and the shape of an AQP exchange.
Participants
Authors a bounded query about one subject.
Applies local policy and authors the answer.
Validates, acknowledges, and routes responses.
The party authorized to use the answer.
A single system may perform multiple roles, but implementations must not assume the roles share identity, storage, or trust.
Exchange
The surrounding conversation or product interaction is deliberately outside the AQP core. A binding correlates it through the subject and query identifiers.
Trust boundaries
Prompts, subjects, response contracts, and delivery endpoints are untrusted input. Respondents must validate schemas, authorize destinations, enforce consent locally, and avoid transferring unrelated context. Collectors must authenticate submission authority, prevent replay, and treat answer content as untrusted.
Storage
AQP defines exchange objects, not a database, queue, or analytics API. Implementations may store and aggregate responses, but retention, search, workflow automation, memory, and training pipelines remain implementation concerns unless a future extension standardizes them.