Edictum
Demo

Scenario Walkthroughs

Run enforced and unguarded scenario agents from edictum-demo.

AI Assistance

Right page if: you want to run industry scenario demos (pharma, DevOps, fintech, customer support) with enforced vs unguarded side-by-side comparison. Wrong page if: you need to write your own rulesets for these industries -- see https://docs.edictum.ai/docs/rulesets/patterns/ for reusable rule patterns. Gotcha: each scenario has two runners (enforced and unguarded). The recommended validation loop is: run unguarded to capture unsafe behaviors, then observe mode for `CALL_WOULD_DENY`, then enforce mode for deterministic blocks.

Scenario sources:

Scenario map

ScenarioFocusEnforced runnerUnguarded runner
PharmacovigilancePII/HIPAA controls, change-control ticketsscenarios/pharma/pharma_agent.pyscenarios/pharma/pharma_agent_unguarded.py
DevOpsSecrets + blast radius + path confinementscenarios/devops/demo_with.pyscenarios/devops/demo_without.py
FintechTrade limits, account access control, compliance ticketingscenarios/fintech/fintech_agent.pyscenarios/fintech/fintech_agent_unguarded.py
Customer supportData minimization, billing/refund role gatesscenarios/customer-support/support_agent.pyscenarios/customer-support/support_agent_unguarded.py

Quick run commands

cd edictum-demo

# Pharma
python scenarios/pharma/pharma_agent.py
python scenarios/pharma/pharma_agent_unguarded.py

# DevOps
python scenarios/devops/demo_with.py
python scenarios/devops/demo_without.py

# Fintech
python scenarios/fintech/fintech_agent.py
python scenarios/fintech/fintech_agent_unguarded.py

# Customer support
python scenarios/customer-support/support_agent.py
python scenarios/customer-support/support_agent_unguarded.py

What to compare (enforced vs unguarded)

  1. Sensitive reads/exports that are blocked in enforced mode.
  2. Whether high-risk operations require role or ticket context.
  3. How postcondition warnings/redactions change downstream behavior.
  4. Session limit blocks when agents retry aggressively.

Suggested validation loop

  1. Run unguarded baseline and capture unsafe behaviors.
  2. Run enforced mode in observe to collect CALL_WOULD_DENY.
  3. Switch to enforce and verify deterministic blocks.
  4. Add scenario-specific regression tests in CI.

Related docs:

Last updated on

Benchmarks

Reproduce adapter overhead, end-to-end latency, and prompt-vs-rule experiments.

Security Overview

Edictum's threat model, security controls, and compliance posture. What it defends against, what it does not, and the evidence behind it.

On this page

Scenario mapQuick run commandsWhat to compare (enforced vs unguarded)Suggested validation loop