Execution Gates

Start with a scenario, adjust destination and reliance, then watch the gate pathway: review, approval or block. The demo shows one possible policy in plain code.

Demo only

Logic is in src/lib/gateRules.ts. Extend or replace it for your environment.

What this shows

Risk changes when an output is used, not only when it is generated.
A summary in a workspace is lower risk than advice sent to a client; gates encode that distinction.
Governance belongs at the point of use: destination and reliance, not the prompt alone.

Scenario briefing

Choose a release context, then adjust controls. The same generated output can require very different gate behaviour once destination and reliance change.

Current narrative

An internal memo is being prepared for team coordination, useful output with moderate reliance and no external release yet.

Gate controls

Output type

Destination

Sensitivity

Reliance level

Gate storyline

Required gate

Review

Release status

Allowed With Controls

Governance weight

Moderate

Check load

1 Required

1
Output prepared
2
Destination assessed
3
Reliance scored
4
Gate selected
5
Checks completed
6
Release decision
Reviewer sign-off required

Related playbook