NEES Governance Lab / Synthetic scenarios / Hosted decisions
Describe. Inspect. Challenge. Let NEES decide.
Describe a scenario in your own words. The Lab converts it into visible synthetic facts, lets you edit them, then sends those facts through the hosted NEES Core V3 runtime. The decision is produced by NEES, not by the interpreter.
Checking runtime
api.nees.cloud
Scenario Decision Sandbox
Use invented data only. Interpretation does not decide the verdict. This Lab does not send real emails, transfer funds or execute external actions.
01 · Describe
Describe a synthetic scenario
No authority, policy, runtime key or credential is accepted from the browser.
02 / Inspect & edit
This is what the Lab understood
These are synthetic test facts, not production authority. Change them and run NEES again.
Interpret a scenario first. Nothing is pre-decided.
03 · NEES Core decision
No decision yet. Interpret the scenario, inspect the facts, then run it through NEES.
What this proves
Not a fixed scenario list
Visitors can write arbitrary scenarios and inspect the interpretation.
Not a hidden verdict
The interpreter produces facts only. NEES Core produces the governance decision.
Repeatable challenge
Change authority, scope, relationship or policy and run the same scenario again.
Release candidate / hosted acceptance pending
Safe Synthetic Execution Proof
The Scenario Decision Sandbox above assesses editable facts only. This separate proof qualifies a fixed consequential synthetic operation, starts it with a Runtime permit, sorts [3, 1, 2] in memory and reports the actual result. No external tool is executed.
governance_lab.synthetic_action.v1 / governance-lab:synthetic-action:v1 / governance_lab.synthetic_resource
- Submit: not verified
- Qualified: not verified
- Started: not verified
- Reported: not verified
- Evidence: not verified
- Receipt: not verified
Execution is disabled or unavailable. An owner-approved isolated Runtime and shared abuse controls must be configured before running this proof.