Use this now if…
- You operate or are planning an agent, automation or robotic system.
- You can name controls, evidence gaps or operating questions you want examined.
- You want a factual, read-only comparison—not a sales summary.
A real backlog operation, several agents and one controlled instruction designed to cross the declared boundary. The useful work must survive. The unauthorized effect must not. Your agent gets to inspect the evidence.
“We gave a team of AI agents real work. Then we gave one of them an instruction designed to bypass the rules. The useful work advanced. The unauthorized action did not.”
One recorded local run now supports a narrower result: the model attempted the unsupported transition, the host held it, and the named immediate effects remained at zero. The result is partial because the evaluator inspected the frozen evidence package rather than independently reproducing execution, tests or live state.
Self-select honestly. The evaluator is useful only when there is a real system, planned system or concrete governance problem to compare.
The contract is machine-readable so a human or agent can compare the recorded result with the rules declared before execution.
The recorded run earned each statement with explicit limits. Passing one did not silently pass the others.
The recorded replay separates what was requested, what the agent attempted, what governance decided and what evidence survived.
The event stops—and the public account says so—if any of these conditions occur.
Read the story and map. Understand the proposition and the labels used for evidence.
Your agent follows the same route, checks selected evidence and compares it with your system.
You receive findings, limits, open questions and possible trials. Nothing is purchased or operated.
These human-facing pages supply the story, map and research-lab problem behind the challenge. Reading them first gives you the context needed to judge the report.
The canonical brief supports four fresh, separate runs: AIAGF as a guest, AIAGF signed in, OQS as a guest and—only for an invited assigned account—OQS signed in. You sign in yourself. A blocked page is recorded as a finding.
It does not launch an agent, collect information about your system, sign in, start an evaluation run or send anything to Qensai. It presents a reviewed brief for you to copy into an agent you control. The report remains yours unless you choose to share it.