Edictum

How It Works

Current conceptual boundary between the SDK runtime and the hosted control plane.

AI Assistance

Right page if: you want the current conceptual model. Wrong page if: you want the retired single-image server architecture. Gotcha: the control plane stores and streams state; the SDK runtime still enforces rules locally.

Edictum has a hard boundary:

  • the SDK runtime evaluates rules locally inside the agent process
  • the hosted control plane stores, streams, and presents workspace state

Local Runtime

The SDK runtime is responsible for:

  • rule evaluation
  • workflow evaluation
  • tool-call allow / block / ask decisions
  • fail-closed behavior inside the agent

Hosted Control Plane

The hosted control plane is responsible for:

  • ruleset distribution
  • event ingest and querying
  • approval records and operator decisions
  • audit visibility
  • notification delivery
  • agent and run views in the app

Data Flow

  1. the agent evaluates locally
  2. the agent posts decision events to edictum-api
  3. the agent fetches rulesets from edictum-api
  4. the agent listens on /v1/stream for updates
  5. operators use edictum-app to inspect runs, approvals, events, audit, and settings

What This Is Not

It is not the retired model where one server both owned the runtime and served a large bundle/composition management surface.

For current route-level truth, use:

Last updated on

On this page

Local RuntimeHosted Control PlaneData FlowWhat This Is Not