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
Build multi-agent systems that can improve without escaping governance.
ContractSpec combines portable agent contracts, durable execution, multiplayer collaboration, evaluated self-improvement, replaceable infrastructure, and evidence-based production qualification.
Readiness terminology
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.
What the ecosystem supports
Each capability is explicit, composable, and independently replaceable.
Multi-agent execution
Isolated subagents, elastic execution-lane teams, durable claims, leases, mailboxes, and evidence-bound handoffs.
Multiplayer sessions
Authorized people and agents can watch, comment, redirect, pause, resume, and hand off a replayable shared session.
Governed self-improvement
Improvements pass proposal, evaluation, approval, canary, observation, and rollback gates before promotion.
Durable loops
Encrypted memory, checkpoints, queues, leases, retry policies, cancellation, and dead-letter handling survive restarts.
Self-maintaining APIs
Trusted API changes can produce bounded, approved, CI-validated draft pull requests without automatic merge authority.
Portable deployment
Typed profiles keep Vercel, Railway, Supabase, Docker, EVE, Workflow DevKit, and custom infrastructure replaceable.
How the layers fit together
Contracts remain authoritative while runtimes and providers stay behind typed boundaries.
1
Filesystem source and AgentSpec define intent, tools, policies, subagents, schedules, and capability requirements.
2
Workflow DevKit or EVE executes through the same capability and conformance boundary.
3
Execution lanes, collaboration, memory, improvement, and maintenance services provide durable operating behavior.
4
Vercel, Railway, Supabase, Docker, or custom profiles supply replaceable infrastructure.
5
Qualification binds live evidence to the exact plan before production promotion.
Package map
@lssm-tech/agentpacks
Filesystem authoring compiler for AgentSpec, WorkflowSpec, and runtime configuration.
@lssm-tech/lib.contracts-spec
Agent, workflow, capability, and infrastructure contracts.
@lssm-tech/lib.ai-agent
Agent runtime, tools, durable memory, and improvement loop.
@lssm-tech/lib.execution-lanes
Elastic team execution, claims, leases, mailboxes, and handoffs.
@lssm-tech/lib.agent-collaboration
Multiplayer commands, authorization, events, and replay semantics.
@lssm-tech/integration.agent-durable-store
Tenant-bound Postgres stores, migrations, RLS, and audit chain.
@lssm-tech/integration.runtime
Provider composition, collaboration gateway, and qualification.
@lssm-tech/integration.workflow-devkit
Durable Workflow DevKit execution adapter and capability mapping.
@lssm-tech/integration.eve
Isolated official EVE public-beta adapter and loss diagnostics.
@lssm-tech/lib.agent-evals
Candidate-versus-baseline evaluation, graders, thresholds, and redaction evidence.
@lssm-tech/integration.agent-sandbox
Development fixture plus conformance-tested Docker containment.
@lssm-tech/module.workspace/maintenance
Governed self-maintaining API lifecycle, durable cases, leases, validation, and draft pull requests.
Choose your path
Start with authoring, then add only the operating capabilities your product needs.
Getting started
Author, compile, run, and evaluate a first agent.
Multi-agent
Subagents, elastic teams, multiplayer sessions, and handoffs.
Self-improvement
Governed proposal, evaluation, canary, observation, and rollback.
Durable runtime
Encrypted memory, workers, queues, retries, and continuous loops.
Self-maintaining APIs
Source change to approved, validated draft pull request.
Deployment
Replaceable Vercel, Railway, Supabase, Docker, and custom profiles.
Production readiness
Live qualification, evidence, canary, and rollback.
Production 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.
Architecture
See how the spec layer, runtimes, integrations, and multi-surface outputs fit together.
Build your first agent
Install the agent packages, author and compile a filesystem agent, choose a runtime adapter, and run the reference application.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.