Latency budget
The total time allowed from sensor measurement to actuator command in a sense-plan-act loop. Each stage of the publish-subscribe pipeline (sensor capture, driver processing, middleware delivery, callback execution, planning, command delivery) consumes part of this budget. Exceeding the latency budget at speed produces unsafe robot behavior.
Defined in 2 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Foundations of Robotics and Physical AI.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The total time allowed from sensor measurement to actuator command in a sense-plan-act loop. Each stage of the publish-subscribe pipeline (sensor capture, driver processing, middleware delivery, callback execution, planning, command delivery) consumes part of this budget. Exceeding the latency budget at speed produces unsafe robot behavior.
The maximum acceptable time a content moderation check may add to a generation request before user experience is meaningfully degraded, allocated across prompt-side, output-side, and, for streaming products, incremental output-side filtering.
The maximum allowable time for a function or loop cycle to complete, determined by the physics of the control task. For a 1 kHz controller, the latency budget is 1 millisecond. Exceeding the budget even occasionally violates control stability assumptions.
The total time allocated to a single control loop iteration, broken into fractions for OS wakeup latency, control law computation, and sensor/actuator communication. Designing a latency budget before writing code ensures the chosen control rate is feasible on the target hardware and prevents discovering the infeasibility after assembly.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Content Moderation Frameworks · Generative AI Compliance, Certified China AI Regulatory Professional (CCARP)
- Why production robotics runs on C++ for speed and control · Programming for Robotics with C++, Foundations of Robotics and Physical AI
- Real-time considerations that shape C++ on robots · Programming for Robotics with C++, Foundations of Robotics and Physical AI
- Nodes, topics, and the publish and subscribe pattern · Your First Robot Software Stack with ROS 2, Foundations of Robotics and Physical AI
Where it shows up at work
A definition is where Latency budget starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Defines who reviews AI outputs, what they check, when they can override, and how to keep review from becoming a rubber stamp.
One lesson on this page teach it as a primary outcome.
Designs decision rights, committees, intake, approval tiers and escalation so routine uses move and consequential uses get reviewed.
One lesson on this page teach it as a primary outcome.
Tiers vendors by use and impact, requests evidence instead of promises, tests in the customer's context, and plans monitoring and exit.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- VP of AI Governance and Ethicsneeds it at depth
- Autonomous Systems Governance Lead, robotics and physical AI editionneeds it at depth
- Responsible AI Leadneeds working knowledge · 7 open postings this week
- AI Product Manager, responsible product editionneeds it at depth · 3 open postings this week
- Ethical AI Specialistneeds working knowledge · 5 open postings this week
- Chief Compliance Officer, AI compliance editionneeds it at depth
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: EU AI Act Article 14; ISO/IEC 42001 Annex A; NIST AI RMF GOVERN; ISO/IEC 42001 Clause 5.
One interview question about it
Design the human oversight for an AI system that approves refunds. What does the reviewer see, and what stops rubber-stamping?
Asked of candidates for human oversight design. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Privacy and data protection carries it as a claim to back up: Processor and vendor review is routine privacy work.
- Cybersecurity and IT carries it as a claim to back up: Supplier security assessment is routine.
- Nonprofit program and grants oversight carries it as a claim to back up: Reviewing grant and vendor agreements for data terms is vendor review.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.