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 · Self-maintaining APIs
Turn provider changes into reviewable consumer pull requests.
The maintenance runtime connects trusted API revisions to bounded analysis, approved changes, CI evidence, draft pull requests, rollback, and merged-outcome observation.
Lifecycle
trusted source revision
→ normalize and digest
→ analyze consumer usages
→ build signed bounded migration plan
→ policy and human approval
→ atomic branch commit
→ CI validation
→ draft pull request
→ merge observation or rollbackRun a bounded maintenance worker
import {
PostgresMaintenanceCaseStore,
SelfMaintainingApiRuntime,
SelfMaintainingApiWorker,
} from "@lssm-tech/module.workspace/maintenance";
const store = new PostgresMaintenanceCaseStore({ database, tenantId });
const runtime = new SelfMaintainingApiRuntime({
store,
normalizer,
usageAnalyzer,
codemods,
policy,
repository,
validation,
clock,
});
const worker = new SelfMaintainingApiWorker({ runtime, store });
await worker.runOnce({ tenantId, workerId, limit: 25 });Safety boundaries
Trusted discovery is host-owned
Consumers must provide authenticated, immutable source discovery. Never fetch arbitrary URLs or accept mutable changelog content as a trusted revision.
Parser and analyzer limits stay visible
Unsupported languages, stale semantic indexes, or insufficient parser coverage must stop or require review. Do not silently fall back to unsafe lexical rewrites.
Never auto-merge
The runtime may prepare a draft PR after approval and validation. Merge authority remains with the consumer's repository governance.
Repairs require new approval
Any diagnostic repair that changes the patch or plan digest invalidates the previous approval and returns to review.
Durable agent runtime
Run durable memory, encrypted storage, continuous loops, schedulers, workers, retries, cancellation, and dead-letter handling.
Deploy agent systems
Choose replaceable Vercel, Railway, Supabase, Docker, or custom-provider topologies and assign infrastructure responsibilities.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.