---
title: "Editorial policy | Agent Ready Checklist"
description: "How Agent Ready Checklist sources facts, labels vendor claims, dates every reading and handles disagreement between the AgentReady spec, Cloudflare and Vercel."
canonical: https://agentreadychecklist.com/editorial-policy
site: "Agent Ready Checklist"
last_updated: 2026-11-05
section: "About"
---

# Editorial policy | Agent Ready Checklist

> How Agent Ready Checklist sources facts, labels vendor claims, dates every reading and handles disagreement between the AgentReady spec, Cloudflare and Vercel.

Source: https://agentreadychecklist.com/editorial-policy
Site: Agent Ready Checklist
Last reviewed: 2026-11-05
Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search)
Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free).

# Editorial policy

## Sourcing

Every fact on a page carries a source link and the date it was read. Prefer primary sources: the spec repository, the vendor's own documentation, the RFC, the live response of a host. A secondary source is labelled as one. A fact without a source does not ship; the page says less, or the page is not built.

## Vendor claims

What a company says about itself is a vendor claim and is labelled as one, Ora's included. Findings from Ora's research lab are written as "Ora's lab found", with the publication date, and never as "studies show". A finding from one sample is described as an association in that sample.

## Where the sources disagree

The spec, Cloudflare's scanner and the Vercel guide do not always agree, for example on whether a site needs a robots.txt or should negotiate markdown. Each position gets its own row with its own source. The methodology page lists the disagreements and how the rows keep them apart.

## Recipes

A recipe says which version it was read against and cites the documentation or the live response behind it. Where a platform cannot satisfy a requirement, the recipe says "not possible on this platform" and gives the workaround. A recipe is not tested on every plan or theme of a platform; the verify command is how a reader confirms the result on their own site.

## Writing

Pages are written to be run, not admired: short sentences, numbers with dates, no marketing register and no superlatives without a source. Each page opens with an In short block and ends with its sources and the date it was last reviewed. A build gate rejects pages that break the writing rules.

## Independence

This site does not rank or score platforms, scanners or vendors, and no row depends on the answer a vendor would like. If a row is wrong, the [corrections page](https://agentreadychecklist.com/corrections/) says how to report it and lists what has been changed.

Edition 2026-11-04.

## Sources

-   [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)read 2026-11-04

Last reviewed 2026-11-05. AgentReady v2.0, read 2026-11-04.