@lssm-tech/lib.assurance-spec
Provider-neutral assurance and compliance evidence correlation contracts for autonomous-company actions.
This package closes the P1 assurance gap as a correlation-only contract/evidence layer. It does not store audit events, query logs, run anomaly detection, execute providers, evaluate policy, or replace ContractSpec Connect.
Public entrypoints
@lssm-tech/lib.assurance-spec@lssm-tech/lib.assurance-spec/types@lssm-tech/lib.assurance-spec/fixtures@lssm-tech/lib.assurance-spec/validation@lssm-tech/lib.assurance-spec/quality and its environment, plan,
primitives, profile, and receipt leaves own the canonical quality models.
Quality models retain the existing V1 schema versions, digests, DocBlocks and receipt binding checks. Historical @lssm-tech/lib.contracts-spec/quality
imports forward to these same definitions. Supplied-receipt validation checks exact plan, delivery, Git SHA, check and Connect decision bindings; it does not execute checks or grant authority. Quality planning, readiness probes and execution remain in @lssm-tech/lib.execution-lanes/quality.
The quality models use the pure LSSM OS delivery primitive leaf, existing Core documentation and serialization helpers, crypto utilities and Zod. This package has no dependency on the compatibility facade or execution runtime.
Límite
The canonical prebuild keeps all 12 public entrypoints and their conditional targets. The committed export maps use the generator's ordering so repeated prebuilds preserve the manifest bytes.
Adjacent systems are referenced through branded refs only: audit events, observability telemetry/anomalies, ai-agent model/tool/session receipts, integration calls, CompanyOS work/policy decisions, Connect reviews, orchestration workflows, and infra-ops deployment/incident refs.
Portable Connect and Harness contracts
@lssm-tech/lib.assurance-spec/connect/types owns the unchanged Connect verdict and review threshold declarations. Connect retains policy evaluation, approvals, and runtime authority.
@lssm-tech/lib.assurance-spec/harness/types owns the unchanged Harness evidence, scenario, suite, target, and execution declarations and the identity declaration factories. It does not execute a harness. The supported Legacy paths forward these declarations. The nominal Harness registry classes retain their existing Legacy implementation and superclass identity until the coordinated runtime ownership cut.
Experience coverage scoring and validation are available at /experience-coverage/scoring and /experience-coverage/validation. They correlate supplied evidence without authorizing execution. Legacy imports forward to these canonical functions.
