Skip to content

Feature taxonomy

Runtime governance, grouped by the problem it solves.

Edictum is not a loose feature dump. Each family answers a concrete operational question about agent actions, policy, approvals, evidence, rollout, integration, or team visibility.

Categorized features

The complete feature map.

Roadmap

01

Runtime Decisions

Now

Should this agent action run right now?

Evaluate every tool call before execution and return a deterministic allow, block, ask, warn, or redact decision.

attempted action -> decision -> allow/block/approval -> audit record

  • Pre-tool decisions
  • allow, block, ask, warn, redact
  • Principal-aware evaluation
  • Side-effect aware rules
  • Structured block reasons
  • Dry-run evaluation

02

Rulesets And Policy-As-Code

Now

What is this agent allowed to read, write, call, or return?

Write versionable YAML rules for pre, post, session, and sandbox checks instead of burying policy in prompts.

  • YAML rulesets
  • Pre, post, session, and sandbox rules
  • Operators and variable interpolation
  • Ruleset templates
  • Schema validation
  • Future inheritance and overlays

03

Workflow Gates

Now

Did the agent follow the required process before moving on?

Require ordered stages, checks, evidence, and terminal states before high-impact actions are allowed.

  • Ordered stages
  • Entry and exit conditions
  • Evidence requirements
  • Terminal stages
  • Stage snapshots
  • Workflow conformance fixtures

04

Human Approval Gates

Now

Which actions need a human decision before execution?

Keep humans in the review path where it matters, with timeout behavior and recorded approval decisions.

  • ask decisions
  • Timeout behavior
  • Approval backend
  • Approval queues
  • Telegram approval path
  • Webhook and notification channels

05

Audit, Evidence, And Reporting

Now

Can we prove what happened later?

Record decisions, workflow state, policy versions, approval actors, and run/session correlation for later review.

  • Structured audit events
  • Local audit sinks
  • Server-backed audit
  • Signed decision bundles
  • Workflow snapshots
  • Run and session correlation

06

Replay And Blast-Radius Preview

Next

What would this rule change have changed?

Replay prior decisions against candidate rulesets before promoting policy changes across agents.

  • Ruleset replay
  • Would-block analysis
  • Saved versions
  • Promotion safety
  • Blast-radius summary

07

SDKs And Framework Adapters

Now

Can I use this with my current agent stack?

Use the same rule model across Python, TypeScript, Go, and common agent frameworks without moving enforcement out of the runtime path.

  • Python SDK
  • TypeScript SDK
  • Go SDK
  • Shared schema fixtures
  • LangChain, LangGraph, OpenAI Agents, CrewAI
  • Claude SDK, Google ADK, Semantic Kernel, Vercel AI SDK

08

Gate CLI And Coding Assistants

Now

Can Edictum control coding agents and local tool runners?

Run local policy checks, workflow gates, audit WAL, and assistant hooks around command-line tool execution.

  • Go CLI
  • edictum validate, check, replay
  • edictum gate init and gate run
  • Local WAL
  • Skill scanner
  • Self-protection rules and ruleset signing

09

Reference API/App Stack

Now

How do teams coordinate visibility, approvals, and audit?

Self-host the optional API/app reference stack for shared visibility while enforcement stays in the agent runtime path.

  • API keys
  • Event ingestion
  • Runs and agents
  • Rulesets and versions
  • Approvals and audit feed
  • SSE hot reload and notification channels

10

Security And Compliance Starters

Next

What common agent risks can I cover immediately?

Start from practical controls for destructive commands, secret redaction, data scope, and agentic-risk mappings.

  • Adversarial tests
  • Secret redaction
  • Destructive command blocking
  • Data scope restrictions
  • Prompt-injection-adjacent tool controls
  • OWASP Agentic starter controls

Adoption paths

OSS first. Reference stack when needed. Design partners for real production workflows.

OSS runtime

Start here

Install the SDK or Gate CLI, load YAML rules, and enforce locally in the agent path.

Read the docs

Optional reference stack

Self-host

Add the API/app reference stack when teams need approvals, event ingestion, audit feed, and ruleset versions.

Deploy guide

Design partner path

Feedback

For teams running agents that touch real systems and need runtime control before tool execution.

Discuss fit