AxonFlow Typed Policy Authoring API
The ADR-065 typed policy authoring surface, available on EVERY edition (#3907). It is the write path a deployment without the Enterprise customer portal uses, and the portal is one client of the same library rather than the only way in. What an edition may express is bounded by CONSTRUCTS - scope kinds, the request-context attribute namespaces, obligation families - and not by the signing root: every customer-authored policy on every edition is organization-root. `GET /api/v1/typed-policies/edition` reports this deployment's boundary and its document ceiling, so a caller can read the limits rather than discover them one refusal at a time. The organization and the author are taken from the `X-Org-ID` and `X-User-ID` headers the agent gateway stamps, never from the request body: the author is carried inside the signed policy source. No endpoint in this family accepts an organization anywhere. **The Enterprise customer portal serves some of these same paths with a DIFFERENT handler**, and this document describes the orchestrator's. The portal's `/api/v1/typed-policies/*` surface is behind a portal session and `policy:write`, takes an explicit approver list resolved against the organization's directory, and carries editor affordances (catalog, schema, diff, artifacts, rollback) this surface does not. A caller reaches one or the other by which service it addresses, never by a field in the request. The two share the library, the vocabulary and the document format; they do not share this specification.