AEROSIM-TS-75
Verify flight-runtime timing and resource budgets
The force-driven motion path satisfies explicit simulation-step, frame-time, CPU, and memory budgets under representative governed traces.
- Verified flow state
- Done
- Owner
- AeroSim Architecture and Delivery
- Feature
- AEROSIM-FT-1
- Component
- Web flight runtime — performance and resource budget harness
- Repository
- corp-v1-aerosim/corp-v1-aerosim
Delivery scope
Benchmark the completed FT-1 simulation path in Chromium, Firefox, and WebKit using basic-flight.json for 21,600 ticks after a 600-tick warm-up. Record p50/p95/p99 simulation-step duration, dropped-render-frame count, process CPU time, and JavaScript heap start/peak/end; compare all values with config/flight-runtime-budgets.json and emit FlightRuntimeBudgetReport.
Implementation contract
Implementation artifacts
- applications/web/test/performance/flight-runtime-budget.spec.ts
- applications/web/test/performance/collect-flight-runtime-metrics.ts
- config/flight-runtime-budgets.json
Inputs
- BenchmarkRun {buildSha,browser,fixtureDigest,warmupTicks:600,measuredTicks:21600,repetition:1..5} and FlightRuntimeBudgets {stepP95Ms,stepP99Ms,maxDroppedFrames,maxCpuSeconds,maxHeapGrowthBytes}.
Outputs
- FlightRuntimeBudgetReport {buildSha,browser,fixtureDigest,repetitions,stepMs:{p50,p95,p99},droppedFrames,cpuSeconds,heapBytes:{start,peak,end,growth},budgetViolations,passed}.
Failure boundaries
- Fail with PERF_SAMPLE_INCOMPLETE if a browser supplies fewer than five completed repetitions or any run uses a different build/fixture digest.
- Fail with PERF_BUDGET_EXCEEDED and list every breached metric when p95/p99 step time, dropped frames, CPU time, peak heap, or heap growth exceeds its configured limit.
- Fail with PERF_METRIC_UNAVAILABLE when required timing, CPU, or heap instrumentation is unavailable; do not silently omit the metric.
- Fail with PERF_TRACE_DIVERGED if the benchmark motion digest differs from the accepted EP3-FT1-03 trace digest.
Excluded scope
- Network/API performance, server capacity, mobile devices, battery consumption, renderer visual quality, and load from features outside FT-1 are not measured.
Verification steps
- Run applications/web/test/performance/flight-runtime-budget.spec.ts for all three browsers with five repetitions.
- Validate the report against config/flight-runtime-budgets.json and assert each required metric is present and finite.
- Lower each budget independently in a test fixture and disable one metrics provider; assert PERF_BUDGET_EXCEEDED and PERF_METRIC_UNAVAILABLE.
- Retain test-results/performance/flight-runtime-budget.json keyed to the exact build SHA and motion fixture digest.
Traceability
Dependencies
- AEROSIM-TS-74Canonical ID: TASK-0074
UI/UX applicability
non_visual
This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.
Acceptance evidence
Verified delivery: application PR #27 reviewed head f50bca31895109ab2c5edd7db055e669ce82aaed, exact-head validation task 1831 succeeded, merged as e8bfe781d3295d445cbc46b297874f066cac8301; Wave 4 integrated application head e8bfe781d3295d445cbc46b297874f066cac8301 passed publish task 1832 and validate task 1833. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.
Current evidence boundary
No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.