The Five Conformance Rules of AGENT-POLICY v0.1
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
A document conforms to AGENT-POLICY v0.1 if and only if it passes five rules: (1) it is valid JSON and a top-level object; (2) all required fields are present with correct types and value domains; (3) no action appears in both the permitted and disallowed lists of the same rule; (4) no two rules share an identifier; and (5) site is an absolute URL and last_updated parses as a date. That is the whole gate — everything else the spec says is guidance.
What is conformance?
Conformance is the format's contract between writers and readers. A writer who passes the five rules is promised that any conforming reader — an agent, a validator, an operator's tooling — can parse the document without improvisation. A reader who trusts the five rules knows exactly which checks the document has survived. The list's brevity is deliberate engineering: five rules, each mechanically decidable, none requiring judgement about intent. Whether the terms in a conforming document are wise is a question the rules honourably refuse — that is what the policy itself, its reviewers, and its readers are for.
Rules 1 and 2: shape and domains
Rule 1 excludes the trivially broken: a file that is not JSON, or whose top level is a list or a string, is not a policy at all. Rule 2 does the heavy lifting of presence and domain. Top level: policy_version, site, owner, default_policy, agents, last_updated, signature. Per rule: identifier, allowed, permitted_actions, disallowed_actions, commercial_terms. Domains are closed sets — three values each for the default, the verdict, and the terms — which is what makes documents comparable across the whole web: conditional means the same thing in every file ever validated. The generator exists largely to make Rule 2 un-failable: answer questions, receive a document whose fields and domains are correct by construction, then let the validator prove it.
Rules 3 and 4: the relational rules
Rules 3 and 4 are different in kind — they govern relationships inside the document, and they are the two that real authors actually break. Rule 3 (no overlap) is the no-contradiction rule: a rule that permits and disallows the same action has not made a decision, so the format declines to call it one. Rule 4 (no duplicates) is the no-ambiguity rule: with no first-match-wins defined, two rules for one identifier leave the named agent without a principled reading, so the document fails instead of the agent guessing. Both rules share a philosophy worth noticing: when the owner's intent is unclear, the format blames the document, never the reader. The mistakes guide is essentially a field guide to Rules 3 and 4 in the wild.
Rule 5 and the deliberate exclusions
Rule 5 is the formats rule: site must be an absolute https:// (or http://) URL, and last_updated must parse as a date. It looks minor until you imagine the alternative — a web of policies whose subjects and freshness cannot be machine-read. Just as instructive is what the five rules exclude. Authenticity: not checked — signature is a null placeholder. Legal sufficiency: not checked. Actual agent compliance: not checked, and not checkable by any document examination. The spec names these exclusions itself, in the same section that states the rules. A conformance regime that knows its own boundary is one whose "pass" you can repeat precisely — which is all validation ever claims.
It is worth noticing what the five rules' brevity buys the ecosystem as a whole. Because the gate is small and mechanical, conformance claims are interoperable: a "valid" from AgentGate's validator, a partner's internal checker, or a host's sweep all mean the same five things, and documents can be compared across the entire web without calibrating whose checker was used. Every additional judgement-laden rule a format might have added — fairness of terms, adequacy of fences, quality of prose — would have forked that meaning into opinions. The rules' discipline is therefore not minimalism for its own sake. It is the deliberate construction of a word — conformant — that strangers can trust identically, which is the only kind of trust a declaration format can manufacture.
Worked example: five rules meet a real editorial workflow
Fictional example. The Harrowgate Gazette, a fictional regional newspaper, keeps its policy in the same repository as its site, edited by whoever updates the paywall. Over one year its validation history touched four of the five rules: a trailing comma broke Rule 1 in March; a well-meant rename of commercial_terms broke Rule 2 in May; the paywall editor added download to a permitted list that already disallowed it in August (Rule 3); and a January cleanup found two rules for the same research agent, written by different editors in different months (Rule 4). Rule 5 never failed — the paper's one perfect rule. The Gazette's fix was procedural, not technical: no policy edit merges without a validator run, which is the five rules' natural habitat — a gate in a workflow, not a puzzle to solve once.
The five-rule self-check
- Rule 1 — parse it. Confirm the file is valid JSON and a single top-level object.
- Rule 2 — count the fields. Seven top-level, five per rule, every value inside its three-value domain where one applies.
- Rule 3 — diff the lists. In every rule, intersect permitted and disallowed: the answer must be empty.
- Rule 4 — list the identifiers. Each identifier appears exactly once across the whole file.
- Rule 5 — read the header literally.
sitean absolute URL,last_updateda real date,signaturepresent.
Keep reading
Agent Policy Mistakes That Make a Policy Invalid · Validator Warnings vs Errors in AGENT-POLICY v0.1 · Agent Access Policy Examples · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
Are the five rules the whole spec?
They are the whole conformance gate. The spec also defines the document structure, the identifier registry, the action vocabulary, and versioning behaviour — but a document is conformant if and only if it passes the five rules. Everything else informs how you write and read; these five decide validity.
Why is there no rule about signature authenticity?
Because v0.1 defines no signature profile to check against — the field is a required null placeholder for a future version. A conformance rule demanding verification of an undefined scheme would be unimplementable, so authenticity sits explicitly outside the v0.1 gate, named in the spec's exclusions.
Which rule do authors break most?
Rules 3 and 4 — the relational ones. Overlapping actions creep in when lists are edited months apart, and duplicate identifiers arrive via merges and copy-paste. Rules 1, 2, and 5 fail early and obviously; 3 and 4 fail silently, inside valid-looking JSON, which is why validators exist.
Does a warning mean a rule was broken?
No. Warnings cover content outside the known lists — unknown identifiers, unknown action names — which no conformance rule prohibits. A document with warnings and no errors is conformant. Errors are rule violations; warnings are the format noting novelty. The two are reported separately for exactly this reason.
Who wrote the five rules?
They are section 4 of the AGENT-POLICY v0.1 draft specification, authored by Ingenious AI (AgentGate) and revised 2026-10-18. The same section states what conformance deliberately excludes: authenticity, legal sufficiency, and whether agents actually comply.
Generate a policy — free · Validate a policy · What an agent access policy is