Skip to content
ContractSpec
Start here

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-spec

Inspect canonical delivery, runtime and execution contract families.

Read package manual →

Suggested entry point

@lssm-tech/lib.lssm-os-runtime

Use deterministic planning/execution, authorization verification and injected runtime-node ports.

Read package manual →

Suggested entry point

@lssm-tech/lib.infra-ops-spec

Start with infrastructure intent, deployment, incident and evidence contracts.

Read package manual →

Suggested entry point

@lssm-tech/lib.builder-runtime

Inspect source ingestion, readiness, planning and governed patch boundaries.

Read package manual →

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

Curated but no longer in the workspace: app.contractspec-ci-controller