Milestones
List view
- No due date•4/9 issues closed
Modular, swappable AI-gateway layer for model/token routing (builds on model-access ADR-059/060/061 and #2243). Scope, default OSS gateway selection, and implementation issues are defined by the design issue in this milestone.
No due date•1/2 issues closedA small released scenario cohort, independent participant/failure/cleanup evidence, current operator handbook, bounded core cleanup and a single evidence-based adoption decision. Review #2080.
No due date•0/8 issues closedDurable public lifecycle, monitoring and containment, fresh-project installation, restore, browser journeys and measured operating limits for the selected GCP release. Review #2080.
No due date•9/15 issues closedDedicated single-customer authority, scenario/version contract, effective range/credential/CI boundaries. First adoption target is GCP/GCE. No AWS parity, mandatory service mesh or new runtime commitment. Review #2080.
No due date•19/24 issues closedSecure, properly scoped participant communications across one or more CTF events: platform-admin and organizer actions, static/dynamic/timed RAES orchestration and participant inject delivery, authenticated in-range triggers, durable per-recipient fan-out, and safe rich in-app content. Existing CTF email/announcement/WebSocket plumbing is foundation; native GitHub issue dependencies enforce hard ordering. No tracking issue.
No due date•5/13 issues closedMove AWS canonical packaging from ECS/Terraform to Kubernetes (Helm/EKS), matching the GCP substrate. Decomposition of epic #1324 under program #1320 (ADR-011). Source map: docs/architecture/branch-routing-provider-coupling-inventory.md. Existing program/contract issues stay in their own milestones; this milestone holds the AWS-to-EKS execution issues only.
No due date•7/10 issues closedPalo Alto Networks-specific work (NGFW/VM-Series, Cortex XDR/XSIAM, PANW integration) concentrated out of the vendor-neutral OSS milestones.
No due date•8/39 issues closedOne provider-neutral range-substrate interface with AWS-Terraform and GCP-GDC as conformance-tested adapters behind the backend-bundle registry; canonical Kubernetes/Helm packaging (including EKS); CI backend matrix replaces branch-routed deploys.
No due date•54/59 issues closedShifter becomes a conformant ACES backend per ADR-024: publish the backend manifest and wire the ACES conformance suite into CI as gates before cutover implementation. CyberScript remains maintenance-only until parity gates pass.
No due date•39/42 issues closedInternal quality work: god-module splits, cyclomatic-complexity reduction, type-checking re-enablement, and structural cleanups with no user-facing behavior change.
No due date•66/68 issues closedNice-to-haves after launch: frontend/design-system redesign, cost dashboards, notification/email surfaces, and assorted UX polish.
No due date•82/118 issues closed