ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

0.5.8

May 25, 2026 · 1 packages · 5 unique changes · 3 release entries

modules

This release affects the solutions family.

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

Release summaries

  • module-companyos-executor

    Introduce the CompanyOS execution composition module.

    maintainer

    A new CompanyOS module composes spec/runtime execution contracts with typed adapter ports and fake adapters.

    integrator

    Applications can provide agent, job, integration, human, dry-run, or manual-record adapters while CompanyOS preserves policy-gate verdicts.

    agent

    Agents can use fake adapters in tests and must supply explicit ports for real execution lanes.

  • module-companyos-flagship-fixture

    Add a replayable CompanyOS source-evidence-to-outcome proof fixture.

    maintainer

    The CompanyOS module now exports a flagship fixture linking communication-style evidence to work, policy gate, dispatch, receipt, and outcome refs.

    integrator

    External agents can use the fixture as a planning smoke proof for source evidence through CompanyOS execution outcomes.

    agent

    Spec-pack agents can replay the fixture without importing CommunicationOS, BillingOS, or other sibling modules.

  • voiceops-gaps-g04-modules-companyos

    Add additive governed-action view-state and lifecycle-view exports to module.companyos.

    integrator

    CompanyOS module consumers can import new product-facing governed-action and lifecycle view-state surfaces composed from companyos-runtime projections.

Upgrade steps

  • Execute CompanyOS plans through explicit adapters

    assisted

    Compose CompanyOS work execution with caller-provided lane adapters instead of importing sibling modules or providers.

    Packages: @lssm-tech/module.companyos

    1. Import `executeCompanyOsWorkPlan` from `@lssm-tech/module.companyos/executor`.
    2. Register only the lane adapters your application owns.
    3. Preserve operator action for approval-required, denied, or reserved-human-only plans.

  • Use the flagship fixture as a cross-domain smoke proof

    assisted

    Validate source-evidence-to-outcome flows against `companyOsFlagshipExecutionProof` before adding provider-specific adapters.

    Packages: @lssm-tech/module.companyos

    1. Import `companyOsFlagshipExecutionProof` from `@lssm-tech/module.companyos/flagship-fixture`.
    2. Confirm the trace covers source evidence, work item, policy gate, dispatch, receipt, outcome, objective, memory, and cadence refs.
    3. Keep sibling module integrations optional and adapter-owned.

Unique release changes

  • - Add a replayable CompanyOS source-evidence-to-outcome proof fixture.

    1 packages · 1 occurrences

  • - Add additive governed-action view-state and lifecycle-view exports to module.companyos.

    1 packages · 1 occurrences

  • - Compose CompanyOS work execution with caller-provided lane adapters instead of importing sibling modules or providers.

    1 packages · 1 occurrences

  • - Introduce the CompanyOS execution composition module.

    1 packages · 1 occurrences

  • - Validate source-evidence-to-outcome flows against `companyOsFlagshipExecutionProof` before adding provider-specific adapters.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/module.companyos

    Layer: modules · 2 changes