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 · Multi-agent
Coordinate agents and people through explicit authority and durable shared work.
ContractSpec separates child-agent delegation, elastic worker teams, and multiplayer collaboration so each product can adopt the smallest coordination model it needs.
Choose the coordination model
Subagent dispatch
One parent delegates bounded context, tools, budget, timeout, and approval authority to an isolated child session.
Elastic execution teams
Workers join or leave restart-safe teams while claims, leases, mailboxes, evidence, and verifier ownership remain durable.
Multiplayer sessions
Authorized humans and agents share a live session through watch, comment, redirect, pause, resume, and handoff commands.
Wire an authenticated multiplayer gateway
Resolve principals only from host-trusted identity claims. Request bodies never grant their own participant identity or capabilities.
import { createCollaborationService } from
"@lssm-tech/lib.agent-collaboration";
import { createCollaborationGateway } from
"@lssm-tech/integration.runtime/agent-platform";
const service = createCollaborationService(collaborationStore);
const gateway = createCollaborationGateway({
service,
auditSink,
principalResolver: {
async resolve(authContext) {
return resolveTrustedPrincipal(authContext);
},
},
signalBus,
});Postgres replay is authoritative
Realtime or WebSocket signals are wake-up hints. Durable session events, CAS versions, idempotency keys, revocation, and replay cursors determine the committed state, so a signal outage cannot erase accepted work.
Operating invariants
Enforce these rules in every adapter and host.
Least authority
History, tools, approval receipts, tenants, and write scopes are deny-by-default and explicitly granted.
Retry-safe coordination
Claims, mailbox messages, commands, and effects use stable dedupe keys and stale-write rejection.
Evidence before completion
Terminal team completion can require task evidence, run evidence, and verifier signoff.
Human control
Pause, redirect, cancel, revoke, and handoff remain explicit authorized commands with audit evidence.
Build your first agent
Install the agent packages, author and compile a filesystem agent, choose a runtime adapter, and run the reference application.
Governed self-improvement
Propose, evaluate, approve, canary, apply, observe, and roll back agent improvements with policy and safety controls.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.