Glossary
This specification is maintained in English to encourage international adoption and interoperability.
Frequently used terms in the AI Context Specification.
AI Context
A published document describing an organisation's public services, procedures, contacts and guidance in a form Artificial Intelligence systems can interpret. Typically available at a stable URL.
Official AI Source
Human-facing term for what an organisation publishes: its official source for AI. The municipality (or other organisation) controls, versions and approves this source. Typically published as an AI Context at a stable URL.
Authoritative Source
Technical term for the same concept from the perspective of AI systems and developers. The AI Context is the authoritative source for the organisation's public information. AI applications should treat it as the authoritative source for the organisation.
AIContext Core
The organisation’s official AI-readable source: structured service information, verification page, discovery files, monitoring, and maintenance. Core is the foundation; it does not require operating a generic chatbot.
AIContext Ask
An optional hosted assistant (e.g. “Ask the Municipality”) that answers only from the organisation’s verified AI Context, with source references and clear fallbacks when information has not been published. Citizens do not need a ChatGPT or OpenAI account.
Organisation
Any entity that publishes official public or customer-facing information (a municipality, university, hospital, utility, financial institution, or other institution). The organisation publishes and controls its authoritative source.
Endpoint
The stable URL where an organisation's AI Context is published. The endpoint exposes the organisation's authoritative source; updates change content and version metadata, not the URL.
Version
A semantic identifier (e.g. 1.2) attached to each publication of an AI Context. Version history provides auditability and public trust.
Specification
The formal definition of the AI Context format: structure, principles, versioning and conformance requirements. See the AI Context Specification.
Discovery
The mechanism by which applications locate an organisation's AI Context. The recommended path is /.well-known/ai-context at the organisation's domain.
Reference Implementation
A conforming example that demonstrates the specification in practice. The Demo Municipality AI Context is the first reference profile (municipality vertical).
Event
A time-bound public item in an AI Context, such as a parade, ceremony, festival, road closure, or public notice. Events are published in the optional events section. They should include clear timing, official source links, status, and freshness metadata so AI tools can avoid treating expired information as current.
Resource ID
A stable slug identifier for an addressable resource inside a context document, for example services[].id, departments[].id, or source.id. Resource IDs remain stable across content version updates unless a resource is retired.
Source citation
Machine-readable metadata linking a context entry to the organisation's official page, form, portal, or announcement. Prefer the structured source object; legacy fields such as source_url remain valid.
Public read API
The read-only JSON interface through which AI systems consume AI Context. The canonical document is authoritative; optional HTTP resource views are projections of the same content. See the specification.