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

Builder guide

Builder Intelligence keeps indexing, memory, and routing reviewable.

Use

builder index

,

builder memory

,

builder context

, and

builder route

as typed dry-run surfaces for the next Builder architecture: deterministic graph refs first, hybrid retrieval later, and SONA-lite learning only through reviewed artifacts.

PR1 CLI surface

These commands emit JSON contracts for operators and tests. They are non-mutating in PR1, so hosts can integrate the shape before durable stores, embeddings, GraphRAG summaries, or adaptive policy writes exist.

builder-intelligence
contractspec builder index build --json
contractspec builder index query --json
contractspec builder memory inspect --json
contractspec builder memory consolidate --json
contractspec builder learn from-trajectory --json
contractspec builder context build --goal "repair contract drift" --json
contractspec builder route explain --json

Artifact layout

  • generated/contractspec/graphs

  • generated/contractspec/index

  • generated/contractspec/memory

  • generated/contractspec/trajectories

  • generated/contractspec/drift

  • generated/contractspec/generation

Safety contract

  • Contract Graph, Codebase Graph, and Contract-Code Link Graph refs remain authoritative; embeddings only widen recall later.

  • PR1/Phase 2 commands are dry-run JSON surfaces and do not write index stores, memories, policy mutations, vectors, or generated files.

  • Memory, trajectories, and ReasoningBank-style strategy cards store observable summaries and evidence refs, not raw hidden reasoning.

  • SONA-lite route proposals, GraphRAG summaries, and neural readiness gates remain review-only and rollbackable.

Contract surface

  • BuilderIndexManifestV1 and BuilderChunkV1 for stable chunks, source hashes, Merkle roots, and generated layout refs.

  • BuilderContextPacketV1 for exact lookup, graph neighborhood expansion, symbol matching, sparse scoring, stale filtering, reranking, and context packing explanations.

  • BuilderMemoryItemV1, BuilderTrajectoryV1, ReasoningPatternV1, BuilderRoutingPolicyV1, and StaleMemoryReportV1 for reviewed memory and SONA-lite proposals.

Phase 1/2 runtime helpers

buildBuilderIndex()

and

queryBuilderIndex()

live in

@lssm-tech/lib.builder-runtime/builder-intelligence

. They are pure in-memory helpers: callers provide refs and source summaries, and the helpers return manifests, chunks, matches, and context packets without writing generated files or treating vector scores as authority. Phase 2 adds pure memory projection, stale reports, consolidation proposals, and observable trajectory capture; later helpers add draft strategy cards, route explanations, graph summaries, and neural readiness gates.

Builder specs packs

Contracts and codebase graph

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

Handle Builder specs packs

Analyze zip or folder specs packs, derive governed task ledgers, and keep apply fail-closed until Connect evidence exists.

Next

Use Connect in a repo

Enable Connect in workspace config, verify agent actions, and inspect local review and replay artifacts.

Why ContractSpec

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

ManifestoContract-first APISpec-driven development