Back to changelog index

0.5.7

May 26, 2026 · 7 packages · 25 unique changes · 13 release entries

appsbundleslibsmodules

This release affects the sharedLibs, solutions familyies.

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

Release summaries

  • companyos-ai-os-operating-graph

    Add CompanyOS-owned operating graph contracts, runtime projections, Knowledge refs, and deterministic sandbox AI OS proofs.

    maintainer

    Maintainers get a CompanyOS-owned Company Brain / AI OS graph closure path without introducing a separate Company Brain package.

    integrator

    Integrators can compose Knowledge source refs, permission decisions, realtime replay, and runbook readiness through deterministic CompanyOS contracts before adding caller-owned live adapters.

    agent

    Agents get four safe deterministic sandbox proofs that emit replayable evidence for generic platform, EngineeringOS, support-to-product, and Incident Brain loops.

  • companyos-communicationos-example-suite

    Align CompanyOS and CommunicationOS example-suite release guidance, registry expectations, and deterministic rich Operating Cockpit boundaries.

    maintainer

    Maintainers get a release checklist for module-owned reusable UI, focused examples, combined TemplateShell cockpit proof, rich interactions, and registry updates.

    integrator

    Integrators can adopt the example suite with deterministic fixtures first and add provider adapters only through explicit non-default seams.

    agent

    Agents should keep combined examples free of example-to-example imports and regenerate the examples registry when public discovery metadata changes.

  • companyos-dispatch-authorization

    Add CompanyOS dispatch authorization and replay substrate contracts.

    maintainer

    CompanyOS now has additive dispatch authorization, source evidence, policy replay, operator route, outcome linkage, replay determinism, and authorization failure contracts.

    integrator

    Integrators can distinguish AIP and command-inbox provenance from actual dispatch authority before wiring production adapters.

    customer

    CompanyOS dispatches gain clearer approval, replay, and outcome evidence before production-impacting work can run.

  • companyos-execution-contracts

    Add additive CompanyOS execution and evidence contracts.

    maintainer

    CompanyOS now has contract-first execution lifecycle, claim/lease, idempotency, policy-gate, dispatch, receipt, checkpoint, replay, and outcome descriptors.

    integrator

    Future CompanyOS runtimes and modules can consume typed execution evidence without treating agents, jobs, or provider integrations as the canonical work state.

    customer

    CompanyOS gains safer foundations for bounded autonomous work by requiring explicit policy, approval, dispatch, and receipt evidence.

  • companyos-runtime-execution-projections

    Add pure CompanyOS execution projection helpers.

    maintainer

    CompanyOS runtime now projects execution readiness, dispatch drafts, policy-gate summaries, receipt summaries, and execution inbox items without side effects.

    integrator

    Integrations can inspect whether CompanyOS work is blocked, approval-required, dispatch-ready, or receipt-pending before handing off to provider adapters.

    agent

    Agents get deterministic projections for policy-gated execution without permission to execute provider work directly.

  • companyos-v0-runtime

    Add pure CompanyOS V0/V1 runtime helpers for deterministic authority, autonomy, inbox, review, operating-loop, agent, memory, objective, and surface projections.

    maintainer

    CompanyOS V0/V1 reusable behavior now lives in a backend-neutral runtime lib instead of examples, modules, providers, or apps.

    integrator

    Integrators can classify autonomy, explain authority, route inbox approvals, summarize reviews, and project V1 objectives, memory, cadence packets, handoffs, operation access, and surfaces without importing modules or provider bindings.

  • companyos-v0-spec

    Add the initial CompanyOS V0 contract package for bounded company operations.

    maintainer

    CompanyOS V0 now has a dedicated contract package, keeping company operating primitives out of the foundational contracts-spec surface.

    integrator

    Integrators can model one deterministic product/customer/engineering loop with explicit authority, autonomy, connector capabilities, operator inbox, and operating review contracts.

  • companyos-v1-operating-loop

    Add CompanyOS V1 operating-loop contracts for objective-aware, cadence-driven, bounded-agent review flows.

    maintainer

    CompanyOS V1 deepens the existing spec package without creating modules, apps, provider bindings, or executable agents.

    integrator

    Integrators can model objective-aware reviews, temporal memory snapshots, cadence inputs/outputs, bounded agent roles, agent-native descriptors, and adaptive surface descriptors.

  • managed-companyos-contract-inventory

    Add the Managed CompanyOS contract inventory release capsule for additive public managed tenant, workflow, runtime health, and evidence surfaces.

    maintainer

    Maintainers get compatibility classification for managed tenant, integration ownership, workflow, WebSocket, degraded-health, replay, and evidence receipt surfaces.

    integrator

    Integrators can consume additive provider-neutral contracts while retaining fail-closed degraded-state and redaction semantics.

    agent

    Agents can map app/API/worker route and event claims back to the managed CompanyOS inventory and ContractSpec evidence packets.

  • voiceops-gaps-g01-companyos-spec

    Add additive VoiceOps action-origin, governed-action lifecycle, evidence receipt, and fixture contracts to companyos-spec.

    maintainer

    CompanyOS spec gains additive VoiceOps contracts for origin-aware governed actions, lifecycle states, by-reference evidence receipt material, and deterministic voice/messaging fixtures.

  • voiceops-gaps-g02-companyos-runtime

    Add additive origin redaction, lifecycle, and lifecycle replay projections to companyos-runtime.

    maintainer

    CompanyOS runtime now projects origin-aware lifecycle state and replay views from companyos-spec without changing execution behavior.

  • voiceops-outcome-linkage-cadence

    Extend CompanyOS outcome linkage with optional review-output-plan cross-link (cadence half of the VoiceOps outcome-linkage gap-fill).

    maintainer

    `CompanyOsOutcomeLinkageSchema` now accepts an optional `reviewOutputPlanIds: string[]` field (defaulted to `[]`). Existing outcome linkages parse unchanged. The new field lets outcomes cross-link back to the `OperatingReviewOutputPlan` that proposed the action, completing the objectives + cadence cross-link surface called out in `specs/companyos_voiceops_specs_pack/03_contractspec_oss_prompts/01_companyos_contracts_prompt.md`.

    integrator

    Consumers that build outcome linkages programmatically can now populate `reviewOutputPlanIds` to attribute the outcome to a specific operating-cadence review cycle. Field is optional; omitting it preserves prior behaviour.

  • voiceops-support-to-product-fixtures

    Add deterministic CompanyOS VoiceOps support-to-product and quote-approval fixtures adapted from the approved hackathon ingest candidate set.

    maintainer

    Add deterministic CompanyOS VoiceOps support-to-product and quote-approval fixtures adapted from the approved hackathon ingest candidate set.

    integrator

    Add deterministic CompanyOS VoiceOps support-to-product and quote-approval fixtures adapted from the approved hackathon ingest candidate set.

