Milestones

List view

• Phase 2.1 — Consolidate Phase 2 (0.2.1)

  Release on top of Phase 2 (0.2.0): consolidates Phase 2 work that slipped or waits on outside access, e.g. F5 Guardrails typing (#1177).

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• Upstream gaps

  Product asks to the Omni Gateway team. Filed in Phase 1, landing whenever the gateway ships them. Build guide 3.1.

  No due date

  •0/7 issues closed
  0% complete7 open0 closed

• Verification

  The §0.3 worklist: never invent an endpoint, header, class name or kwarg. Cross-phase, unversioned — each row blocks specific feature work.

  No due date

  •18/51 issues closed
  35% complete33 open18 closed

• Phase 5 — Complete rollout (1.0.0)

  TypeScript port, remaining adapters by demand, go-to-market, 1.0 stability guarantees. Build guide 3.5, gated on Python PMF.

  No due date

  •0/6 issues closed
  0% complete6 open0 closed

• Phase 4 — Enterprise readiness (0.4.0)

  Security review, performance budget, error-message pass, migration and deprecation policy, compliance evidence, log shipping, residency, workload identity, support model.

  No due date

  •0/14 issues closed
  0% complete14 open0 closed

• Phase 3 — Platform capabilities (0.3.0)

  Policy handshake, to-the-code push, structured output + eval hooks. Largely gated on the Upstream gaps milestone. Build guide 3.2-3.4.

  No due date

  •0/11 issues closed
  0% complete11 open0 closed

• Phase 2 — Differentiate, go beyond (0.2.0)

  Refusal handlers, classification registry, HITL, identity helpers, in-repo scanner + Action, kill-switch, MCP discovery, second adapter, A2A serve/expose/dev. Build guide 2.1-2.9.

  No due date

  •30/77 issues closed
  38% complete47 open30 closed