Specification

Spec changelog

What changed in the Prongs Intent Spec, newest first. Package releases have their own changelog; this one covers the format only.

Draft

2026-10-17

  • First draft: intents, profiles, registries, resolution, usage, the agent spec, the registry export and versioning.
  • Added terms and principles.
  • Added meta, for data the spec does not define, under reverse-DNS prefixed keys (§1.5). Keys under a prongs prefix are reserved.
  • Defined what each status means and what tooling does with it (§1.4). A deprecated intent should name its replacement.
  • Gave every validation issue a stable code (§3), and added the meta-key, meta-reserved and deprecated-no-instead issues.
  • Said that resolution reads only refs and binding, and fails on a cycle even when validation is off (§4).
  • Defined the shape of a checker's findings (§5.1).
  • Asked for deterministic agent spec output (§6).
  • Said what a reader does with an export from a spec version it does not know (§7). prongs export writes an export.
  • Added intents at run time (§8), conformance fixtures (§9), security (§10), and what counts as a breaking change, for the spec and for a registry (§11).
  • schema.json gained meta, and its $id now resolves.