Pick a group, destination and detector class to see a resolution trace from the current deterministic policy-engine package. This browser tool does not call a deployed verdict service.
These three groups, five destinations and six rules are a demo policy set published as part
of this page. It is not a tenant's policy, no tenant policy is reachable from here, and
nothing you select is sent anywhere.
This page called evaluate() from @aidom/policy-engine — the same
function from the same package used by the POC enforcement path. Not a reimplementation for
the web. The trace above is the evaluator's own output, rendered without editing.
What is real here
01
The evaluator: this page imports and calls evaluate() from
@aidom/policy-engine directly. No policy logic is re-derived for the web.
02
Eight of the ten sandbox detector classes correspond to classes in the shipped
@aidom/detectors registry — checksum arithmetic and structural rules, exactly
as in the prompt sandbox.
03
Rollout-stage capping, exception precedence, and the fail-mode rung all run for real.
What this is not
01
The prompt sandbox says "Allowed" when nothing matches. The product has no such rung:
the action ladder is log-only → warn-then-confirm → hard-block, and the
least restrictive outcome still records the event. This viewer shows the ladder as the
contract defines it.
02
Crown-jewel EDM and source-code are demo stand-ins, marked DEMO CLASS wherever they
appear — there is no current registry class behind either one.
03
Not a rule editor, not a snapshot uploader, not a dry-run over a corpus, and not
connected to any live control plane — those are console surfaces.