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 ยท Production readiness

Promote one exact plan only after its live evidence passes.

Qualification is digest-bound to the source, profiles, controls, environment, declared losses, and complete suite set. It never promotes a provider globally.

Responsibility boundary

Repository-provided

Contracts, adapters, deterministic conformance, security gates, reference topologies, and qualification machinery.

Consumer-owned

Identity, credentials, KMS, tenant mapping, storage policy, live providers, budgets, observability sinks, and incident ownership.

Evidence-required

Live isolation, authorization, restore, RPO/RTO, failover, load, redaction, canary, and rollback results for the exact plan.

Run live qualification

import { AgentPlatformQualificationRunner } from
  "@lssm-tech/integration.runtime/agent-platform";

const qualification = await new AgentPlatformQualificationRunner({
  profiles: myPinnedProfiles,
  suites: myLiveSuites,
}).run({
  composition,
  sourceRevision: gitCommitSha,
  environmentDescriptor: redactedEnvironmentDescriptor,
  declaredLosses: acceptedLosses,
  evidenceRefs: [rootEvidenceBundleRef],
});

if (qualification.report.overall !== "pass") {
  throw new Error("Agent platform is not production-qualified");
}

Mandatory evidence

Gate 1

Tenant and workspace isolation, including cross-scope denial.

Gate 2

Authentication, authorization, revocation, and break-glass audit.

Gate 3

Durable replay, idempotency conflicts, process death, and stale writes.

Gate 4

Queue redelivery, poison items, retry exhaustion, and audited dead letters.

Gate 5

Backup restore, measured RPO/RTO, failover, reconnect, and load.

Gate 6

Sandbox containment, resource limits, network/mount denial, and teardown.

Gate 7

Redacted audit, trace, metric, cost, and budget export.

Gate 8

Dependency, static-analysis, clean-consumer, canary, and rollback evidence.

Candidate versus qualified

candidate

A repository-supported profile whose contracts, templates, and deterministic checks pass. Candidate status does not certify a consumer environment for production.

qualified

A candidate whose complete live suite passes for the exact source revision, configuration, credentials, region, controls, and plan digest being promoted.

Release checks

bun run security:advisories
bun run verify:export-integrity
contractspec release build
contractspec release check --strict

# Then publish and verify a canary in clean Node and Bun consumers.

AI agent package reference

Reference application guide

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

Deploy agent systems

Choose replaceable Vercel, Railway, Supabase, Docker, or custom-provider topologies and assign infrastructure responsibilities.

Next

Domains overview

Navigate AuthOS, BillingOS, CompanyOS, CommunicationOS, and other product operating domains across web and mobile.

Why ContractSpec

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

ManifestoContract-first APISpec-driven development