0.2.19

Jul 16, 2026 · 10 packages · 13 unique changes · 6 release entries

libs

This release affects the sharedLibs family.

Run contractspec connect adoption resolve --family sharedLibs to see how it impacts your project.

Release summaries

assurance-policy-runtime
Add assurance correlation contracts and CompanyOS policy-runtime hardening.
maintainer
Assurance-spec adds provider-neutral evidence correlation contracts while CompanyOS gains additive policy-runtime contracts and pure projections.
integrator
Integrators can correlate audit, observability, agent, integration, CompanyOS, Connect, orchestration, and infra refs without importing runtime/storage/provider packages.
agent
Agents can validate assurance packets and fail-closed CompanyOS policy readiness before proposing autonomous execution.
crypto-wallet-agent-payment-protocols-closure
Add the first canonical crypto wallet and agent payment protocol contract slice.
maintainer
A new contract-only package models wallet policy, HTTP payment challenges, agent authorizations, settlement evidence refs, and safety validation.
integrator
Runtime and provider adapters can depend on a stable contract envelope before adding wallet, x402, facilitator, or settlement execution.
agent
Agent payment plans now have explicit authority, finance approval, assurance, audit, replay, and idempotency requirements before any payment runtime acts.
growth-finance-ops-specs
Add canonical growth and finance-ops contract packages.
maintainer
Two additive contract-only packages close the P2 marketing/growth and finance-ops gaps while preserving analytics, personalization, BillingOS, CompanyOS, assurance, and integration boundaries.
integrator
Integrators can reference campaign/publishing and finance-ops handoff packets without provider credentials or runtime execution.
agent
Agents can validate consent, brand review, spend approval, authority, assurance evidence, and no-provider-execution constraints before proposing growth or finance actions.
infra-ops-spec
Add provider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.
maintainer
A new infra-ops-spec package models environments, services, deployment/release/rollback/migration, health, SLO, incident, on-call, capacity, cost, secret refs, approvals, and evidence receipts without provider automation.
integrator
Integrators can reference progressive delivery, observability, jobs, integrations, CompanyOS, orchestration, cost, and metering surfaces through branded refs while keeping provider adapters host-owned.
agent
Agents can use deployment/release and incident fixtures plus validation rules to draft infra spec packs without leaking secrets or provider config.
opportunity-engine-first-slice
Add the first canonical Autonomous Company Opportunity Engine spec/runtime slice for evidence-graded scoring, gates, simulation, and portfolio ranking.
maintainer
Maintainers now have additive provider-neutral opportunity contracts, public validation-rule primitives, and pure deterministic runtime projections, with module/provider/live-research execution explicitly deferred.
integrator
Integrators can score, gate, validate, simulate, and rank autonomous-company candidates using explicit evidence levels and handoff refs without triggering provider actions.
customer
Opportunity recommendations can now be explained through reviewable evidence, gates, and portfolio rationale instead of opaque startup ideation.
orchestration-spec
Add provider-neutral cross-domain orchestration semantics for autonomous-company workflows.
maintainer
A new orchestration-spec package binds existing workflow primitives to cross-domain refs, evidence links, policy gates, receipts, replay, checkpoint, and saga obligations.
integrator
Integrators can model CommunicationOS, CompanyOS, BillingOS, jobs, integrations, audit, and outcome evidence without adopting a provider runner.
agent
Agents can use the fixtures and validation rules to draft cross-domain spec packs while keeping infra-ops deferred.

Upgrade steps

