Edictum

Roadmap

Current shipped surface and near-term direction for Edictum.

AI Assistance

Right page if: you want the current public truth about what Edictum ships today and what is next. Wrong page if: you need setup or API details -- use the surface-specific docs directly. Gotcha: this page is intentionally short. It is not a historical dump of retired server-stack plans.

This page tracks current public truth, not every historical idea.

Shipped Today

Core SDKs

  • Python: edictum
  • TypeScript: @edictum/core plus adapters
  • Go: github.com/edictum-ai/edictum-go
  • Shared kind: Ruleset / rules: YAML format across the SDKs
  • Rule types: pre, post, session, sandbox
  • Current actions: block, ask, warn, redact
  • Templates, observe mode, audit sinks, OpenTelemetry, and approval backends

Gate

  • Local pre-execution enforcement for coding assistants
  • Canonical CLI shipped from edictum-go
  • edictum validate, check, diff, replay, test, skill scan
  • edictum gate init, gate run, gate check, gate status, gate audit, gate sync

Workflow Gates

  • Ordered stage enforcement on top of rulesets
  • Stage tool allowlists and glob patterns
  • File-read, command, approval, and MCP-result evidence
  • Terminal stages
  • Shared v0.18 workflow semantics landing across the SDKs

Hosted Control Plane

  • Hosted beta at app.edictum.ai and api.edictum.ai
  • Rulesets, runs, events, approvals, audit, agents, API keys, and notification channels
  • Telegram is interactive today
  • Slack, Discord, and webhook are notification channels
  • No public self-serve Stripe billing yet
  • No public self-serve Docker Compose or Railway path

In Progress

  • Release sweep for the post-tag work now sitting in edictum, edictum-ts, and edictum-go
  • First public release/tag flow for edictum-schemas
  • Public docs catch-up for the newest workflow semantics and ruleset inheritance helpers
  • Cleanup of stale demo content and repo metadata that still speaks in legacy ruleset/control-plane terms

Planned Next

  • Better release hygiene so tags, package versions, docs, and repo metadata stay aligned
  • More ruleset and workflow examples tied to the real shipped API/app surface
  • Dedicated deployment and self-hosting conversations handled directly instead of fake self-serve docs

Not Current

These are not current public promises:

  • edictum-console as the canonical product
  • legacy pre-ruleset YAML syntax
  • $39 hosted pricing
  • self-serve Docker Compose, Railway, or Render setup for the control plane
  • notification or approval flows that the app/API do not actually ship

Use the surface-specific docs as the source of truth:

Last updated on

Licensing

Edictum core is MIT. Edictum Control Plane is FSL-1.1-ALv2 (source-available, converts to Apache 2.0). No per-agent fees, no usage limits, no vendor lock-in.

On this page

Shipped TodayCore SDKsGateWorkflow GatesHosted Control PlaneIn ProgressPlanned NextNot Current