OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Agent ecosystem · Durable runtime
Run loops that survive retries, restarts, and operator intervention.
Durability comes from explicit memory, checkpoints, queues, leases, idempotency, cancellation, and evidence—not from keeping one process alive.
Runtime building blocks
Encrypted memory
The runtime encrypts serialized session memory through a consumer-owned cipher/KMS port before durable persistence.
Tenant-bound Postgres
Stores require tenant identity and can generate private-schema, least-privilege, RLS, and FORCE RLS migrations.
Continuous workers
Schedulers enqueue bounded work while leased workers retry idempotently and recover after process death.
Failure operations
Expiry, cancellation, retry budgets, dead-letter state, replay, and operator evidence remain explicit.
Harden the Postgres boundary
The migration hardening options are additive. Bind the session tenant context and runtime roles in the trusted host.
import {
migratePostgresAgentMemoryStore,
createPostgresAgentMemoryStore,
} from "@lssm-tech/integration.agent-durable-store/postgres";
await migratePostgresAgentMemoryStore(database, {
schema: "agent_runtime",
privateSchema: true,
enableTenantRls: true,
forceRowLevelSecurity: true,
runtimeRoles: ["agent_runtime"],
readonlyRoles: ["agent_auditor"],
});
const memoryStore = createPostgresAgentMemoryStore({
database,
tenantId,
schema: "agent_runtime",
});Realtime is not durable memory
Presence, WebSockets, and realtime broadcasts improve responsiveness but cannot replace the event log, checkpoint store, queue, or replay cursor.
Continuous-loop checklist
Scheduling
Use cron or queues only to enqueue bounded work with a stable dedupe key.
Leases
Fence stale workers and reclaim expired work without duplicating effects.
Retries
Classify failures, persist next-attempt time, cap attempts, and apply backoff.
Dead letters
Persist exhausted work, emit one redacted operations event, and require audited replay.
Governed self-improvement
Propose, evaluate, approve, canary, apply, observe, and roll back agent improvements with policy and safety controls.
Self-maintaining APIs
Ingest trusted sources, analyze impact, approve signed migration packs, run CI, prepare draft PRs, and preserve rollback boundaries.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.