@lssm/lib.infra-ops-spec

Provider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.

This package closes the Phase 2 infra-ops gap as a contract/evidence layer. It does not deploy services, page humans, resolve secrets, run migrations, or call provider APIs.

Public entrypoints

• @lssm/lib.infra-ops-spec — root barrel
• @lssm/lib.infra-ops-spec/types — schemas and TypeScript types
• @lssm/lib.infra-ops-spec/fixtures — canonical deployment and incident fixtures
• @lssm/lib.infra-ops-spec/validation — semantic validation helpers
• @lssm/lib.infra-ops-spec/intent-types — additive V2 infrastructure-intent schemas and types
• @lssm/lib.infra-ops-spec/intent-fixtures — canonical provider-neutral V2 fixture
• @lssm/lib.infra-ops-spec/intent-validation — V2 reference, waiver, policy, decision, and leakage validation

Contract families

The package models:

• environments, runtime targets, and services;
• deployments, releases, migration windows, rollbacks, and pipelines;
• health/readiness/liveness checks, SLOs, monitors, and alerts;
• incidents, on-call ownership, escalation, mitigation, and postmortems;
• capacity plans, cost budgets, secret refs, operational risks, approvals, and evidence receipts.

Boundary

Adjacent systems are referenced through branded refs only:

• progressive delivery rollout/rollback refs;
• observability metric/trace/log refs;
• job schedule refs;
• integration capability refs;
• CompanyOS policy/owner refs;
• orchestration workflow refs;
• cost budget and metering usage refs.

No provider SDKs, credentials, live provider config, network calls, deployment runners, incident automation, queues, or secret resolution are included.

Infrastructure intent V2

V2 is additive: every V1 entrypoint and schema remains supported unchanged. The new contract graph captures operational goals and requirements, quantified workload envelopes, restrictions and provider policy, logical capabilities, bindings, evolution triggers, scoped expiring waivers, architecture candidates, Pareto comparisons, ADRs, implementation-neutral plans, handoff evidence, and unsatisfiable-requirement reports.

Candidate comparison first rejects candidates with hard violations. It then computes a deterministic Pareto frontier across cost, reliability, performance, scalability, portability, complexity, and migration risk; IDs provide stable ordering but never override the multi-objective frontier. Waiver inheritance is tightening-only: a child cannot broaden scope, change the waived restriction, or outlive its parent. Provider policy can mark restrictions non-waivable.

validateInfrastructureIntentV2 performs strict schema and semantic validation. canonicalizeInfrastructureIntent and digestInfrastructureIntent provide a stable JSON projection and SHA-256 binding for review and handoff receipts. These contracts contain target classes and redacted references only—never provider credentials, SDK configuration, resolved secrets, or execution behavior.