Operators · Policy release candidates

Turn an accepted proposal into a reviewable candidate

A release candidate is not a live policy. Approved for catalog PR still requires a separately reviewed source-code change. Abraxas does not auto-publish policy logic.

Path

  1. Partner proposal — structured eligibility gate. Not a policy.
  2. Operator release candidate — server-owned specification and contract fixtures.
  3. Reviewed catalog PR — a separately reviewed source-code change publishes any pack or version.
  4. Sandbox validation — Studio, Starter Kit, and Partner Flow stay on the existing catalog until that PR merges.
  5. Reviewed Production adoption — Launchpad Policy Version Planner and Production review, never auto-promotion.

Lifecycle

Draft → Ready for review → Needs revision → Approved for catalog PR → Superseded. Approved for catalog PR is still not a live policy. Abraxas does not auto-publish policy logic and does not turn a proposal into a live compliance decision.

Where this lives

Policy proposals · Policy packs · Selective disclosure · Compatibility edges · Policy Fit