Milestones
List view
Design and implement OpenRAE developer, CI/CD, and release package/artifact management: pinned tools and dependencies, OCI test inputs, repositories and mirrors, caches, integrity and provenance, promotion, publication, and offline/air-gapped operation. The first issue is architecture/design; its outputs are ADRs, implementation issues, and an enforced GitHub dependency graph.
No due date•3/7 issues closedDesign and implement the RAES runtime control-plane across embedded, local, development, testing, air-gapped, multiprocess, and high-load operating contexts.
No due date•0/2 issues closedAssessment, adoption design, and implementation planning for a unified participant-control boundary spanning participant-relative observability, action semantics and equivalence, temporal behavior, output masking/redaction, external input/intervention, and inject delivery across runtimes and backends. The first issue is design-only; implementation proceeds through child issues created in this milestone.
No due date•28/41 issues closedConsolidated product wave: documentation, community docs, governance requirements (versioning/deprecation/migration, federation and interoperability, information governance, evidence integrity), and scenario-pack companion-repo follow-through. Contract-first: contracts/schemas publish with CI gates before implementation.
No due date•4/36 issues closedConsolidated product wave for backend contracts, conformance suites and fixtures, realization honesty, and downstream implementation evidence. RAES owns the portable contract and conformance authority; concrete backends such as LilRAE and APTL live and release outside RAES core.
No due date•13/21 issues closedConsolidated product wave: processing model and lifecycle, participant model (behavior, knowledge, coordination, tools/affordances, manifests), control-plane and shared-state contracts, observability runtime and provenance. Contract-first: contracts/schemas publish with CI gates before implementation.
No due date•8/42 issues closedConsolidated product wave: SDL semantics and schema authority, language surfaces, validation/admission of authored artifacts, semantic consistency, and SDL-level authoring tooling. Contract-first: contracts/schemas publish with CI gates before implementation.
No due date•39/41 issues closedReplicate TTCP CAGE Challenge 2 (Scenario2) by expressing it once as an ACES SDL document and driving it through a conformant CybORG simulation-backend adapter and the ACES reference backend. Establishes the aces-adapters monorepo (isolated per-sim adapter projects, shared sim-adapter base + conformance harness, per-adapter CI matrix) with full Ground Control onboarding and a strict SonarCloud profile mirroring aces-strict. Scope EXCLUDES realizing CAGE-2 on an emulation backend (deferred).
No due date•4/5 issues closedJoint design (#125) and per-requirement issues: DSL-122 (truth/adjudication refs), API-416 (contracts), EXP-726 (protocol), EXP-727 (verifier/judge/reward), EXP-729 (reference targets/hidden assets), EXP-730 (human review/adjudication).
No due date•0/15 issues closedJoint design (#124) and per-requirement issues for participant trajectories across SEM/DSL/ACT/API/EXP/AUT: SEM-221, DSL-119, ACT-621, API-415, EXP-723/724/725, AUT-814.
No due date•0/11 issues closedJoint design (#123) and per-requirement issues: API-417/418 (contracts), RUN-312 (runtime accounting), ASR-523 (conformance), EXP-728 (experiment episode records). Pairs with #122 (episode + budget model).
No due date•0/7 issues closedJoint design (#122) and per-requirement issues for participant episodes and budgets across SEM/DSL/ACT: SEM-222/223 (semantics), DSL-120/121 (surfaces), ACT-623/624 (model). Wave TBD.
No due date•2/7 issues closed