ProxyCore Overview
ProxyCore is the runtime that executes workflows: it reacts to events, runs steps in order, enforces the permissions each step declared, and records what happened. Workflows are defined in ProxyLang and run on ProxyCore. It is the governance runtime underneath EXOS and the workflows deployed in an engagement. In preview.
Start here
- Installing ProxyCore — build the workspace, run the runtime, configure it.
- Core concepts — the primitives in depth: data, events, permissions, state, agents, audit.
Core concepts
Workflows
A workflow is a named unit of automation triggered by an event. It owns its permissions and a sequence of steps. Everything ProxyCore runs is a workflow.
Events
Workflows react to events — for example event("form.submitted"). An event carries a payload the workflow's steps can read, within their granted permissions.
Steps
A step is a unit of work inside a workflow. A step can declare the model tier it uses, a token budget, and a fallback — so cost and behavior are part of the definition, not an afterthought. Steps can branch with when / else.
Permissions
Permissions are granted explicitly, per workflow, following least-privilege: a step gets only the reads and writes it needs (permit agent.read = [crm]). They are declared up front so they show up in review, not in production.
Audit
A workflow can mark itself to log its decisions (audit all), so you can reconstruct what ran, with what inputs. Audit coverage is expanding through preview — see the status note below.
Dashboards & surfaces
ProxyCore exposes workflow state to dashboards and connects to external systems through defined integration points, so operators can watch what is happening and act on it.
How a workflow runs
- You define the workflow, its permissions, and its steps in ProxyLang.
- ProxyCore runs it when its trigger event fires, enforcing the declared permissions.
- You observe state on dashboards and review the audit trail of each step.
For the full syntax and worked examples, see the ProxyLang language reference.
Status & limitations
ProxyCore is in active preview and dogfooding. It is not yet offered as a multi-tenant SaaS, and we do not describe it as "governed" or "tamper-proof" — those are goals with open work behind them, not claims we make today. Audit coverage and isolation are still maturing. If you are evaluating it for real work, tell us the constraint and we will be straight about fit.