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.

AI index

Agent ecosystem ยท Deployment

Choose infrastructure by responsibility, budget, security, and residency.

ContractSpec profiles describe capabilities and proof requirements without coupling the agent contracts to one deployment vendor.

Provider responsibilities

Vercel

Web/API, streaming, bounded jobs, and durable workflows.

Railway

Always-on workers, WebSockets, and queue consumers.

Supabase

Postgres, identity, realtime signals, queues, and scheduling.

Docker

Packaging and isolation for untrusted agent execution.

Custom provider

Consumer-owned infrastructure behind the same typed capability, evidence, and qualification contracts.

Reference topologies

Vercel + Supabase

Serverless-first web/API with managed data; add an external always-on worker when workloads exceed bounded execution.

Railway + Supabase

Always-on services, WebSockets, and workers with managed Postgres, identity, queues, and realtime.

Vercel + Railway + Supabase

Split web/API, long-lived workers, and managed data into independently scalable responsibilities.

Docker or custom

Maximum control over isolation, residency, and operations while implementing the same typed profile and qualification contracts.

Compose before provisioning

import { composeReferenceAgentPlatform } from
  "@lssm-tech/example.agent-application-foundation/enterprise-platform";

const selected = composeReferenceAgentPlatform(
  "vercel-railway-supabase",
);

if (selected.composition.unresolvedRequirements.length > 0) {
  // Expected while selected profiles remain candidate.
  // Supply target-specific controls and run live qualification.
}

Secrets are references

Provider credentials, model keys, signing keys, and database passwords stay in the selected secret manager. Specs, plans, replays, and evidence contain only approved references and redacted metadata.

Local Docker reference

cp deploy/enterprise-agent-platform/.env.example \
  deploy/enterprise-agent-platform/.env

docker compose \
  --env-file deploy/enterprise-agent-platform/.env \
  -f deploy/enterprise-agent-platform/docker-compose.yml config

AI agent package reference

Reference application guide

OSS docsagentsStart with OSS. Adopt Studio when you want the operating layer.
Previous

Self-maintaining APIs

Ingest trusted sources, analyze impact, approve signed migration packs, run CI, prepare draft PRs, and preserve rollback boundaries.

Next

Production readiness

Qualify candidate deployments with baseline and live suites, observability, security, restore, failover, canary, and rollback evidence.

Why ContractSpec

Keep educational and comparison content reachable without letting it define the primary OSS learning path.

ManifestoContract-first APISpec-driven development