EdictumRuntime Core And Reference Stack
Enforcement lives in the SDKs and Gate runtime. The reference API/app stack is optional coordination for rulesets, approvals, events, and visibility.
Right page if: you are deciding whether you need the optional API/app stack in addition to the SDKs or Gate runtime. Wrong page if: you need the actual workflow format -- see https://docs.edictum.ai/docs/reference/workflows or https://docs.edictum.ai/docs/guides/workflow-gates. Gotcha: Workflow Gates do not run in the reference API/app stack. They run in the SDK or Gate runtime.
Edictum's product center is runtime governance. The SDKs and Gate runtime make decisions before tools execute.
The reference API/app stack is optional. Use it when teams need shared ruleset delivery, centralized approvals, event ingestion, and visibility across agents.
Runtime Core
The runtime core does the enforcement work:
- runtime decisions
- rulesets
- Workflow Gates
- local approvals
- audit sinks
- adapters
- Gate CLI enforcement
No reference-stack server is required to enforce behavior. Workflow Gates run in the SDK or Gate runtime when that runtime version supports the workflow surface you are using.
Reference API/App Stack
The reference stack coordinates work across agents:
- remote ruleset delivery
- centralized approvals for server-backed agents
- event ingestion and audit feed
- runs and agent visibility
- bundle/ruleset management
- SSE hot reload for rulesets
It does not evaluate production tool calls for the agent. It also does not execute Workflow Gates.
Workflow YAML stays in the SDK or Gate runtime today.
Boundary
| Need | Runtime core | Reference API/app stack |
|---|---|---|
| Tool-call enforcement | Yes | No |
| Ruleset evaluation | Yes | No |
| Workflow Gates | SDK/Gate runtime, version-specific | No |
| Local/offline use | Yes | No |
| Local audit sink | Yes | No |
| Remote ruleset distribution | Optional client | Yes |
| Central approval records | Optional client | Yes |
| Audit feed and run visibility | Optional client | Yes |
When To Use Each
Use the runtime core when:
- one agent process can load its own ruleset
- the workflow can be attached locally
- local audit sinks are enough
- you want Gate to control a coding assistant or local tool runner
Add the reference stack when:
- multiple agents need the same deployed ruleset
- a team needs a central approval queue
- audit events need to land in one feed
- operators need run and agent visibility
- rulesets should hot-reload over SSE
What To Read
Last updated on