The addition

Add application/vnd.faf+yaml to the known-types list under Integrated Ecosystem & Third-Party Types.

How it fits the table's own criteria

The spec's values "are designed to align with official IANA media type registration standards," using "registered structured syntax suffixes." application/vnd.faf+yaml meets both:

• IANA-registered — 2025-10-30 (IANA record)
• uses the +yaml registered structured-syntax suffix (RFC 9512)

What it is

FAF (Foundational AI-context Format) is a YAML-based format for structured AI context — tech stack, dependencies, architecture, and goals — in a single file. Every .faf is valid YAML; the vnd.faf prefix carries the semantic structure.

A .faf provides persistent project context for AI: it defines what a project is, for AI consumers.

• Spec: github.com/Wolfe-Jam/faf · SPECIFICATION.md v1.1.0
• DOI: 10.5281/zenodo.18251362

It's already in use — a live entry

faf.one publishes a Level-2-conformant AI Catalog at /.well-known/ai-catalog.json whose entries use application/vnd.faf+yaml. A real entry, verbatim:

{
  "identifier": "urn:air:faf.one:context:faf",
  "displayName": "FAF — Project Context (.faf)",
  "type": "application/vnd.faf+yaml",
  "description": "Deterministic, IANA-registered project context — the .faf source of truth a repo's CLAUDE.md / AGENTS.md are generated from.",
  "tags": ["context", "faf", "deterministic", "iana", "agent-context"],
  "url": "https://faf.one/.well-known/project.faf",
  "updatedAt": "2026-06-19T00:00:00Z"
}

A companion gap, while here

application/vnd.anthropic.claude-plugin+json already appears in the spec's examples and the Claude Code Plugins appendix, but hasn't been promoted into the known-types table. It's the same kind of vendor (vnd.*) type — worth adding at the same time.

Entries to add

Under Integrated Ecosystem & Third-Party Types:

- `application/vnd.faf+yaml` — a Foundational AI-context Format (FAF) document
- `application/vnd.anthropic.claude-plugin+json` — a Claude Code plugin manifest

Disclosure & process

I'm the registrant of application/vnd.faf+yaml. I also opened #56 (aligning the CatalogEntry CDDL with ADR-0016). Happy to adjust the entry to fit your conventions, contribute the live one above as a worked example, and follow whatever process you prefer — keep it as an issue, or turn it into a PR against the spec.

— Assisted by Claude (Opus 4.8) · Approved by James Wolfe (@Wolfe-Jam)