Skip to content

PLAT-210: Shifter ACES Compatibility Profile

Statement

Before ACES-backed scenario definitions are enabled for provisioning, Shifter shall document the supported ACES compatibility profile: accepted ACES version or dialect, supported scenario capabilities, unsupported capabilities, Shifter-owned backend responsibilities, and user-facing diagnostics for constructs outside the supported profile. CyberScript compatibility shall be documented as transition/archive support while it remains live, not as a co-equal future DSL profile; additional non-ACES profiles require a later ADR or requirement.

Rationale

Multiple future-facing DSL profiles would make migration correctness ambiguous and could silently extend legacy semantics. The ACES migration needs one explicit Shifter ACES profile plus clear diagnostics and legacy compatibility notes, while current CyberScript behavior remains operational until parity and cutover are proven.

Traceability

  • DOCUMENTS → GITHUB_ISSUE Brad-Edwards/bigrae#676 (PLAT-007: Scenario Expressiveness Dependency)
  • DOCUMENTS → GITHUB_ISSUE Brad-Edwards/bigrae#620 (Scenario expressiveness dependency)
  • DOCUMENTS → GITHUB_ISSUE Brad-Edwards/bigrae#314 (Create CyberScript CLI tool and shared validation package)