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.
Spec pack
Builder is a governed authoring control plane, not a frontier coding agent.
Builder composes
@lssm-tech/lib.builder-spec
,@lssm-tech/lib.builder-runtime
, execution lanes, provider integrations, Connect, CLI/tmux, workbench, and mobile review into one durable run/evidence model.Production runs
Use the codex-opencode-go production profile, durable run folders, readiness reports, provider receipts, and workbench summaries instead of one-off chat transcripts.
Canonical lanes
Persist execution as canonical lane keys such as team.coordinated and complete.persistent. Shorthands like ultrawork, ulw, and ralphone stay sourceAlias metadata only.
Diagnostics and precision tools
Treat LSP, AST-Grep, prebuild checks, background-agent status, tmux, cancel, attach, and workbench JSON output as evidence surfaces that cannot bypass Connect review.
Current Builder loop
Bootstrap managed, local-daemon, or hybrid presets explicitly instead of inventing provider posture ad hoc per host.
Treat specs packs as governed execution inputs: import, analyze, plan, and keep apply blocked until Connect evidence exists.
Compile goals into plan packs, execution lanes, provider profiles, and runtime targets with durable receipts.
Route risky writes, AST rewrite plans, workspace renames, and protected-path edits through Connect before applying them.
Keep background agents scoped by leases, write scopes, lifecycle state, cancellation evidence, and verifier signoff.
Project the same run state into CLI JSON, tmux/workbench status, mobile review, and release evidence.
Dry-run before live providers
The pending Builder release capsules are additive, but they make the production profile, alias semantics, diagnostics, and background-agent evidence public workflow surfaces. Verify deterministic dry-runs before turning on live Codex, opencode-go, tmux attach, or provider checks.
For runtime modes, workspace config, mobile review, and host wiring, use the Host Builder workbench guide.
contractspec builder doctor --json
contractspec builder run "<goal>" --dry-run --skip-provider-checks --run-id builder-smoke --json
contractspec builder status --run-id builder-smoke --json
bun test packages/apps/cli-contractspec/src/commands/builder/index.test.ts packages/apps/cli-contractspec/src/commands/execution-lanes/behavior.blackbox.test.ts
bun test packages/libs/builder-spec/src packages/libs/builder-runtime/src packages/libs/execution-lanes/srcContractSpec Connect
Guard coding-agent edits and shell actions with task-scoped context, plan packets, patch verdicts, and review packets.
Contract types
Choose the right contract surface for the behavior you want to make explicit.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.