Migration guide

  • Keep reusable CompanyOS UI in the module

    Use `@lssm-tech/module.companyos/ui` for reusable CompanyOS view models and screens; keep example UI as deterministic adapters.

    1. Promote reusable CompanyOS UI and view-model contracts to @lssm-tech/module.companyos/ui before examples consume them.
    2. Keep @lssm-tech/example.companyos-product-engineering-loop focused on replay/proof and fixture-backed adapters.
  • Regenerate example registry for public discovery changes

    Registry metadata must be rebuilt when example exports or preview discovery links change.

    1. Run `bun run --cwd packages/modules/examples generate:registry` after adding or changing public ./example, ./docs, ./ui, presentation, or preview metadata.
    2. Keep catalog root imports metadata-only and avoid direct @lssm-tech/example.* imports.

Upgrade steps

  • Review Voiceops Support To Product Fixtures adoption

    manual

    Add deterministic CompanyOS VoiceOps support-to-product and quote-approval fixtures adapted from the approved hackathon ingest candidate set.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime

    1. Review the paired changeset summary and update consumers only if they use the affected package surface.
  • Cross-link outcomes to operating-cadence review plans

    auto

    When constructing `CompanyOsOutcomeLinkage` values, populate `reviewOutputPlanIds` with the IDs of `OperatingReviewOutputPlan` records that proposed the action.

    Packages: @lssm-tech/lib.companyos-spec

    1. Import `CompanyOsOutcomeLinkageSchema` from `@lssm-tech/lib.companyos-spec`.
    2. Where the outcome ties back to a cadence review (e.g. an action proposal surfaced by a weekly review), include `reviewOutputPlanIds: [reviewOutputPlan.id]` in the linkage payload.
    3. Existing callers do not need to change; the field defaults to `[]`.
  • Use CompanyOS graph contracts before live adapters

    assisted

    Import CompanyOS operating graph contracts/runtime helpers and keep Knowledge, auth, realtime, and provider systems behind explicit refs or caller-owned adapters.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime, @lssm-tech/lib.knowledge, @lssm-tech/example.companyos-ai-os-proofs

    1. Do not create a separate Company Brain package for these semantics.
    2. Keep examples and default proofs on deterministic fixtures and sandbox adapters.
    3. Treat restricted source data through ACL refs and redaction evidence before graph/action use.
  • Adopt the Operating Cockpit suite with deterministic fixtures first

    assisted

    Start from the focused examples and combined cockpit proof before wiring live providers.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/module.companyos, @lssm-tech/example.companyos-product-engineering-loop, @lssm-tech/example.communication-os, @lssm-tech/example.companyos-communicationos-operating-cockpit, @lssm-tech/module.examples, @lssm-tech/bundle.marketing, @lssm-tech/app.web-landing

    1. Use the CompanyOS focused example for replay and policy-gated work proof.
    2. Use the CommunicationOS focused example for conversation-to-work fixtures and proof.
    3. Use the combined TemplateShell Operating Cockpit example to verify home/dashboard navigation, CommunicationOS evidence mapping into CompanyOS work/autonomy, dry-run execution, reset, and return to CommunicationOS audit/action status.
    4. Validate starter-kit navigation with the additive @lssm-tech/lib.companyos-spec operating-cockpit screen contract.
    5. Add provider adapters only behind explicit typed ports; do not make them the default path.
  • Review additive Managed CompanyOS public-surface inventory

    assisted

    Confirm downstream code treats the managed surfaces as additive and provider-neutral by default.

    Packages: @lssm-tech/lib.companyos-spec

    1. Preserve redacted credential refs in schemas, fixtures, replay packets, WebSocket messages, and evidence receipts.
    2. Keep green API health from hiding worker, WebSocket, replay, or evidence degradation.
    3. Run ContractSpec Connect gates before future public-surface widening.
  • Require explicit dispatch authorization evidence

    assisted

    Use the new authorization and replay contracts to bind policy decisions, source evidence, operator routing, and outcomes before non-dry-run dispatch.

    Packages: @lssm-tech/lib.companyos-spec

    1. Treat AIP and command-inbox records as `CompanyOsSourceEvidenceRefSchema` provenance only.
    2. Require `CompanyOsExecutionDispatchAuthorizationSchema` before module or runtime dispatch adapters execute non-dry-run work.
    3. Persist `CompanyOsPolicyReplayPacketSchema` and `CompanyOsReplayDeterminismCaseSchema` evidence for deterministic replay.
  • Model CompanyOS execution evidence before runtime dispatch

    assisted

    Use the new execution contracts to describe work execution plans, gates, dispatches, receipts, and outcomes while keeping provider execution outside the spec layer.

    Packages: @lssm-tech/lib.companyos-spec

    1. Add execution plans for CompanyOS work items that may be dispatched later.
    2. Attach claims, leases, idempotency keys, policy-gate envelopes, and receipts.
    3. Keep actual provider or agent execution in runtime/module adapter layers.
  • Project execution readiness before dispatch

    assisted

    Use the new execution helpers to derive readiness, dispatch drafts, policy summaries, receipts, and inbox items over CompanyOS execution contracts.

    Packages: @lssm-tech/lib.companyos-runtime

    1. Import helpers from `@lssm-tech/lib.companyos-runtime/execution`.
    2. Keep provider, queue, agent, or human side effects outside the runtime package.
    3. Treat approval-required and reserved-human-only projections as operator-facing gates.
  • Use pure runtime helpers for deterministic CompanyOS replay

    manual

    Import helpers from `@lssm-tech/lib.companyos-runtime` after modeling contracts with `@lssm-tech/lib.companyos-spec`.

    Packages: @lssm-tech/lib.companyos-runtime

    1. Keep real providers, storage, UI, modules, and integrations outside this package.
    2. Treat authority explanations as deterministic projections, not authentication enforcement.
    3. Require approval or reserved-human-only handling for unsafe autonomy decisions.
  • Model CompanyOS V0 loops through the spec package

    manual

    Use the contract-only CompanyOS package before adding runtime, module, app, or provider bindings.

    Packages: @lssm-tech/lib.companyos-spec

    1. Import schemas and types from `@lssm-tech/lib.companyos-spec/types`.
    2. Validate deterministic V0 fixtures with `@lssm-tech/lib.companyos-spec/validation`.
    3. Keep provider bindings outside the CompanyOS contract package.
  • Extend V0 loops with V1 operating review contracts

    manual

    Use `CompanyOsV1OperatingLoopSchema` for objective-aware, cadence-driven, bounded-agent operating review fixtures.

    Packages: @lssm-tech/lib.companyos-spec

    1. Import V1 schemas and types from `@lssm-tech/lib.companyos-spec/types` or the dedicated V1 subpaths.
    2. Validate V1 fixtures with `validateCompanyOsV1OperatingLoop` or `assertCompanyOsV1OperatingLoop`.
    3. Keep provider writes, UI rendering, modules, and MCP execution out of this contract-only surface.

