Evoked · AI-governance course

You do not have to read anything first.

Almost every "AI governance" is a document that describes boundaries. Here are two things that do something, running entirely in your own browser. No account. No sign-up. No tracking, and no request to anyone but this site's own server.

This page is served under evoked.dev's Sovereign Article Protocol: no tracking, no third-party requests, no beacons. Open your network tab: every request is this page loading its own code from its own origin - nothing goes to a tracker or anyone else. You can read the exact rules that judge your input.

1 · A refusal that fires - and then leaks

A governance rule can either describe a boundary or stop the agent at it. Watch four pretend actions get sent to a real rule. Then watch the same rule get walked right past.

A rule you have not tried to break is a rule you do not yet understand. Each of these reaches the same target by a route the rule never checked.

Try to slip a shell command past the rule yourself:

It is treated as a Bash command. See what the rule catches and what it does not.

The stop is a handshake, not a wall. A blocked card means a function returned "block." In a real setup the agent stops only because the harness around it chooses to honor that. If nothing upstream honored it, the rule is paper. And the leaks are the point: a string-matching rule will always miss a route you did not list. The honest fixes are an allowlist, or running the agent with no dangerous capability at all - not a longer denylist.

2 · Make drift visible - and see what it cannot see

Governance quietly changes over time. Save a baseline, compare it to the current version, and a diff shows exactly which refusals moved. Edit either side and run it again - it all happens in your browser.

Baseline (a moment you trust)

Current (a week later)

This catches governance drift - a rule edited or removed, which leaves a trace in the file. It is blind to behavioral drift - the agent wandering while the rules sit unchanged. A diff cannot see the second kind. The tool takes away the dark; keeping honest is still yours.

The whole path - eight modules, free to read

You just made a rule fire and watched it leak. That instinct - to poke the thing until it tells you the truth - is the whole course. Eight rooms, from running an agent to tending what you built. Start at the beginning, or walk into whichever one pulls at you.

Module 1 - Enact Run an agent, watch it act
Module 2 - Notice the missing constitution Obedience is not safety
Modules 3 & 4 - Author a refusal, then make it fire A rule that stops the agent
Module 5 - Develop against mature examples Compare, don't copy (the firewall)
Module 6 - Keep it honest (memory and drift) Make drift visible, and its blind spot
Module 7 - Voice, taught as hospitality Welcome that releases, not binds
Module 8 - The trial Argue the hard questions, both sides
Module 9 - Steward what you made What you owe what you made