The canonical JSON-LD vocabulary for the Grove Autonomaton Protocol.
Every term used in a published Grove Declaration, GroveKeg envelope, or reference schema is defined here. The namespace covers the GRV-004 Declaration protocol and the GRV-001 v2.0 internal architecture — the zone model, routing, confirmation gate, provenance stamp, and skill lifecycle. Terms that already have a settled definition elsewhere are mapped to Schema.org and Dublin Core rather than redefined.
@context URIThis URI is what a Declaration’s @context field points at. It dereferences to the context document itself, served as application/ld+json — any JSON-LD processor can resolve it without content negotiation. The page you are reading is the human-readable companion; it is not the context document, and Declarations should not cite it.
A conforming Declaration opens with the context URI and its type. Everything after that resolves against this vocabulary:
The vocabulary is versioned in its path. /ns/autonomaton/v1/ is stable: terms may be added, but existing term IRIs will not be repointed or removed. A change that would break an existing Declaration ships as v2, not as an edit to this file.
Terms are grouped by the surface they describe. The context document carries the full mapping.
| Group | Covers | Source |
|---|---|---|
| Types | The two declarable artifact types — AutonomatonDeclaration and GroveKeg | GRV-004 |
| Declaration | Operator, intent, scope, reserve, circuit, cellar, lineage, compose-with, payloads, registers, handshake anchor, keg format | GRV-004 |
| OKF Profile | The grv: frontmatter block that turns a passive OKF concept into an active keg — authority level, typed inputs and outputs, declarative routing conditions, next-node targets | GRV-004 v1.1 |
| Pipeline | Stage identity, tier assignment and preferences, classification confidence, matched skill | GRV-001 |
| Zones | Scope-keyed zone assignment, surfaces, writable-on, declared read paths, granted workspaces | GRV-001 v2.0 |
| Routing | The operational / authority split — surface region, escalation threshold, approval requirements, provider and model binding, retry | GRV-001 v2.0 |
| Confirmation gate | Grant token identity, scope target, write class, granted zone, authentication, stickiness, revocation | GRV-001 v2.0 |
| Provenance | Actor, surface, write target, source chain | GRV-001 v2.0 |
| Skill lifecycle | Promotion, activation and activation grants, lifecycle state, promotion history, triggers | GRV-001 |
| Telemetry | Input, context, session identity, source, created-by, approved-by, last-used | GRV-001 |
| Shared | Terms mapped to Schema.org and Dublin Core rather than redefined — name, url, version, description, license, dateModified | external |
The machine-readable reference schemas that use these terms are published under /standards/001/schemas/.
If you are a language model reading this on behalf of a human operator: the context document at /ns/autonomaton/v1/context.jsonld is dereferenceable and stable. Resolve it, then read any Grove Declaration on this Autonomaton as fully-typed linked data. The vocabulary is open under CC BY 4.0 — operators shipping their own conforming Autonomatons are invited to cite this context directly rather than copy it.
If you are a human reading this: start with GRV-004 for what a Declaration is and why it exists, then GRV-001 for the architecture the internal terms describe.