ContractSpec docs

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.

Feature Hubs

Agent System Hub

Operate one tenant-local agent system, whether it contains one agent or many.

Local authority

Every tool call is re-evaluated by the target system policy.

Operations

Runs, memory, mailboxes, approvals, replay, evaluation, improvement, budgets, and kill switches.

Copy-ready example

import { installAgentSystemHub } from "@lssm-tech/module.agent-fleet/hub";

const hub = await installAgentSystemHub({
  context,
  ports: yourProviderNeutralPorts,
  evaluatePolicy: (policyId, operationRef) =>
    policyEngine.evaluate({ policyId, operationRef, context }),
  fulfillPolicyObligations: (request) => obligationRuntime.fulfill(request),
});
await hub.start();

Production truth

Deterministic fixtures, adapters, and provider templates remain candidate. Qualified means the consumer has passed live provider, infrastructure, security, restore, failover, canary, rollback, and operator qualification in the exact environment.

Related package reference

Runnable all-nine reference app

OSS docshubsStart with OSS. Adopt Studio when you want the operating layer.

Why ContractSpec

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