Builder specs
Builder control-plane contracts, capabilities, and validation for ContractSpec.
@lssm-tech/lib.builder-specpackages/domains/builder/spec
Core relationshipDeclares the ContractSpec core package directly.
Inspected package consumers11 packages declare this specification in the reviewed inventory.
CONNECTED ACROSS LSSM
From this specification to the systems around it.
Select an entry to explore its neighbours. Move between ownership, specifications, areas, products, data and infrastructure without leaving this page.
9 entries · 27 recorded relationships
Arrow keys navigate entries. Enter selects. Alt + arrows rearranges. F fits the view; Shift + F fits the selection. + and − zoom. Shift + F10 opens actions.
Accessible entry list (9)
- Products & experiences
- Shared foundations
- Inspected sources
- Toolchain & agents
- Specialized specifications
- Specialized specifications
- Specialized specifications
- Specialized specifications
- Specialized specifications
Architecture lineage
- ContractSpec ↗Specialized contracts within ContractSpecContractSpec → Builder specs
The architecture specializes ContractSpec for this contract surface. Exact direct, indirect or absent package dependencies are recorded separately.
Dependencies between specifications
- ContractSpec ↗Declared package dependencyContractSpec → Builder specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- LSSM OS specs ↗Declared package dependencyLSSM OS specs → Builder specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- Orchestration specs ↗Declared package dependencyOrchestration specs → Builder specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- Provider routing specs ↗Declared package dependencyProvider routing specs → Builder specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
- CompanyOS specs ↗Declared package dependencyBuilder specs → CompanyOS specs
The consumer manifest declares this dependency in dependencies. Presence in a manifest is distinct from a tested runtime import or live deployment.
Connected systems and service roles
- Builder & product delivery ↗Source-mapped contract scopeBuilder specs → Builder & product delivery
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
- ContractSpec Studio ↗Source-mapped contract scopeBuilder specs → ContractSpec Studio
Pinned package purpose and reviewed source map associate this contract surface with the target. This relationship is not a manifest dependency or proof of product runtime adoption.
Source and package context
- ContractSpec repository ↗Pinned specification package sourceBuilder specs → ContractSpec repository
Exact package manifest and README evidence at the retained source commit.
Groups connected through this specification
- Company & owner assistance ↗Specialized contracts in this group’s contextCompany & owner assistance → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Company decisions & learning ↗Specialized contracts in this group’s contextCompany decisions & learning → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Contracts & application foundations ↗Specialized contracts in this group’s contextContracts & application foundations → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Product discovery & decisions ↗Specialized contracts in this group’s contextProduct discovery & decisions → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Planning & delivery ↗Specialized contracts in this group’s contextPlanning & delivery → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Feedback & outcome checks ↗Specialized contracts in this group’s contextFeedback & outcome checks → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Product work & delivery ↗Specialized contracts in this group’s contextProduct work & delivery → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
- Product feedback & learning ↗Specialized contracts in this group’s contextProduct feedback & learning → Builder specs
Derived through explicit member products, selected capabilities or their recorded source paths. The source edge chain preserves implemented, proposed and editorial scopes; the group link adds navigation, not runtime integration.
Packages that declare this dependency.
These package manifests explicitly name this specification. Their runtime and deployment status remain separate.
- @lssm-tech/bundle.product-intent ↗
packages/bundles/product-intentComposes product-intent reasoning, evidence retrieval and an AI runner around provider-neutral core services for product definition and delivery preparation.
- @lssm-tech/bundle.workspace ↗
packages/bundles/workspaceOwns ContractSpec's reusable CLI/editor service composition for workspace discovery, validation, code generation, graph/drift inspection, setup and release workflows, plus guarded maintenance adapters and Connect host hooks.
- @lssm-tech/module.lssm-os-control-plane ↗
packages/domains/builder/control-planeTenant-safe application services and scheduling for the LSSM OS control plane.
- @lssm-tech/module.mobile-review ↗
packages/domains/builder/mobile-reviewReusable mobile-first Builder review surfaces.
- @lssm-tech/module.builder-workbench ↗
packages/domains/builder/moduleReusable Builder workbench UI module.
- @lssm-tech/module.product-intent-core ↗
packages/domains/builder/product-intent-coreCore product intent orchestration and adapters
- @lssm-tech/lib.product-intent-utils ↗
packages/domains/builder/product-intent-utilsPrompt builders and validators for product-intent workflows.
- @lssm-tech/lib.builder-runtime ↗
packages/domains/builder/runtimeBackend-neutral Builder runtime, ingestion, fusion, readiness, and replay services.
- @lssm-tech/lib.companyos-spec ↗
packages/domains/company/specContract-first CompanyOS V0/V1 specifications for bounded company operations.
- @lssm-tech/lib.mobile-control ↗
packages/platform/agents/mobile-controlBuilder mobile-control primitives for review cards, parity, and deep-link-safe actions.
- @lssm-tech/lib.contracts-spec ↗
packages/platform/delivery/contracts-spec-compatCompatibility facade forwarding original ContractSpec contracts and registries to canonical owners.
Inspect the specification.
Typed control-plane, plan, readiness and preview contracts reference Connect decisions without owning execution or authorization. Builder plans, authors and prepares evidence through explicit boundaries. Connect authority, durable stores, provider execution and deployment qualification remain distinct.
Open the package in the complete inventory ↗