Milestones
List view
Design and implement the bounded control/runtime refactor established by the completed diagnosis: reusable mixed-control policies, modular provider composition, supervised execution and recovery, inject realization, mixed-backend coordination, IFC profile support, API trust boundaries, and truthful outcomes. Design issues settle requirements and contracts before dependent implementation. Preserve sound SDL semantics and the shared-runtime/backend responsibilities. Diagnosis: https://github.com/OpenRAE/rae/blob/077f7d04/docs/research/runtime-refactor/diagnosis.md
No due date•10/31 issues closedParticipant-relative information flow, action/observation relations, governed control, inject delivery, and backend realization. Open work: adversarial evaluation and publication (#1007, #1008), and the finite-bisimulation model, runtime mapping, counterexamples, checking, reproduction, and publication (#971–#976). Contract/runtime repairs are tracked in Runtime Refactor: https://github.com/OpenRAE/rae/milestone/71. Design, implementation, model checking, and runtime/backend realization establish distinct assurance results.
No due date•35/43 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/35 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•15/21 issues closedComplete participant authoring, runtime integration, and assurance against the current architecture. Trackers: #120 authoring; #121 profiles, context assets, and capabilities; #28 lifecycle; #8 control-plane completion. Identity remediation: #1338–#1342, verified by #220/#221. Other work covers timing, holdings and outcomes, derived context, replay, and conformance reporting. Each issue states the remaining work and acceptance evidence. GitHub dependencies define execution order. Reuse existing contracts; publish necessary contract changes before dependent implementation.
No due date•22/47 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/14 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/10 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