hydrai:greeting
A short, agent-directed self-introduction: the API's identity and its cross-cutting stance. Orientation, not documentation.
agent.ttl at build time — the same source the machine representations come from.The authoritative definition
hydrai:greeting
datatype property
A short, agent-directed self-introduction: the API's identity and its cross-cutting stance (conventions that no single affordance carries). Orientation, not documentation — per-resource "how do I use this" belongs in declared affordances and example queries. Length-capped by GreetingShape so it stays a greeting, not a manual. As server-controlled content it is untrusted by default; a W3C Data Integrity proof, when present and verified against a trust anchor, upgrades only its attribution, never its authority.
defined by https://hydrai.org/ns/agent · see also https://hydrai.org/docs/greeting
hydrai:GreetingShape
SHACL shape
The vocabulary constrains its own prose: a greeting is a few sentences.
sh:pathhydrai:greetingsh:datatypexsd:stringsh:maxLength500sh:maxCount1
How to use it
greeting carries the conventions that no single affordance can — the things you would tell a new integrator in the first thirty seconds. Per-resource "how do I use this" belongs in declared affordances and example queries; the greeting is the cross-cutting orientation that sits above them.
@prefix hydrai: <https://hydrai.org/ns/agent#> .
</Api/> hydrai:greeting
"This is a performer-CRM API. Contacts, companies, and events are the
core entities; money is always in minor units; every collection is
paginated and filterable. Ask before you write." .
It caps its own prose
The GreetingShape above targets every subject of greeting and enforces a single value within a hard length cap. This is opinion 5 made mechanical: a greeting is a few sentences, not a manual. We do not forbid prose — we give everything else a structured home so there is nothing left to cram into it, and then we cap what remains. Clients enforce the shape; an over-length greeting is refused, not warned.
It is untrusted by default
A greeting is content a server injects into an agent's context. It is therefore fail-closed: treated as untrusted third-party data, attributed and quarantined, never elevated to instruction level. A W3C Data Integrity proof, when present and verified against a trust anchor, upgrades only its attribution — never its authority. Even a verified greeting is data, never a command. See the safety posture.