ContractSpecContractSpec

Start with OSS

Back to changelog index

11.1.0

Jun 01, 2026 · 1 packages · 2 unique changes · 1 release entry

libs

This release affects the contracts family.

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

Release summaries

  • special-ops-review-decide-weekly-approve-contracts

    Add two additive Managed CompanyOS Special Ops operation contracts — specialOps.reviewCard.decide and specialOps.weeklyReport.approve — on the canonical production contracts surface to retroactively govern the already-shipped decideReviewCard and publishWeeklyReport handlers in api-application-monolith. The example special-ops-cockpit package stays a pure fixture demo.

    maintainer

    Two new defineCommand contracts live under packages/libs/contracts-spec/src/companyos/commands (reviewCardDecide.command.ts, weeklyReportApprove.command.ts), exported via the commands barrel and registered in companyOsOperationRegistry under keys specialOps.reviewCard.decide and specialOps.weeklyReport.approve. Each carries a same-file DocBlock (kind reference, visibility internal) linked via meta.docId and declares sideEffects.audit for the intended managed_companyos_audit_events emission.

    integrator

    The change is additive — new operation keys only; no existing contract, registry key, or schema changes. Special Ops handlers in api-application-monolith are now governed by production contracts. The example package (packages/examples/special-ops-cockpit) remains an unchanged, network/DB-free fixture demo.

Upgrade steps

  • Resolve Special Ops decide/approve handlers through the production registry

    manual

    Lane handlers should resolve the two new operations through companyOsOperationRegistry rather than reaching into individual files.

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

    1. Import ReviewCardDecideCommand and WeeklyReportApproveCommand from @lssm-tech/lib.contracts-spec (companyos commands barrel) or look them up in companyOsOperationRegistry by key (specialOps.reviewCard.decide, specialOps.weeklyReport.approve) when wiring REST/Elysia handlers.
    2. Do not add these production-shaped contracts to packages/examples/special-ops-cockpit; that package must stay a pure fixture demo.

Unique release changes

  • - Add two additive Managed CompanyOS Special Ops operation contracts — specialOps.reviewCard.decide and specialOps.weeklyReport.approve — on the canonical production contracts surface to retroactively govern the already-shipped decideReviewCard and publishWeeklyReport handlers in api-application-monolith. The example special-ops-cockpit package stays a pure fixture demo.

    1 packages · 1 occurrences

  • - Lane handlers should resolve the two new operations through companyOsOperationRegistry rather than reaching into individual files.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 2 changes