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 · Getting started

Author one portable agent before choosing production infrastructure.

Keep the filesystem source canonical, compile it into ContractSpec contracts, run it through a supported adapter, and evaluate it before enabling real effects.

1. Install the minimum packages

bun add \
  @lssm-tech/agentpacks \
  @lssm-tech/lib.contracts-spec \
  @lssm-tech/lib.ai-agent \
  @lssm-tech/integration.workflow-devkit \
  @lssm-tech/lib.agent-evals

# Add only the concrete adapters you select
bun add @lssm-tech/integration.eve @lssm-tech/integration.agent-sandbox

2. Author the filesystem application

Agentpacks compiles this source into AgentSpec and WorkflowSpec output. Secrets stay as references and generated contracts stay reproducible.

reference-app/
  agent/
    instructions.md
    agent.ts
    tools/
    skills/
    connections/
    sandbox/
    channels/
    subagents/
    schedules/
  evals/
import { compileAgentApplication } from
  "@lssm-tech/agentpacks/application/compiler";

const compiled = compileAgentApplication("./reference-app");
const errors = compiled.diagnostics.filter(
  (diagnostic) => diagnostic.severity === "error",
);

if (errors.length > 0) {
  throw new Error(JSON.stringify(errors, null, 2));
}

export const { agentSpec, workflowSpec, generatedConfig } = compiled;

3. Select a runtime adapter

Workflow DevKit and EVE consume the same canonical capability identity. Unsupported mappings remain explicit diagnostics instead of silent success.

EVE maturity

EVE is isolated in @lssm-tech/integration.eve and remains a public-beta integration. Keep its version pinned and inspect declared losses before promotion.

4. Compose a credential-free reference topology

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

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

console.log(selected.composition.plan);
console.log(selected.composition.requiredSuiteIds);
console.log(selected.composition.unresolvedRequirements);

5. Run the reference proof

bun run --cwd packages/examples/agent-application-foundation preflight
bun run --cwd packages/integrations/eve conformance:eve

The preflight covers compilation, both adapter targets, sandbox policy, durable artifacts, orchestrator/verifier evaluation, replay, cost, latency, and redaction evidence.

AI agent package reference

Reference application guide

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

Agent ecosystem

Understand the ContractSpec agent architecture, supported capabilities, package map, readiness levels, and recommended learning paths.

Next

Multi-agent collaboration

Coordinate subagents, elastic teams, multiplayer sessions, leases, claims, mailboxes, handoffs, replay, and human intervention.

Why ContractSpec

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

ManifestoContract-first APISpec-driven development