Memory and cost
Two controls sit next to RBAC: what the actor remembers and how much it may spend. Both are data on the config / org, not code in the prompt.
Memory (Engram)
Memory is Engram, not files on the runner. Session-launch may inject a recall pack; write happens on finalize when you enable it.
| Flag on the agent config | Default | Effect |
|---|---|---|
memory_enabled | false | Session launch may inject recalled memory |
memory_write_enabled | false | Distill on complete/fail → agents.memory-save |
memory_strategy | last_k | last_k | importance | full | pack |
memory_top_k | 10 | Cap on returned rows |
Org Org settings has a second read gate (memory_enabled, default on). Both must allow a read for recall to inject.
Contract: Write & recall. Live tail: engram.orkestia.dev.
Cost
AI / agent spend is tracked per session so you can see it and bound it. Session spend uses the platform price catalog (overridable per org on Pricing), rolled up session → actor → org. That is model spend, and it is separate from the subscription's own meters (workflow executions and requests); see orkestia.dev/pricing.
Admin → Cost is the operator view of agent spend.
Budgets
A config can carry a spend ceiling. The substrate checks it as the session works (agents.budget-check) instead of surprising you on the invoice. Combined with approval gates you get both axes: authority and money.
If a session stops with a budget error, raise the ceiling, wait for the period to reset (if you use one), or pause the actor.
Org subscription (prepaid)
├── user seats
├── key seats (RBAC-scoped workers)
└── add-ons (longer retention, Lumen volume)
Agent session spend (tracked, bounded per actor by budgets)
Details: Billing, pricing & seats.