Need
#861 establishes autonomous participant scheduling, but a conformant backend needs a portable way to bind due actions to real service adapters, execute multiple green participants, and expose operational control and evidence across a remote control boundary.
Required capability
- Backend manifest/admission for exact participant-action and target-service execution support.
- Bounded concurrent execution rather than serialized occurrence simulation only.
- RAES-controlled start, pause, resume, health, drain, reset, stale-generation rejection, and teardown.
- Typed health/readiness and action readback; operation receipts and runtime snapshots proving native action execution.
- Shared-time control/provenance usable through a backend control-plane interface, including pacing loss and deviations.
- Conformance tests that reject capability declaration without executable behavior or lifecycle evidence.
Consumer
Required by autarchy-ai/penumbra-scenarios#556. Product adapters and deployment mechanics remain backend-owned; no pack-specific scheduler or control semantics.
Architecture and governance requirements
Before implementation, reconcile this need against existing requirements, issues, ADRs, architecture, semantic owners, and already-provided capability; extend an incumbent concept rather than creating a parallel surface. Record relevant external and internal precedent and fully update the RAES lineage material. Add or amend ADRs when the design changes architecture or authority. Update normative specification, schemas/contracts, compiler, validator, runtime, backend manifests and admission, conformance guards, documentation, tests, release notes, and migration guidance wherever the chosen design applies. Establish and verify bidirectional requirement, issue, implementation, test, and release traceability. The issue is not complete until the released package exposes and guards the capability end to end.
Need
#861 establishes autonomous participant scheduling, but a conformant backend needs a portable way to bind due actions to real service adapters, execute multiple green participants, and expose operational control and evidence across a remote control boundary.
Required capability
Consumer
Required by autarchy-ai/penumbra-scenarios#556. Product adapters and deployment mechanics remain backend-owned; no pack-specific scheduler or control semantics.
Architecture and governance requirements
Before implementation, reconcile this need against existing requirements, issues, ADRs, architecture, semantic owners, and already-provided capability; extend an incumbent concept rather than creating a parallel surface. Record relevant external and internal precedent and fully update the RAES lineage material. Add or amend ADRs when the design changes architecture or authority. Update normative specification, schemas/contracts, compiler, validator, runtime, backend manifests and admission, conformance guards, documentation, tests, release notes, and migration guidance wherever the chosen design applies. Establish and verify bidirectional requirement, issue, implementation, test, and release traceability. The issue is not complete until the released package exposes and guards the capability end to end.