RUGet started
Program Runtime · architecture preview

The platform executes programs, not a catalog of special nodes

Agent stays the product-level identity. Underneath it can run a visual process or a native Program built from events, state, waits and isolated execution.

Visual processes currently remain on Graph Runtime. Native Program advances through separate technical gates; graph migration starts only after trace, output and effect parity.
Visual BuilderAI BuilderCode
→
Program Runtimeevents · state · effects · waits
→
Runners

PostgreSQL owns the journal, state and outbox. Redis accelerates wakeups and is fully recoverable.

01

Architecture

Modules, versioned contracts, capabilities and subscriptions. The view communicates process architecture instead of technical if/switch/merge plumbing.

Module
  accepts(event, state)
  execute(context)
  emits(events, effects, waits)
02

Events

Every event carries correlation and causation. Subscribers independently decide whether to accept it.

cron.reconciliation.requested
  → source.loaded
  → reconciliation.completed
  → report.created
03

Run

A Run pins an immutable Release. Activations, attempts, effects and waits remain observable across restarts.

running → waiting_approval
        → resumed
        → completed
04

State

A state patch, emitted events and outbox commit atomically. An ambiguous external write must be reconciled.

transaction {
  state + events + outbox
}
redis = recoverable accelerator

Capability boundary

Control Plane

Users, spaces, Agent identity, Connections, Secrets, Policies, billing and runner registry.

Program Runtime

Programs, Releases, event journal, state, activations, barriers, waits, timers and effect intents.

Runner plane

Executes an ActivationSpec in isolation and returns a result. Runtime chooses what runs next.

What we do not claim yet

We do not claim exactly-once, unrestricted code, universal failover or Agent memory. Those properties ship only after their technical gates pass.