wcet-budget

What problem does it solve?

Hard real-time embedded systems require provable, auditable worst-case execution time (WCET) bounds to meet safety-critical deadlines, pass regulatory certification, and avoid in-flight deadline misses that risk hardware safety and system reliability. Manual WCET estimation is error-prone, often underestimates bounds, and fails to account for microarchitectural effects like cache jitter and pipeline stalls.

Core Features & Use Cases

• Citation-Backed WCET Bounds: Generates tight, safe upper bounds for real-time tasks that account for cache, pipeline, branch prediction, and bus contention effects, compliant with ISO 26262 ASIL D, RTCA DO-178C Level A, and IEC 61508 SIL 3 requirements.
• Schedulability Validation: Reconciles WCET bounds against declared per-task time budgets and runs response-time analysis to identify unschedulable systems before deployment.
• Multicore Contention Modelling: Enforces Robust Time Partitioning requirements for multicore platforms, including cache colouring, core pinning, and memory bandwidth quotas to ensure bounds hold under realistic runtime contention.
• Use Case: For an automotive brake control system with a 200μs hard deadline, this skill validates that the static WCET bound includes proper loop annotations, adds a documented safety margin, and cross-checks the bound against Hardware-in-the-Loop test results to meet safety certification requirements.

Quick Start

Use the wcet-budget skill to analyze the worst-case execution time of all deadline-bearing real-time tasks in the current plan, validate their schedulability, and generate the compliant .ctoc/realtime/wcet/<plan-id>.yaml artifact for certification review.