Edictum

Agency control layer for production AI agents. Workflow Gates, rulesets, and adapters that turn documented profiles into runtime boundaries.

Edictum is the agency control layer for production AI agents. Agent frameworks build the agent. Edictum bounds the agency.

It turns a documented agent profile into executable runtime boundaries: Workflow Gates enforce ordered process with evidence, rulesets enforce single tool-call boundaries, and adapters make the same control model framework-independent.

Start here:

Agency Control

Map low, medium, and high agency profiles to runtime boundaries.

Quickstart

Write one ruleset and block a bad tool call.

Workflow Gates Runtime

Stage work, require evidence, and pause for approval.

Workflow Reference

Real kind: Workflow fields, conditions, and validation rules.

Python SDK

Python core SDK, adapters, and server client.

TypeScript SDK

Node and TypeScript SDK with shared YAML semantics.

Go SDK

Go SDK with the same ruleset format and runtime model.

Ruleset Generator

Prompt an AI assistant with the right schema instead of the dead one.

What Edictum Is

Edictum is built around three runtime primitives:

Workflow Gates enforce ordered process with evidence and approvals.
Rulesets enforce single tool-call boundaries: pre-execution checks, sandbox boundaries, output checks, and session limits.
Adapters make the model framework-independent across Python, TypeScript, and Go.

The same rules.yaml works across all three SDKs.

Install

pip install edictum[yaml]

npm install @edictum/core

go get github.com/edictum-ai/edictum-go

Feature Order

Feature	What it solves	Start here
Agency Control	"What is this agent allowed to do, in what order, with what evidence?"	/docs/agency-control
Workflow Gates	"Did the agent follow the right process?"	/docs/guides/workflow-gates, /docs/reference/workflows
Rulesets	"Should this tool call be allowed, blocked, redacted, or asked?"	/docs/quickstart
Adapters	"How do I wire this into my framework?"	/docs/python, /docs/typescript, /docs/go

SDK Snapshot

	Python	TypeScript	Go
Core package	`edictum`	`@edictum/core`	`github.com/edictum-ai/edictum-go`
Workflow runtime	Yes	Yes	Yes
Ruleset format	YAML	YAML	YAML
Remote/server integration	`edictum[server]`	`@edictum/server`	`edictum-go/server`
Telemetry	OpenTelemetry	OpenTelemetry	OpenTelemetry

Workflow Gates First

Workflow Gates are the differentiator. Rulesets handle one tool call at a time. Workflow Gates enforce the ordered work that makes a profile defensible:

Read the spec before editing.
Run git diff before review.
Require tests to pass before merge.
Pause for human approval at the next stage.

apiVersion: edictum/v1
kind: Workflow
metadata:
  name: feature-delivery

stages:
  - id: implement
    entry:
      - condition: file_read("specs/feature.md")
        message: "Read the spec first"
    checks:
      - command_matches: "git diff"
        message: "Inspect your changes before review"
    exit:
      - condition: exec("pnpm test", exit_code=0)
        message: "Tests must pass"

  - id: review
    entry:
      - condition: stage_complete("implement")
    approval:
      message: "Human approval required"