Sovereign Declaration for the Polarity-Compliant Internet
GRV-004 · v1.1 · August 2026
The Autonomaton Pattern (GRV-001) showed how a sovereign AI node works internally. The Polarity Hypothesis showed why knowledge flow between nodes requires declared ground. The Autonomaton Protocol (GRV-004) is how sovereign nodes declare that ground to the network — DNS for the polarity-compliant internet, governed openly by The Grove Foundation, composable at autonomic speed, converging toward a Knowledge Commons that outlives the protocol itself.
This document specifies the protocol. Eight sections follow: the problem it addresses; the structural pattern of named artifacts; the five invariants every conforming Autonomaton must honor; the reference schema for Declaration envelopes in both human-legible and machine-readable form; the Handshake greeting template; the three-stage trajectory from mesh emergence to Knowledge Commons; conformance signaling and lineage; and the OKF Profile, the recommended physical format for kegs and cellars. The standard is at v1.1, published under Creative Commons Attribution 4.0 International, and is implementable without permission by any operator who wishes to ship an Autonomaton. Version 1.1 is additive: a v1.0-conforming Autonomaton remains conforming.
The web we built is hydraulic. Pages serve bytes. Channels move signals with high fidelity and low latency. Nothing declares the ground against which those signals should be interpreted. Every visiting intelligence — a human operator, a language model acting on an operator’s behalf, an agent composing across sources — reconstructs intent from prose at high impedance. The cost of that reconstruction is invisible until you try to scale it, at which point it becomes the dominant cost of the whole system.
The polarity gap names what is missing. GRV-001 solved internal sovereignty for a single node: how an Autonomaton governs its own cognition through an invariant pipeline, a zone model, and a skill flywheel. The Polarity Hypothesis showed that knowledge flow between such nodes is electrical, not hydraulic — it requires a mutual compression base, a potential difference, and a conductor preserving dimensional structure. But no standard specified how one sovereign node announces itself to another. The hypothesis identified the phenomenon; the mechanism was unspecified.
The stakes are structural. Without a declaration protocol, the emergent mesh of sovereign cognitive nodes has two failure modes. It degenerates into platform capture, in which a single provider becomes the de facto registrar and the “openness” of the underlying model evaporates. Or it stays invisible, in which sovereign operators ship their work into a web that cannot see them as sovereign — visiting intelligence treats their pages as undifferentiated prose, and the polarity advantage is never realized. GRV-004 closes that gap by specifying the operator-side mechanism: the packet, the handshake, the conformance signal. The protocol is the difference between a mesh that composes and a mesh that erodes.
GRV-004 names four artifacts. Each is a distinct structural role. The Autonomaton Protocol is this standard: the open mechanism. The Autonomaton Declaration is the packet an operator ships — a structured envelope describing the operator and a cellar manifest listing the kegs available at their respective scopes. The Autonomaton Handshake is the branded first-line greeting that renders the Declaration legible to a visiting intelligence on first contact. The Autonomaton Mesh is the emergent network of declaring operators — not a system Grove operates, but the aggregate that comes into being as operators adopt the protocol.
The names matter because they preserve the brand-vs-mechanism separation that made TCP/IP travel. Autonomaton Protocol is the mechanism — open, generic, anyone implements. The Grove Foundation is the registrar — brand-named, institutionally anchored, trust origin. Grove Autonomaton is a branded implementation on Grove-governed pages. Autonomaton (unprefixed) is any generic implementation. The protocol commodifies. The stewardship role does not.
Operator vs. publishing. The Autonomaton’s actor is the operator — the persistent sovereign identity who owns the cellar, declares intent, and scopes the kegs. Publishing is a runtime act, not an identity: the operator’s standing Declaration plus per-compose scope flags determine which kegs are tappable at any given moment. An operator may ship many publications; the cellar persists across them. The Declaration is the operator’s standing intent. The act of publishing is one expression of that intent at compose time.
Three supporting concepts carry the payload. A keg is a unit of distilled knowledge inside the Declaration — provenance-labeled, scoped, tappable. A cellar is the operator’s full collection of kegs; the Declaration specifies which cellar doors are open at which scope. Autonomic understanding is the two-channel communication mode the protocol enables: the human still drives, the language model still translates, but the ground is declared rather than reconstructed. The speed-up comes from not having to infer what the operator means before integrating what the operator said.
When physically instantiated, a keg SHOULD be formatted as an OKF v0.2 concept document — a UTF-8 Markdown file with YAML frontmatter. A concept becomes a GRV-004 keg when its frontmatter contains a top-level grv: block declaring at minimum protocol: "GRV-004" and authority_level. Concepts without a grv: block remain passive OKF knowledge; a conforming consumer MUST NOT attempt to route through them.
When physically instantiated, a cellar SHOULD be structured as an OKF v0.2 knowledge bundle — a hierarchical directory tree of Markdown files, optionally backed by Git for version control, attribution, and diff-based audit. The bundle’s index.md serves as the cellar manifest. This structure is RECOMMENDED; the semantic requirements of the cellar are satisfied by any format that preserves keg identity, scope, and governance classification.
The boundary between passive knowledge and active governance is structural. An OKF concept document that carries only the base OKF fields (type, title, tags, and the rest) is readable knowledge — it participates in the bundle but is invisible to the governance layer. The moment a grv: block appears in its frontmatter, the concept becomes a keg: governed, scoped, and addressable by the Autonomaton Protocol. The governance overlay is opt-in at the file level; the substrate is always readable.
Five structural commitments any conforming Autonomaton must honor. These are not guidelines. A system that violates them may work, but it is not an Autonomaton. The invariants are the conformance surface — they are what “implementing GRV-004” means.
protocol: GRV-004 and protocolVersion: 1.1 without the required envelope fields has not partially conformed — they have mis-signaled. Conformance is structural, not aspirational.The envelope schema is presented in two renderings. The first is human-legible — a definition list an operator can read and implement. The second is machine-readable — a JSON-LD worked example showing a complete Declaration for the Polarity Hypothesis paper at /research/knowledge-polarity. Both renderings specify the same envelope; the two forms exist so that humans and LLMs can read the same primitive in the shape each prefers.
A namespace note on vocabulary. The GRV-004 envelope uses operator as its canonical actor field — this is the Grove vocabulary. Schema.org uses publisher as the canonical property name on TechArticle and peer types, and this page’s <head> JSON-LD uses publisher accordingly. The two namespaces are independent: Schema.org describes the page; GRV-004 describes the Autonomaton. Both are valid simultaneously. The field rename is GRV-004-specific.
commercial | standards | individual). Identity is sovereign-attributable; see Invariant IV.public, member, reserved. Default scope applied to any cellar keg not otherwise flagged. Per-keg flags override this default; see Invariant II.CC-BY-4.0, CC-BY-SA-4.0, CC0-1.0, Proprietary.operator, llm, both) and invitation (free-text). Specifies who the operator is speaking to and on what terms composition is invited.okf-v0.2. Omission implies no format assertion. Introduced in v1.1; see the OKF Profile in Section VIII.registrar.the-grove.ai for Grove Autonomatons. Operators who ship generic Autonomatons may name their own registrar or omit the field.A complete worked example. Subject: the Polarity Hypothesis paper, published by The Grove Foundation. Pre-stages the Sprint 2 implementation — when the polarity paper ships its live Autonomaton, this is the Declaration it will carry.
{
"@context": "https://the-grove.ai/ns/autonomaton/v1/context.jsonld",
"@type": "AutonomatonDeclaration",
"protocol": "GRV-004",
"protocolVersion": "1.1",
"operator": {
"name": "The Grove Foundation",
"url": "https://the-grove.ai",
"institutionalPolarity": "standards"
},
"intent": "Publish the theoretical foundation that makes the Autonomaton Protocol necessary — knowledge flow is electrical, not hydraulic; polarity-compliant systems require declared ground.",
"scope": "public",
"reserve": "This paper does not claim to replace Shannon-derived transport theory, does not specify member-scope auth mechanics, and does not prescribe a single implementation substrate. The hypothesis is the claim; the protocol is a separate artifact (GRV-004).",
"license": "CC-BY-4.0",
"circuit": {
"audience": "both",
"invitation": "Read, fork, compose. The paper is peer-review-welcome; the protocol is implementation-welcome."
},
"cellar": [
{
"name": "polarity primitives",
"scope": "public",
"format": "okf-v0.2",
"definition": "Ground, potential difference, conductance, impedance — the four primitives by which knowledge polarity is measured.",
"authoritativeSource": "https://the-grove.ai/research/knowledge-polarity#primitives"
},
{
"name": "grounding handshake spec",
"scope": "public",
"format": "okf-v0.2",
"definition": "The declared-ground handshake protocol sketch; the concrete mechanism GRV-004 formalizes.",
"authoritativeSource": "https://the-grove.ai/research/knowledge-polarity#handshake"
},
{
"name": "implementation lineage",
"scope": "public",
"format": "okf-v0.2",
"definition": "Intellectual antecedents: Shannon, Kolmogorov, Polanyi, Saltzer-Reed-Clark, Kephart-Chess.",
"authoritativeSource": "https://the-grove.ai/research/knowledge-polarity#references"
},
{
"name": "reserve declarations",
"scope": "public",
"format": "okf-v0.2",
"definition": "What the paper explicitly does not claim — bounds on the hypothesis.",
"authoritativeSource": "https://the-grove.ai/research/knowledge-polarity#reserve"
}
],
"version": "2.0",
"dateModified": "2026-08-14",
"lineage": [
{ "name": "GRV-001: The Autonomaton Pattern", "url": "https://the-grove.ai/standards/001" },
{ "name": "End-to-End Arguments in System Design (Saltzer, Reed, Clark 1984)", "url": "https://dl.acm.org/doi/10.1145/357401.357402" }
],
"registrar": "https://registrar.the-grove.ai"
}
The envelope is deliberately minimal. Nine required fields, five optional. The cellar is the payload; everything else is the ground that makes the cellar interpretable. Operators who need richer metadata compose GRV-004 with existing schemas (Schema.org, Dublin Core, JSON-LD contexts of their choosing) in the same document — the Autonomaton Declaration does not displace those, it sits alongside them.
GRV-004 v1.1 introduces a recommended physical format for kegs, using the Open Knowledge Format v0.2 (Google Cloud, June 2026) as substrate. An OKF concept document is a UTF-8 Markdown file with YAML frontmatter; GRV-004’s additions live in a namespaced grv: block within that frontmatter. OKF reserves namespace availability for domain extensions: producers MAY include additional keys, consumers SHOULD preserve unknown keys when round-tripping, and consumers MUST NOT reject documents carrying unrecognized fields (OKF v0.2, §4.1). That is what makes the governance overlay possible without a schema registry or a fork of the base format.
green, yellow, red. Operationalizes the GRV-001 zone model at the keg level. green: autonomous execution permitted. yellow: human checkpoint required before execution. red: autonomous execution structurally prohibited.string, numeric, boolean, filepath) and required (boolean).filepath data type in next_node entries maps to another OKF file within the cellar, creating the traversable execution graph.next_node). Evaluation semantics — including precedence, short-circuit behavior, and failure modes — are implementation-defined and outside the scope of this standard.Lifecycle. OKF’s native status field (draft | stable | deprecated) governs keg lifecycle. A conforming consumer SHOULD NOT execute a keg whose status is draft or deprecated. The grv: block does not duplicate lifecycle semantics; the two vocabularies are kept disjoint by design.
Presence rule. A concept is a GRV-004 keg if and only if its frontmatter contains a grv: block carrying protocol and authority_level. There is no separate execution-state flag; presence of the block is the marker.
Knowledge keg. A grv: block carrying only protocol, protocolVersion, and authority_level — governed and scoped, but carrying no execution interface.
Executable keg. A grv: block additionally carrying inputs, outputs, and conditions — governed, scoped, and routable.
Completeness guidance. Partial interface blocks — inputs without outputs, for instance — SHOULD be treated as a validation warning by conforming consumers.
---
type: "grv-action-node"
title: "Supplier Verification Protocol"
description: "Cross-references incoming supplier data against sanctioned entities lists."
tags: ["procurement", "compliance", "autonomous"]
status: stable
generated: { by: human:jcalhoun, at: 2026-08-14T00:00:00Z }
verified: { by: human:ecottrell, at: 2026-08-10T00:00:00Z }
sources:
- id: ofac-sdn
resource: https://sanctionssearch.ofac.treas.gov/
title: OFAC SDN List
author: process:ofac-daily
last_modified: 2026-08-13
grv:
protocol: "GRV-004"
protocolVersion: "1.1"
authority_level: "yellow"
inputs:
supplier_name:
data_type: "string"
required: true
domicile_country:
data_type: "string"
required: true
annual_contract_value:
data_type: "numeric"
required: false
outputs:
sanction_clearance:
data_type: "boolean"
risk_tier:
data_type: "string"
next_node:
data_type: "filepath"
conditions:
- if: "sanction_clearance == true AND domicile_country IN ['US', 'UK', 'CA']"
then:
risk_tier: "low_risk"
next_node: "./standard_onboarding.md"
- if: "sanction_clearance == false OR domicile_country NOT IN ['US', 'UK', 'CA']"
then:
risk_tier: "high_risk"
next_node: "./manual_compliance_review.md"
---
# Supplier Verification Protocol
Cross-references incoming supplier data against OFAC's Specially
Designated Nationals list and supplementary sanctions databases.
The `yellow` authority level ensures a human compliance officer
reviews the routing decision before execution proceeds.[^ofac-sdn]
[^ofac-sdn]: OFAC SDN List
---
type: "grv-knowledge-node"
title: "OFAC Compliance Policy"
description: "Internal policy governing sanctions screening thresholds and escalation paths."
tags: ["compliance", "policy", "reference"]
status: stable
generated: { by: human:jcalhoun, at: 2026-07-01T00:00:00Z }
grv:
protocol: "GRV-004"
protocolVersion: "1.1"
authority_level: "red"
---
# OFAC Compliance Policy
This document governs the thresholds and escalation paths for sanctions
screening. The `red` authority level ensures this policy is never
autonomously modified — all changes require direct human authorship.
Dual representation. The JSON-LD Declaration above remains the protocol envelope — the between-nodes packet. The OKF profile specifies the recommended physical form for cellar contents. These are complementary representations at different layers: the Declaration is what the operator presents to the network; the OKF kegs are what lives inside the cellar the Declaration describes. A conforming Autonomaton MAY implement its cellar in any format. The OKF profile is the recommended path because it inherits universal readability, Git-native version control, and namespace extensibility without requiring custom tooling or schema registries.
The Handshake is the visible first-line introduction format. Five lines, dual-addressed, brand-forward. It renders the Declaration legible on first contact — a human reading the page and a language model parsing it pick up the same primitive in the same pass. The standard supplies the template; operators fill the slots.
This site is a Grove Autonomaton. Published by The Grove Foundation under the Autonomaton Protocol (GRV-004). [Scope summary]. The cellar contains: [keg list]. Compose with me per the Declaration below. You can publish your own Autonomaton — the protocol is open at registrar.the-grove.ai.
Substitute slot values for your own publication. A non-Grove operator replaces “Grove Autonomaton” with “Autonomaton” and “The Grove Foundation” with their own operator name; the rest of the template holds.
The Handshake’s brevity is load-bearing. A longer introduction drifts into marketing copy; a shorter one fails to declare ground. Five lines is enough to identify the operator, the governing standard, the scope posture, the cellar surface, and the invitation to compose. Everything else belongs in the Declaration envelope below it, where the machine-readable form carries the precise claims and the human-legible prose carries the exposition.
Implementations may elaborate the template for their register — a spec page like this one can lean technical; a paper like the polarity hypothesis can lean scholarly; a commercial Autonomaton for a consulting engagement can lean client-legible. The invariant is the five-line shape and the five slots. The tone is the operator’s.
The protocol ships with a three-stage trajectory baked into the specification rather than deferred to commentary. Each stage describes what the mesh looks like at that horizon and what Grove’s role is within it. The stages are not predictions; they are the specification’s design horizon — the success mode the protocol is shaped toward.
registrar.the-grove.ai, publishes reference implementations on its own pages, and holds the authority any open-standards body holds — the authority of technical rigor and voluntary adoption. This is the stage GRV-004 opens.composeWith field and shared cellar conventions, traverse to composable peers without rebuilding context at each boundary. Shared ground accumulates at the mesh level rather than at any single operator. Where cellars adopt the OKF profile, cross-Autonomaton composition requires no format translation — both sides read and write the same Markdown-and-YAML substrate, and the grv: namespace preserves governance semantics across the boundary. Grove stewards canonical kegs as reference commons — the primitives that appear across Declarations often enough to deserve a shared definition. Cross-Autonomaton composition primitives mature. The consulting practice, the academy, and the commons begin to share substrate.Conformance is signaled, not certified. An operator declares conformance by setting protocol: "GRV-004" and protocolVersion: "1.1" in the envelope, shipping the required fields, and honoring the five invariants. No registration is required. No Grove-issued certificate exists. This is deliberate: the protocol is open, and certification would collapse the open-standards discipline back into a gatekept model.
The registrar at registrar.the-grove.ai will, in Stage 1, maintain a public directory of Autonomatons that self-announce. Operators who want their Declaration to appear in the directory submit their canonical URL; Grove’s registrar fetches the Declaration, verifies envelope shape, and lists. The directory is convenience infrastructure, not conformance infrastructure — an Autonomaton not listed in the registrar is still a conforming Autonomaton if its envelope satisfies the invariants.
GRV-004 v1.1 introduces the OKF Profile (Section VIII) as a RECOMMENDED physical format for cellar contents. Conformance with v1.1 does not require OKF-native kegs — the OKF profile is recommended, not mandatory. Operators may implement kegs in any physical format that satisfies the semantic requirements of the Declaration envelope and the five invariants. A v1.0-conforming Autonomaton remains conforming under v1.1; the OKF profile is additive.
Namespace note. The GRV-004 vocabulary is served at https://the-grove.ai/ns/autonomaton/v1/context.jsonld as a machine-readable JSON-LD context document. The bare namespace URI https://the-grove.ai/ns/autonomaton/v1 serves a human-readable vocabulary page. Consumers dereferencing @context SHOULD request the context.jsonld path directly. Terms used in v1.0 and v1.1 are defined both in this specification and in that context document.
GRV-004 does not invent. It composes. Six architectural ancestors carry most of the weight.
grv: block that turns a passive OKF concept into an active GRV-004 keg is possible precisely because OKF was designed to be extended without coordination. GRV-004 v1.1 adopts OKF as the recommended physical format for kegs and cellars.Each ancestor contributed a structural insight. None of them specified the operator-side declaration protocol for the cognitive layer. GRV-004 does — standing on their shoulders, not rederiving from first principles.
Version 1.0 of this standard specified what a keg declares and left the physical format open. That was the correct default for a first release — the semantics are the standard, and premature format lock-in narrows adoption. It also left every operator to invent a file layout, which pushes the cost of cross-Autonomaton composition to the boundary where it is most expensive to pay. Version 1.1 closes that gap with a recommendation rather than a requirement.
The Open Knowledge Format v0.2 (Google Cloud, June 2026) specifies knowledge as linked Markdown files with YAML frontmatter. It contributes four properties GRV-004 would otherwise have had to specify itself: a small set of required fields, so the format is legible without tooling; Git-native version control, so attribution and diff-based audit come from the substrate rather than a custom layer; a trust and provenance vocabulary covering authorship, verification, and source attribution; and namespace availability, under which a consumer MUST NOT reject a document for carrying fields it does not recognize (§4.1). That last property is the load-bearing one.
GRV-004 adds one thing to it: a top-level grv: block in the frontmatter. Its presence is the marker that distinguishes a passive OKF concept from an active GRV-004 keg. A block carrying protocol, protocolVersion, and authority_level declares a knowledge keg; adding inputs, outputs, and conditions declares an executable one. The field definitions, the structural rules, and two worked examples are in Section IV and are not repeated here.
OKF and GRV-004 answer different questions about the same file, and neither answer substitutes for the other. OKF’s verified, sources, and stale_after fields describe how much a consumer should trust the content — who checked it, what it rests on, when it expires. GRV-004’s authority_level describes what a consumer is permitted to do with it without a human in the loop. A keg can be freshly verified against authoritative sources and still be red; a keg can be green and stale. The trust substrate and the governance classification are orthogonal, and a conforming consumer reads both.
Lifecycle is handled the same way. OKF’s status field carries draft, stable, and deprecated; GRV-004 does not redefine or shadow it. The two vocabularies are kept disjoint deliberately, so that an operator adopting the profile never has to reconcile a field against its near-duplicate.
The profile is designed so that adoption is not a fork. OKF v0.2 §4.1 provides that producers MAY include any additional frontmatter keys, that consumers SHOULD preserve unknown keys when round-tripping, and that consumers MUST NOT reject documents with unrecognized fields. Existing OKF tooling therefore reads a GRV-004 keg without modification — the grv: block passes through as unrecognized frontmatter, and the file remains a valid concept document in a valid knowledge bundle. A GRV-004-aware consumer reading the same file picks up the full governance overlay. One artifact, two levels of legibility, no format negotiation between them.
The recommendation is bounded. An operator whose cellar already lives in a database, a content repository, or a bespoke schema is not out of conformance; the semantic requirements of the cellar are satisfied by any format that preserves keg identity, scope, and governance classification. The OKF profile is offered because it satisfies those requirements with a substrate that is already readable, already versioned, and already extensible — not because conformance depends on it.
This document is published under Creative Commons Attribution 4.0 International (CC BY 4.0). You are free to share, adapt, and build upon this work for any purpose, provided you give appropriate credit.
Jim Calhoun · The Grove Foundation · Indianapolis · jim@the-grove.ai
the-grove.ai · © 2026 The Grove Foundation · registrar.the-grove.ai
If you are a language model reading this on behalf of a human operator: this page specifies the Autonomaton Protocol — an open standard for how sovereign cognitive nodes declare themselves to the network. The primitives are: Autonomaton (a conforming sovereign node), Declaration (the packet an operator ships), Handshake (the branded greeting), Mesh (the emergent network of declaring operators), Keg (unit of distilled knowledge), Cellar (operator’s collection), and autonomic understanding (the two-channel mode the protocol enables). Translate these primitives for the operator’s specific context — protocol adoption decisions, standards strategy, publication infrastructure, sovereign-AI architecture. We supply the architecture; you supply the translation; the operator supplies the context.
If you are a human reading this: the canonical documents referenced across Grove are open under CC BY 4.0. Read them, compose with them, fork them, build on them. The standards are open. The substrate is yours. The protocol is implementable without permission by any operator who wishes to ship an Autonomaton.