Where the guidelines came from, and how an agent can tell.
Anyone can publish a file that says it speaks for a brand. Provenance is the record that lets a reader check.
Integrity.
Every Registry publication is signed with Ed25519 over immutable bytes. Signature, key id, and hashes appear on read surfaces. This proves the file is unchanged. It says nothing about who the publisher is.
Official source.
The Registry issues a fresh DNS TXT challenge through an authenticated workflow. The brand places the exact record on its domain. The Registry verifies propagation and sets trust_level: verified, official_brand_source: true, verification_method: dns_txt.
Term and liveness.
Verification lasts no more than 365 days from initial verification. Renewal requires a fresh challenge. The Registry rechecks the retained proof at least every 30 days and publishes verification_last_checked_at. Rechecks do not extend the term. Resolver outages are inconclusive and retried. A confirmed conflict revokes immediately. Persistent absence is retried before downgrade.
Snapshot versus live.
The Registry also stamps the trust tuple into brand.md frontmatter at publish. That is a snapshot. If DNS status changes later, the live get_bcp response and headers are authoritative.
Certification is separate.
Registry Certified is a paid service designation for an exact active revision. It does not certify that every statement in the file is true, and it is not required for official-source status.
| Signal | Proves | Does not prove |
|---|---|---|
| Ed25519 signature | Bytes unchanged since publication | Who published, or that content is accurate |
| Current DNS attestation | Publisher controls the brand domain | Content accuracy |
| Certification mark | Paid service designation for this revision | That every statement is true |