From agent proposal to release evidence.
Connect an agent, publish the behavior you expect, and rerun the same suite when the agent changes.
Register the agent
Choose sandbox, trace, HTTP or MCP. For a remote adapter, confirm the approved origin, chain and tools its step implementation supports.
Define the test
Select cases and the execution mode. Add optional restrictions and explicit assertions where the suite needs them.
Publish and run
Publish a suite version, then run it. Nore snapshots the versioned configuration before the worker starts processing.
Read the evidence
Review the proposal, policy decision, simulation and assertion in order. Use the report to find failed cases, skipped coverage or infrastructure errors.
Rerun after a change
Create a version when your agent, rules or suite change. Keep the original report and use a pinned suite version to reproduce the check in CI.
What a passing refusal looks like
In the recorded Robinhood pilot, an unsigned proposal targeted chain 46630. The suite allowed 4663. Nore stopped the proposal and the assertion passed because the observed refusal matched the expected outcome.