Edictum

Developer agent behavior platform for Python, TypeScript, and Go. Workflow Gates, rulesets, and adapters that make agent behavior predictable.

Agents are good at saying the right thing and still calling the wrong tool. Edictum gives you rules and Workflow Gates so the behavior is actually enforced.

Start here:

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 a developer agent behavior platform built around three things:

Workflow Gates for stage-based process enforcement.
A rules engine for tool calls, output checks, sandbox boundaries, and session limits.
Cross-framework adapters so the same ruleset works 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
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. Rules are about single tool calls. Workflow Gates are about ordered work:

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"