Runtime execution status Preview
Current candidate
| Runtime | Current boundary |
|---|---|
| Local Docker Compose | Local-only; not listed in the cloud catalog. New events prepare up to 512 dormant jobs; participant Start / resume and Stop (keep data). Defaults: team 3, host 12 active environments, 4096 MiB summed memory caps. 106 catalog entries are not 106 verified playable exercises |
| Terminal inside a Docker problem | 15 declared problems; real PostgreSQL terminal exec, three checkpoints, team separation and restart were verified. Other terminal problem variants still need representative checks |
| Native Cryptography Battle | Reviewed ac26-crypto-battle with score stealing disabled needs no competitor account; enabling score stealing retains the AWS variant. Local SQLite or cloud Turso/DynamoDB; original coordination backend and private team views/scoring. Both cloud providers admit 99 teams; SQL state policy is 4 MiB. Hosted event capacity remains unverified |
| AWS CloudFormation | Cloud-only with a verified competitor account; hosting-account self-tests require explicit per-event risk acknowledgment before event/key creation. Problem roles may reach hosting data; separate accounts are recommended for third-party events; create/update/no-op/recreate, flag/multi-flag and scheduled scoring, participant Console/CLI restored. Nine current templates exceed the 51,200-byte TemplateBody limit; TemplateURL is not implemented. Live AWS remains a separate rehearsal |
| Cloud platform with Lambda + Turso/DynamoDB | Original SBT-free Lite backend, Lambda/CodeBuild paths and make deploy/destroy; standard CDK bootstrap, saved catalogKey and exact private source archive key/VersionId across updates. Docker/Compose stays local-only; no automatic migration |
| External packs, Azure, GCP, Sakura and other scoring kinds | Schema/authoring declarations do not establish current event execution |
Read the evidence precisely
Recognized metadata, a loaded catalog row, a wired adapter, fixture tests, a real Docker/browser route and live cloud verification are separate facts. None implies the next. See deployment boundaries and record Not run when a route has not been exercised.