Correlate autonomous action evidence before execution
assisted
Use assurance-spec packets plus CompanyOS policy-runtime projections to prove provenance, redaction, retention, compliance controls, approval, dry-run, and assurance coverage.
Packages: @lssm-tech/lib.assurance-spec, @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime
1. Keep audit storage, observability collection, agent execution, provider calls, and Connect governance in their existing packages.
2. Use branded refs for adjacent evidence surfaces.
3. Treat missing policy or assurance evidence as fail-closed.
Model crypto agent payments before adding runtime adapters
assisted
Use the crypto-payments-spec packet to review wallet policy, challenge, authorization, and settlement evidence refs before implementing wallet/provider execution.
Packages: @lssm-tech/lib.crypto-payments-spec
1. Validate wallet policy and challenge packets with @lssm-tech/lib.crypto-payments-spec.
2. Keep private keys, provider secrets, signing, custody, and on-chain transfer behavior in host/provider layers only.
3. Reference BillingOS, finance-ops, CompanyOS, assurance, audit, and replay artifacts instead of duplicating them.
Model growth operations as reviewable handoffs
assisted
Use growth-spec for consented audiences, campaigns, experiments, content/copy/SEO metadata, lifecycle messages, publish workflows, brand review, approvals, and evidence.
Packages: @lssm-tech/lib.growth-spec, @lssm-tech/lib.finance-ops-spec
1. Keep delivery, CMS publishing, CRM writes, ad buying, and social posting in host-owned provider adapters.
2. Use branded refs for analytics, personalization, communication, CompanyOS, assurance, and integrations.
Model internal finance operations beyond BillingOS
assisted
Use finance-ops-spec for budgets, spend policies, procurement, vendors, expenses, payroll/tax/accounting handoffs, cashflow, approvals, and evidence.
Packages: @lssm-tech/lib.growth-spec, @lssm-tech/lib.finance-ops-spec
1. Reference BillingOS artifacts by branded ref instead of redefining invoice/payment/refund/reconciliation primitives.
2. Keep bank, accounting, payroll, tax, and payment provider execution outside this contract package.
Model production-impacting operations as contracts and evidence
assisted
Use infra-ops-spec to model deployment, release, rollback, health, SLO, incident, on-call, capacity, cost, secret-ref, approval, and evidence obligations before host-owned execution.
Packages: @lssm-tech/lib.infra-ops-spec
1. Keep live deployment, pager, secret resolution, CI/CD, and provider execution outside the package.
2. Use branded refs for adjacent package surfaces instead of importing implementation packages.
3. Validate deployment/release and incident loops before treating generated plans as executable.
Model autonomous-company opportunity candidates with evidence-graded scorecards
manual
Use the new spec package for candidate, score, evidence, gate, validation, simulation, and portfolio contracts, then use the runtime package for deterministic projections.
Packages: @lssm-tech/lib.opportunity-spec, @lssm-tech/lib.opportunity-runtime
1. Create `OpportunityCandidate` packets with per-score and per-estimate evidence refs.
2. Run `validateOpportunityCandidate` before projecting scores.
3. Use runtime projections as decision evidence only; do not treat a high score as production approval.
Model cross-domain orchestration as workflow evidence bindings
assisted
Use orchestration-spec to bind existing workflow step IDs to domain refs, policy gates, dispatches, receipts, outcomes, and replay evidence.
Packages: @lssm-tech/lib.orchestration-spec
1. Keep generic graph/state/retry behavior in contracts-spec workflow primitives.
2. Use OrchestrationDomainRef and evidence links for cross-domain references.
3. Keep infra incident/deployment workflows deferred to the infra-ops spec.

Unique release changes

- Add assurance correlation contracts and CompanyOS policy-runtime hardening.
3 packages · 3 occurrences
- Use assurance-spec packets plus CompanyOS policy-runtime projections to prove provenance, redaction, retention, compliance controls, approval, dry-run, and assurance coverage.
3 packages · 3 occurrences
- Add canonical growth and finance-ops contract packages.
2 packages · 2 occurrences
- Add the first canonical Autonomous Company Opportunity Engine spec/runtime slice for evidence-graded scoring, gates, simulation, and portfolio ranking.
2 packages · 2 occurrences
- Use finance-ops-spec for budgets, spend policies, procurement, vendors, expenses, payroll/tax/accounting handoffs, cashflow, approvals, and evidence.
2 packages · 2 occurrences
- Use growth-spec for consented audiences, campaigns, experiments, content/copy/SEO metadata, lifecycle messages, publish workflows, brand review, approvals, and evidence.
2 packages · 2 occurrences
- Use the new spec package for candidate, score, evidence, gate, validation, simulation, and portfolio contracts, then use the runtime package for deterministic projections.
2 packages · 2 occurrences
- Add provider-neutral cross-domain orchestration semantics for autonomous-company workflows.
1 packages · 1 occurrences
- Add provider-neutral infrastructure operations contracts and evidence for autonomous-company deployment and incident loops.
1 packages · 1 occurrences
- Add the first canonical crypto wallet and agent payment protocol contract slice.
1 packages · 1 occurrences
- Use infra-ops-spec to model deployment, release, rollback, health, SLO, incident, on-call, capacity, cost, secret-ref, approval, and evidence obligations before host-owned execution.
1 packages · 1 occurrences
- Use orchestration-spec to bind existing workflow step IDs to domain refs, policy gates, dispatches, receipts, outcomes, and replay evidence.
1 packages · 1 occurrences
- Use the crypto-payments-spec packet to review wallet policy, challenge, authorization, and settlement evidence refs before implementing wallet/provider execution.
1 packages · 1 occurrences

Impacted packages

@lssm-tech/lib.assurance-spec
Layer: libs · 2 changes
@lssm-tech/lib.companyos-runtime
Layer: libs · 2 changes
@lssm-tech/lib.companyos-spec
Layer: libs · 2 changes
@lssm-tech/lib.crypto-payments-spec
Layer: libs · 2 changes
@lssm-tech/lib.finance-ops-spec
Layer: libs · 3 changes
@lssm-tech/lib.growth-spec
Layer: libs · 3 changes
@lssm-tech/lib.infra-ops-spec
Layer: libs · 2 changes
@lssm-tech/lib.opportunity-runtime
Layer: libs · 2 changes
@lssm-tech/lib.opportunity-spec
Layer: libs · 2 changes
@lssm-tech/lib.orchestration-spec
Layer: libs · 2 changes