A versioned YAML/JSON manifest mapping each interface — Agents, RELAY, SWML, REST API, Compatibility API, Browser SDK, Call Flow Builder, Dashboard AI Agent — to canonical name, aliases, use_when, avoid_when, protocols, languages, and quickstart/reference/schema/errors URLs. This is also where the "use this, not that" contraindications live (use SWML, not RELAY, when you only return declarative instructions; don't use the Compatibility API for SignalWire AI), so product routing becomes deterministic instead of inferred from prose. Audit §7 and §13.
This manifest is the single source of truth for product routing: the llms.txt decision map (#560) and the For AI choosing-an-interface page (#563) derive from it rather than encoding their own routing tables. Alias definitions come from the terminology registry (#561).
A versioned YAML/JSON manifest mapping each interface — Agents, RELAY, SWML, REST API, Compatibility API, Browser SDK, Call Flow Builder, Dashboard AI Agent — to canonical name, aliases, use_when, avoid_when, protocols, languages, and quickstart/reference/schema/errors URLs. This is also where the "use this, not that" contraindications live (use SWML, not RELAY, when you only return declarative instructions; don't use the Compatibility API for SignalWire AI), so product routing becomes deterministic instead of inferred from prose. Audit §7 and §13.
This manifest is the single source of truth for product routing: the llms.txt decision map (#560) and the For AI choosing-an-interface page (#563) derive from it rather than encoding their own routing tables. Alias definitions come from the terminology registry (#561).