docs(brand-protocol): fold distributed-brand-json RFC into brand-json.mdx after ratification

[bokelley]

Tracking issue. Once RFC #3533 ratifies and impl #3764 lands, fold the RFC's content into the normative spec at `docs/brand-protocol/brand-json.mdx` and delete the proposal file.

What to fold (move from RFC into brand-json.mdx)

The RFC carries content the spec page doesn't have today:

• Motivation paragraph (operational pain story — 'Converse can't update its own logo without editing Nike's file'). Useful framing for spec readers.
• Conformance section (validator invariants — brand_id cross-array uniqueness, mutual-assertion as canonical trust primitive, managed_by non-trust, standalone trumps third-party claim, strictest-of compliance, 180-day TTL). Belongs in the normative spec.
• Strictest-of compliance resolution rule for governance fields. Belongs alongside the field-resolution table.
• Prior art note (ads.txt / sellers.json). Worth keeping for context, possibly in a sidebar.
• AAO API ergonomic note (server-side family merge). Already non-normative; can stay as-is in spec page.

What to drop

• Open questions — once decided in the RFC review, no longer questions. Drop.
• Migration plan section — once both shapes coexist in production, the spec page just states the rule. The full plan was a discussion artifact.
• Status table — RFC-only artifact. Drop.

What to delete

• `docs/brand-protocol/proposals/distributed-brand-json-rfc.mdx` — the file
• The directory `docs/brand-protocol/proposals/` if no other RFC files moved in

Acceptance

• RFC docs(brand-protocol): RFC for distributed brand.json #3533 ratified
• Impl feat(brand-protocol): schema cut for distributed brand.json RFC #3764 merged
• Folding complete (single PR, ~50-line delta to brand-json.mdx + file deletion)
• No 404s on links pointing to the old proposal path (search the repo first)

References

• docs(brand-protocol): RFC for distributed brand.json #3533 (RFC)
• feat(brand-protocol): schema cut for distributed brand.json RFC #3764 (impl)

[bokelley]

Triage

Classification: Tracking issue
Bucket(s): web / site / docs, brand
Status: deferred

My take: Well-formed and clearly scoped, but blocked on both listed prerequisites. The fold work (docs/brand-protocol/brand-json.mdx + proposal file deletion) touches the same surface as #3764 — flagged there as a fold candidate so it doesn't get orphaned when the schema PR ships.

Blocked-on: #3533 (RFC ratification) and #3764 (impl merge) — resurfaces on merge.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01KQb6mN4C46XYpsttP74FnX

---

Generated by Claude Code