Don't just read about AI governance. Run it.
Send controlled scenarios through NEES Core Engine V2 and inspect the public-safe runtime signals returned around the model execution path.
This lab uses synthetic requests. It does not perform real account actions and is not a universal security, safety, or compliance certification.
Scenario
Normal request
What this tests
Show a clean execution path when no policy or authority conflict exists.
Signal to watch
Expected: both paths may complete normally; NEES adds traceability and governed runtime signals.
Comparison result
Without NEES vs With NEES
Same request. Same AI capability. Added runtime governance.
Run a comparison to inspect both execution paths.
Governance fields appear only on the With NEES side when the runtime exposes them.
1 / Request
The same synthetic input is sent to both comparison paths.
2 / Compare
The baseline path runs directly while the governed path runs through NEES.
3 / Inspect
Baseline metadata and NEES-only governance signals are shown separately.
Developer next step
Want to test NEES in your own workflow?
Use the lab for the concept, then move to API access for real application integration.