Autonomous & robotic systems
Can the system recognize stale sensor data? Does it stay within approved limits? Can an operator interrupt it in time? Test these behaviors before expanding its permissions.
+ Defense & national security
We evaluate AI, autonomous systems and supporting infrastructure. Our tests examine performance, failure modes, human approval and the ability to intervene.
Test the system as people will use it.
A successful demonstration may depend on fresh data, a reliable connection or a reviewer who has time to act. We test those assumptions and document where the result changes.
Our main focus is AI, including autonomous systems, sensing, communications and the infrastructure they use. Each engagement has a defined system, purpose and test plan.
Can the system recognize stale sensor data? Does it stay within approved limits? Can an operator interrupt it in time? Test these behaviors before expanding its permissions.
Give the system incomplete or conflicting reports. Check whether its summary preserves the source, uncertainty and missing information that a reviewer needs.
Check whether an image, quotation or translated report can be traced to its source. Test whether summaries change the meaning or remove important context.
Rehearse a lost connection, delayed message or unavailable identity service. Check whether operators can still see the problem, limit activity and restore service.
Compare supplier results with the version and use you plan to approve. Inspect excluded tests, missing conditions and claims that the supplied evidence does not establish.
Identify who can approve an action, what information they receive and how quickly they can stop it. Measure the full response, from detecting a problem to stopping the affected action.
Include shift changes, missing reviewers and failed communications. Assign the response, check the fix and record what still needs testing.
Explore a network scenario ↗The Syntony Evidence Pack brings the test conditions, results, proposed response and next check into one record.
The intended use, system version, conditions tested and criteria for a useful result.
Test records another reviewer can inspect, with observed effects, limits and open questions.
Changes to consider, a named owner and the decision that needs to be made.
The tests to repeat after a fix or relevant change, and what must be checked before approval.
A connection can fail even when its components pass their individual tests. Explore examples across systems.
See how a stale sensor reading can affect a movement decision.
Explore robotics ↗SPACE & NETWORKSSee what happens when a remote command arrives late.
Explore space systems ↗RESEARCH & FORESIGHTRead our work on evaluation methods, connected risks and how institutions respond.
Explore the research ↗DISCUSS AN EVALUATION