Intent
A small, validated request that application code and agents can both send through the same pipeline.
An intent is a typed request for a view. It says what outcome you need, not how to construct HTML. It may name a registered view preference, but it cannot install or implement that view.
Pick a standard intent#
| Kind | Purpose |
|---|---|
browse | Collection, search, filter, sort, and pagination. |
detail | One identified entity or content item. |
create | Open a registered creation form. |
edit | Open a registered edit form for current host-supplied state. |
compare | Compare identified entities or values. |
analyze | Aggregate registered meanings at a valid grain and temporal policy. |
Send the envelope#
This browse request names a registered resource, one field filter, and a registered view preference:
intent.json
{
"version": "1",
"id": "browse-engineering",
"kind": "browse",
"resource": "people",
"fields": ["name", "team"],
"filter": { "op": "compare", "field": "team", "comparison": "eq", "value": "Engineering" },
"preferredView": "table"
}
Your code passes the same object to app.render({ intent }). An agent sends it through aeliqo_render. Both paths run identical validation.
Stay inside the envelope#
Intent may include resource, fields, filters, sort, page, identities, registered measures, period, and preferredView. It never includes principal, grants, credentials, executable code, SQL, HTML, endpoint URLs, or module paths.
Register a custom intent#
Register a namespaced version, runtime input schema, capability list, and pure synchronous compiler. The produced Task passes the same schema, catalog, Region, and authority validation as a standard intent.