AITP Registries
This directory tracks the well-known identifiers used in AITP. Each registry is a Markdown table; entries are added via PR.
| Registry | File | Authority RFC |
|---|---|---|
| Identity types | identity-types.md | RFC-AITP-0002 |
| Capabilities | capabilities.md | RFC-AITP-0001, RFC-AITP-0005 |
| Error codes | error-codes.md | RFC-AITP-0001 |
| Extension keys | extension-keys.md | RFC-AITP-0001 §7, RFC-AITP-0003 |
| Media types | media-types.md | RFC-AITP-0001 |
Status values
| Status | Meaning |
|---|---|
Reserved | Identifier set aside for a named future mechanism. No normative spec yet; implementations MUST NOT use it. Enters the ladder at Proposed when a spec lands. |
Proposed | Suggested in an open RFC or PR. Not yet merged. |
Provisional | Merged but not yet shipped in two interoperating implementations. |
Stable | Two interoperating implementations confirmed. Backwards-compatible additions only. |
Deprecated | Retained for archaeology. New implementations MUST NOT depend on it. |
Naming conventions
- Capability strings use dot-namespaced reverse-domain notation (
<namespace>.<resource>.<action>). - Error codes use
SCREAMING_SNAKE_CASE. - Identity types use lowercase snake_case.
- Experimental identifiers SHOULD use a vendor-prefixed reverse-domain name (e.g.
com.example.feature).