Reference

What the runtime guarantees

Limits that hold whatever the model decides, each proven by a test.

  • Budgets can't be exceeded by a team, and only a person adds more.
  • Permissions only narrow from parent to child.
  • Durability: an interrupted run resumes; a non-idempotent call is never repeated blindly.
  • Approvals: a call marked "ask" never runs before a person approves it, and runs once after.
  • Tenant isolation in messaging, discovery, memory, SQL, records, and every way in.
  • End users reach only their own conversations and records, enforced in the tools themselves.
  • Every record write is checked, and each change fires a trigger once.
  • Registry packages are verified against their digest and signature at install.
  • The audit chain detects edits, insertions and deletions.

Each guarantee is enforced in the runtime itself and covered by automated tests.