The notice Field: Putting the Honest Scope in the File
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
The notice field is the one optional top-level field in an agent-policy.json file: a free-text string where the owner can say, inside the document itself, anything the structured fields cannot. Its most common content is the spec's own honest-scope line — that the policy is a declaration of the owner's terms, not an enforcement mechanism. AgentGate's own published policy carries that sentence as its notice.
What is the notice field?
It is the file's margin for human sentences. Every other field is a code, a list, or a date, because machines must act on them. The notice is where judgment lives: context about the policy, pointers to related documents, explanations of unusual decisions. The spec defines it with a single example — "e.g. restating that this is a declaration, not enforcement" — and no constraints on length or content, because a field meant for everything the schema cannot foresee cannot itself be schematised. Think of it as the cover note on a formal document: the document binds the reader's expectations; the note makes sure the reader understands what kind of document it is.
What belongs in a notice — and what does not
Good notice content clarifies without contradicting. The honest-scope restatement belongs: it frames every verdict in the file correctly for a first-time reader. Pointers belong: "Our data licensing terms are described at the owner contact" tells an operator where the structured file's story continues. Explanations of surprising decisions belong: a bank whose notice says its block reflects regulatory obligations, not hostility to agents, gives operators a reason instead of a wall. What does not belong is anything that fights the structured fields — a notice saying "actually, shopping agents are welcome" above a file that disallows shop creates two policies, and readers will believe the structured one, because that is the one machines can check and the one the validator certifies.
The notice as your honesty surface
AgentGate's own policy uses the field for the sentence the whole fleet runs on: this policy is a declaration of the site owner's terms, not an enforcement mechanism, and it does not force any agent to obey it. Putting that sentence inside the file — not just on the marketing pages around it — matters for a specific reason: the file travels. It gets fetched, cached, quoted in operator documentation, and read by people who will never visit the site that published it. The notice travels with it. Owners whose policies carry unusual features — a paid tier, a strict training refusal in data-use terms, a temporary restriction — use the same mechanism: the context rides along with the terms it explains.
Writing one well
Two or three sentences, in the plain register of the spec itself. Say what kind of document this is, say anything a reasonable reader would need to interpret the structured fields correctly, and stop. Resist turning the notice into a second policy, a legal disclaimer wall, or a marketing paragraph — all three bury the one job it has. If you have nothing that meets the bar, omit the field: it is optional, its absence is conforming, and an empty-hearted notice is worse than none. The samples demonstrate both choices across their three postures, and the generator leaves the field for you to fill deliberately rather than pre-filling boilerplate you did not mean.
Read your notice once a year with a specific question in mind: if this field were the only part of the file a busy operator read — and for a meaningful share of readers, skimming a fetched document between other tasks, it effectively is — what would they believe about your site's posture? If the answer matches the structured fields' story, the notice is doing its job. If it is boilerplate they would skip, or emphasis the fields contradict, rewrite it or remove it. The field's optionality is a standing invitation to keep it either excellent or absent; the mediocre middle — a paragraph of inherited scope language nobody chose — is the only genuinely wrong way to use the one field the format leaves entirely to your judgement.
Worked example: a medical publisher's notice does real work
Fictional example. Clearline Medical Publishing, a fictional publisher of patient-education articles across 14 condition guides, runs an allow default with generous reading rules — and a notice that earns its keep: "This policy declares terms for agent access to our published educational articles. It does not cover our clinician portal, which is not agent-accessible, and nothing in this file is medical advice or a substitute for it." Twice in the notice's first year, agent operators who had found the policy wrote in asking about portal access; both conversations opened with the operator quoting the notice back — the clarification had travelled with the file and pre-answered the exact confusion it was written to prevent.
The notice checklist
- Restate the scope. Say, in the file, that the policy declares terms and enforces nothing.
- Add only what clarifies. Pointers and explanations that help a reader interpret the structured fields.
- Never contradict the fields. If the notice and a rule disagree, readers believe the rule — fix the file instead.
- Keep it short. Two or three plain sentences; the notice is a cover note, not a second policy.
- Omit it if you have nothing to say. The field is optional, and absence beats boilerplate.
Keep reading
Where to Publish agent-policy.json: the /.well-known/ Path · How to Validate an agent-policy.json File · What Is an Agent Access Policy (v0.1)? · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
Is the notice field required?
No — it is the only optional top-level field in the format. The other seven top-level fields are all required. A policy without a notice fully conforms; a policy with one gains a place for context the structured fields cannot carry.
What do most policies put in the notice?
The honest-scope line: a restatement that the file is a declaration of the owner's terms, not an enforcement mechanism. AgentGate's own published policy uses exactly that sentence. Beyond it, owners add pointers to licensing contacts or explanations of unusual decisions.
Can the notice override a rule?
No, and it should never try. The structured fields are the policy — the parts agents parse and validators certify. A notice that contradicts them creates ambiguity the format refuses to resolve. If your intent changes, change the rule; use the notice to explain the change, not to make it.
How long can a notice be?
The spec sets no limit. Practice argues for brevity: the field is read by operators skimming a file and by agents summarising terms. Two or three sentences carry the scope line and one clarification comfortably; anything longer belongs on a page the notice can point to.
Does the validator check the notice?
Only its type — if present, it must be a string. Content is the owner's judgement, which is the point of a free-text field. That freedom is also the responsibility: the notice is the least checkable part of your file, so it should be the most carefully honest.
Generate a policy — free · Validate a policy · What an agent access policy is