Unique release changes

  • - Align CompanyOS and CommunicationOS example-suite release guidance, registry expectations, and deterministic rich Operating Cockpit boundaries.

    5 packages · 5 occurrences

  • - Registry metadata must be rebuilt when example exports or preview discovery links change.

    5 packages · 5 occurrences

  • - Start from the focused examples and combined cockpit proof before wiring live providers.

    5 packages · 5 occurrences

  • - Use `@lssm-tech/module.companyos/ui` for reusable CompanyOS view models and screens; keep example UI as deterministic adapters.

    5 packages · 5 occurrences

  • - Add deterministic CompanyOS VoiceOps support-to-product and quote-approval fixtures adapted from the approved hackathon ingest candidate set.

    2 packages · 4 occurrences

  • - Add CompanyOS-owned operating graph contracts, runtime projections, Knowledge refs, and deterministic sandbox AI OS proofs.

    3 packages · 3 occurrences

  • - Import CompanyOS operating graph contracts/runtime helpers and keep Knowledge, auth, realtime, and provider systems behind explicit refs or caller-owned adapters.

    3 packages · 3 occurrences

  • - Add additive CompanyOS execution and evidence contracts.

    1 packages · 1 occurrences

  • - Add additive origin redaction, lifecycle, and lifecycle replay projections to companyos-runtime.

    1 packages · 1 occurrences

  • - Add additive VoiceOps action-origin, governed-action lifecycle, evidence receipt, and fixture contracts to companyos-spec.

    1 packages · 1 occurrences

  • - Add CompanyOS dispatch authorization and replay substrate contracts.

    1 packages · 1 occurrences

  • - Add CompanyOS V1 operating-loop contracts for objective-aware, cadence-driven, bounded-agent review flows.

    1 packages · 1 occurrences

  • - Add pure CompanyOS execution projection helpers.

    1 packages · 1 occurrences

  • - Add pure CompanyOS V0/V1 runtime helpers for deterministic authority, autonomy, inbox, review, operating-loop, agent, memory, objective, and surface projections.

    1 packages · 1 occurrences

  • - Add the initial CompanyOS V0 contract package for bounded company operations.

    1 packages · 1 occurrences

  • - Add the Managed CompanyOS contract inventory release capsule for additive public managed tenant, workflow, runtime health, and evidence surfaces.

    1 packages · 1 occurrences

  • - Confirm downstream code treats the managed surfaces as additive and provider-neutral by default.

    1 packages · 1 occurrences

  • - Extend CompanyOS outcome linkage with optional review-output-plan cross-link (cadence half of the VoiceOps outcome-linkage gap-fill).

    1 packages · 1 occurrences

  • - Import helpers from `@lssm-tech/lib.companyos-runtime` after modeling contracts with `@lssm-tech/lib.companyos-spec`.

    1 packages · 1 occurrences

  • - Use `CompanyOsV1OperatingLoopSchema` for objective-aware, cadence-driven, bounded-agent operating review fixtures.

    1 packages · 1 occurrences

  • - Use the contract-only CompanyOS package before adding runtime, module, app, or provider bindings.

    1 packages · 1 occurrences

  • - Use the new authorization and replay contracts to bind policy decisions, source evidence, operator routing, and outcomes before non-dry-run dispatch.

    1 packages · 1 occurrences

  • - Use the new execution contracts to describe work execution plans, gates, dispatches, receipts, and outcomes while keeping provider execution outside the spec layer.

    1 packages · 1 occurrences

  • - Use the new execution helpers to derive readiness, dispatch drafts, policy summaries, receipts, and inbox items over CompanyOS execution contracts.

    1 packages · 1 occurrences

  • - When constructing `CompanyOsOutcomeLinkage` values, populate `reviewOutputPlanIds` with the IDs of `OperatingReviewOutputPlan` records that proposed the action.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.web-landing

    Layer: apps · 4 changes

  • @lssm-tech/bundle.marketing

    Layer: bundles · 4 changes

  • @lssm-tech/lib.companyos-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.companyos-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.knowledge

    Layer: libs · 2 changes

  • @lssm-tech/module.companyos

    Layer: modules · 4 changes

  • @lssm-tech/module.examples

    Layer: modules · 4 changes