Area guide · 45 packages · Trace a desired-state plan
Delivery, infrastructure and runtime operations
Connect source intent, governed plans and provider execution through exact revisions, receipts and recoverable operational state.
What are you trying to do?
- What does LSSM OS planning own and what does a provider execute?
- How are source changes admitted before mutation?
- Which evidence supports deployment or recovery?
Why start with these packages
Suggested entry point
@lssm-tech/lib.lssm-os-specInspect canonical delivery, runtime and execution contract families.
Suggested entry point
@lssm-tech/lib.lssm-os-runtimeUse deterministic planning/execution, authorization verification and injected runtime-node ports.
Suggested entry point
@lssm-tech/lib.infra-ops-specStart with infrastructure intent, deployment, incident and evidence contracts.
Suggested entry point
@lssm-tech/lib.builder-runtimeInspect source ingestion, readiness, planning and governed patch boundaries.
Practical steps
Step 01
Inspect one plan and its dependencies
Follow the selected source/desired revision, observed state, target, costs and evidence into the plan digest. Identify which unknowns require review and which provider capabilities the plan expects.
Step 02
Trace the execution receipt
Locate authority verification, lease/attempt binding, provider dispatch, receipt append/read-back and completion. Review interrupted and ambiguous cases before claiming repeatability or recovery for a particular adapter.
Step 03
Qualify the intended channel
Use the owning delivery plan and tests for the exact runtime/provider/state combination. Keep source support, local conformance, clean package consumption and deployed operation as distinct evidence when documenting availability or an upgrade path.
Start with desired and observed state
LSSMOSRuntime compiles desired and observed revisions into canonical plans and binds them to digests. It verifies current Connect authorization before idempotent execution under fenced leases. Drift, reconciliation, rollback, decommission and replay have explicit surfaces. Plan cost records distinguish exact, ranged, stale and unavailable information; uncertain cost can add an economic review requirement. Start by inspecting the inputs and resulting plan, so a reviewer can tell precisely what would change and what evidence is missing.
Keep contracts, execution and providers connected
InfraOpsSpec models environments, targets, services, deployments, incidents, readiness, budgets and evidence references. It supplies contracts and validation, while concrete infrastructure effects remain with provider integrations. RuntimeNode execution similarly receives dispatch authority, operation state, provider receipts, router and clock ports. An exact receipt replay and a new provider effect have different paths. Select the actual state backend and provider adapter for the host rather than inferring a deployment capability from the existence of an infrastructure operation.
Admit source mutations deliberately
BuilderRuntime supports ingestion, deterministic extraction/chunking, readiness, planning and replay. Its governed patch path validates repository-relative edits against approved scope; the workspace adapter must still enforce filesystem isolation, symlink and preimage checks. Trusted authority enters separately from untrusted request payloads. This creates a useful review sequence: inspect source context, proposed changes, admitted paths, quality evidence and permission, then execute through the selected host boundary. Generated plans and previews remain reviewable artifacts until that boundary runs.
Follow a practical path.
Inspect one plan and its dependencies
Follow the selected source/desired revision, observed state, target, costs and evidence into the plan digest. Identify which unknowns require review and which provider capabilities the plan expects.
Trace the execution receipt
Locate authority verification, lease/attempt binding, provider dispatch, receipt append/read-back and completion. Review interrupted and ambiguous cases before claiming repeatability or recovery for a particular adapter.
Qualify the intended channel
Use the owning delivery plan and tests for the exact runtime/provider/state combination. Keep source support, local conformance, clean package consumption and deployed operation as distinct evidence when documenting availability or an upgrade path.
Packages in this area (45)
45 of 45 shown
- Open manual →
GitHub Action for running ContractSpec CI checks
- Open manual →
GitHub Action for ContractSpec version management
- Open manual →
GitHub Action for ContractSpec drift detection
- Open manual →
GitHub Action for ContractSpec PR checks
- Open manual →
Lifecycle management bundle with analytics and AI advisor
- Open manual →
Product intent bundle with AI runner and evidence retriever
- Open manual →
Qualified Redis and Valkey cache, coordination, and SQL-authoritative stream acceleration for LSSM OS.
- Open manual →
Authenticated MQTT publication normalization into the LSSM OS durable inbox.
- Open manual →
Browser, Bun, and Node client for canonical LSSM OS durable-operation status.
- Open manual →
Docker Compose provider execution adapter for LSSM OS.
- Open manual →
Scoped Cloud Run transport for governed LSSM OS hosting lifecycle composition.
- Open manual →
GitHub provider execution adapter for LSSM OS.
- Open manual →
Runtime Node provider lifecycle adapter for Neon.
- Open manual →
Railway provider adapter for governed LSSM OS infrastructure execution.
- Open manual →
Runtime Node provider lifecycle adapter for Resend.
- Open manual →
Supabase provider execution adapter for LSSM OS.
- Open manual →
Vercel provider adapter for governed LSSM OS infrastructure execution.
- Open manual →
SQL-authoritative GCP Pub/Sub and Cloud Tasks wake transports for LSSM OS.
- Open manual →
SQL-authoritative RabbitMQ wake-up transport for LSSM OS durable queues.
- Open manual →
SQL-authoritative SQS wake-up transport for LSSM OS durable queues.
- Open manual →
Atomic Git-tracked desired state and immutable LSSM OS receipts.
- Open manual →
Multi-node tenant-scoped Postgres and Supabase state adapters for LSSM OS.
- Open manual →
Transactional single-node SQLite and PGlite state adapters for LSSM OS.
- Open manual →
Runtime integration with secret management
- Open manual →
Hybrid runtime compatibility wrapper for Builder.
- Open manual →
Local runtime compatibility wrapper for Builder.
- Open manual →
Managed runtime compatibility wrapper for Builder.
- Open manual →
Pure, deterministic runtime audit engine for mobile app submission readiness (ReviewReady). No network calls; integrations feed it snapshots to audit.
- Open manual →
Backend-neutral Builder runtime, ingestion, fusion, readiness, and replay services.
Inspect source ingestion, readiness, planning and governed patch boundaries.
- Open manual →
Builder control-plane contracts, capabilities, and validation for ContractSpec.
- Open manual →
AI-powered contract evolution engine
- Open manual →
Provider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.
Start with infrastructure intent, deployment, incident and evidence contracts.
- Open manual →
Contract lifecycle management primitives
- Open manual →
Provider-neutral qualification contracts and runner for LSSM OS execution adapters.
- Open manual →
Deterministic, provider-neutral planning and execution kernel for LSSM OS.
Use deterministic planning/execution, authorization verification and injected runtime-node ports.
- Open manual →
Canonical, provider-neutral context and goal contracts for LSSM OS.
Inspect canonical delivery, runtime and execution contract families.
- Open manual →
Prompt builders and validators for product-intent workflows.
- Open manual →
Progressive-delivery contracts and runtime controls for safe staged rollouts.
- Open manual →
ReviewReady module: runtime-driven app-submission readiness report, rejection assistant, and admin rule surfaces built from real audit output.
- Open manual →
Reusable Builder workbench UI module.
- Open manual →
AI-powered lifecycle recommendations and guidance
- Open manual →
Core lifecycle stage definitions and transitions
- Open manual →
Tenant-safe application services and scheduling for the LSSM OS control plane.
- Open manual →
Reusable mobile-first Builder review surfaces.
- Open manual →
Core product intent orchestration and adapters
Curated but no longer in the workspace: app.contractspec-ci-controller
What connects to this area
Governance and approvals
Execution uses authority bound to the exact work and current context.
Observability and testing
Operational claims need source- and environment-bound evidence.
Integrations and providers
Concrete cloud, queue, state and ingress adapters implement supplied ports.
App composition
The selected host connects these capabilities into an actual product.