ContractSpecContractSpec

Start with OSS

Back to changelog index

1.0.7

Aug 05, 2026 · 14 packages · 52 unique changes · 27 release entries

appsbundlesintegrationslibsmodules

This release affects the contracts, integrations, sharedLibs, solutions familyies.

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

Release summaries

  • company-intelligence-brain-runtime

    Add immutable evidence-backed Company Brain editions, lifecycle, projections, gaps, remediation, and bounded compiled artifacts.

    integrator

    Brain editions and projections are now immutable, deterministic, permission-aware, bounded, and durable.

  • company-intelligence-canonical-contracts

    Add canonical tenant-scoped Company Intelligence records with semantic validation, canonical serialization, versioned SHA-256 fingerprints, and additive operation/event contracts.

    maintainer

    CompanyOS gains one canonical, provider-free record vocabulary for lineage, evidence, knowledge, graph, editions, grounding, learning, promotion, rollback, and replay. Stable semantic validator codes and canonical fingerprints guard durable boundaries.

    integrator

    Adopt the additive company-intelligence subpaths and operation registry keys. Existing graph, evidence, replay, approval, execution, outcome, and learning identities remain unchanged.

    agent

    Treat knowledge as evidence only. Policy, proposal, approval, execution, and outcome are distinct authority classes; grounded answers cannot authorize action and promotions require independent evaluation, policy, approval, rollback, and kill-switch refs.

  • company-intelligence-durable-graph

    Add deterministic bitemporal graph integrity, bounded query, replay and reviewed identity lineage.

    integrator

    Graph replay and identity decisions are now deterministic, bounded, tenant-safe and durable.

  • company-intelligence-governed-learning

    Add append-only governed learning with 25 stable gates, deterministic rollback and replay, and existing-table FORCE-RLS persistence.

    integrator

    Adopt the additive marker-gated lifecycle and pure decision API without changing legacy record, operation, event, fingerprint, or persistence identities.

    maintainer

    Persist lifecycle transitions only through the existing canonical Company Intelligence repository with lifecycle CAS, exact replay, and constrained-role FORCE RLS.

  • company-intelligence-grounded-retrieval

    Add bounded authorization-first grounded retrieval with deterministic redacted citations, independent claim verification, and exact replay receipts.

    integrator

    Adopt the additive grounding contracts and caller-owned ports without changing legacy query, retriever, access, runtime, operation, event, or status identities.

    maintainer

    Authorization preflight, post-retrieval scope validation, viewer redaction, server-minted citations, strict drafting, independent verification, one repair, and deterministic replay now form one fail-closed package boundary.

  • company-intelligence-structured-extraction

    Add schema-constrained evidence-linked structured extraction, trusted review gates, redacted deterministic receipts, immutable corrections, and PostgreSQL qualification.

    integrator

    Untrusted model output now crosses a strict candidate schema and can reach canon only through trusted evidence resolution and deterministic review policy.

  • 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-bitemporal-assertions

    Add neutral bitemporal assertion contracts and fixtures.

    integrator

    Consumers can model valid time, known time, contradictions, and supersession without persistence or destructive merge semantics.

  • 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-foundation-p1-p2-public-compatibility

    Expose additive CompanyOS Foundation contracts through fingerprinted public entrypoints.

    integrator

    Consumers can compose tenant governance, temporal-store, and provider-observation surfaces without deep imports.

  • companyos-gtm-p0-conformance-hardening

    Harden the reusable CompanyOS P0 governance, temporal, communication-ingestion, and provider contracts.

    integrator

    Consumers gain target-bound learned-rule activation, storage-neutral temporal queries, normalized consent/redaction ingestion fixtures, and extensible provider capability identifiers without deep imports or real provider execution.

  • companyos-gtm-p1p2-decision-execution

    Add governed, deterministic P1/P2 decision and zero-effect execution-preparation contracts.

    integrator

    Vertical repositories can consume deterministic provider decisions, governed learning projections, approval-bound communication scheduling, and CRM dry runs without deep imports or external effects.

  • companyos-gtm-platform-public-compatibility

    Declare the neutral GTM platform compatibility surface for packed consumers.

    integrator

    External consumers can use declared, fingerprinted contracts without deep imports.

  • companyos-layer0-public-exports

    Document sponsor-neutral Layer 0 CompanyOS contracts and runtime helpers while tightening stable reason codes, order-stable replay governance refs, review-gated routing, and export accountability invariants.

    maintainer

    Layer 0 remains sponsor-neutral and additive over existing CompanyOS authority, policy, evidence, and execution primitives; active routing rules must be reviewed before use.

    integrator

    Import Layer 0 packet/routing contracts from companyos-spec and deterministic policy, routing, and replay helpers from companyos-runtime; policy summaries now include stable reason-code constants and replay summaries expose order-stable governance ref ids.

  • companyos-outcome-value-projections

    Add CompanyOS projections for evidence-backed outcome value reports.

    maintainer

    CompanyOS now owns business value projection contracts over ContractSpec OutcomeClaim refs without redefining the generic claim kernel.

    integrator

    Integrations can project evidence-backed outcome claims into business value reports, review queues, readiness signals, sales reports, and prompt/skill influence summaries.

    agent

    Agents must provide evidence-backed claim refs; no-evidence claims are excluded from CompanyOS value reporting.

  • 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-signed-ingress-reference

    Add a tenant-safe signed webhook and API ingress reference runtime for CompanyOS fixtures.

    integrator

    Consumers can verify fixture HMAC ingress, reject replay, and exercise outbox retry and dead-letter behavior without provider listeners, credentials, or network integration.

  • 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

  • Qualify immutable Company Brain runtime

    assisted

    Apply additive migration 0026 and run pure, repository, and PostgreSQL proofs.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime, @lssm-tech/app.api-application-monolith

    1. Apply additive API migration 0026 before writing Brain object versions.
    2. Run both exact S7 acceptance commands.
    3. Run the managed PostgreSQL 15 proof under constrained runtime roles.

  • Adopt canonical Company Intelligence record packets

    assisted

    Validate and fingerprint immutable records before persistence or API transport while keeping legacy adapters until downstream cutover evidence is complete.

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

    1. Import record schemas from @lssm-tech/lib.companyos-spec/types/company-intelligence.
    2. Build fingerprints with company-intelligence-sha256:v1 over canonical-json:v1 content.
    3. Reject non-empty semantic validation results before persistence, retrieval, or promotion.
    4. Preserve existing operation identities and add adapters only at approved runtime/app edges.

  • Qualify durable graph and identity

    assisted

    Run pure graph, repository and constrained PostgreSQL proofs.

    Packages: @lssm-tech/lib.companyos-runtime, @lssm-tech/app.api-application-monolith

    1. Apply additive API migration 0025 before writing graph projections or identity decisions.
    2. Run both exact S6 acceptance commands.
    3. Run the disposable PostgreSQL 15 proof.

  • Qualify caller adoption of governed learning

    assisted

    Run the exact golden, unsafe, replay, package, and PostgreSQL acceptance before adoption.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.evolution, @lssm-tech/app.api-application-monolith

    1. Treat canary as a signed deterministic receipt only, never live activation.
    2. Keep providers, credentials, HTTP routes, UI, external export, and live tenants outside S9.
    3. Roll back by removing caller adoption; no schema or data migration rollback is required.

  • Qualify caller-owned grounded retrieval adapters

    assisted

    Bind only authorized runtime channels and independent providers, then run the deterministic golden, adversarial, and replay acceptance commands before production composition.

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

    1. Keep provider credentials, persistence, application routes, and action dispatch outside these packages.
    2. Reject fixture provenance in production mode and preserve zero-call denied/empty preflight behavior.
    3. Treat grounded knowledge as evidence only; it never authorizes action.
    4. Roll back by removing caller adoption of the additive subpaths; no migration, provider, app, or persistence rollback is required.

  • Qualify trusted extraction and receipt persistence

    assisted

    Run the pure runtime suite and disposable PostgreSQL proof.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime, @lssm-tech/app.api-application-monolith

    1. Apply additive API migration 0024 before persisting extraction receipt details.
    2. Run the exact Company Intelligence extraction command.
    3. Run the disposable PostgreSQL proof with PostgreSQL 15.

  • 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.

  • 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.

  • Adopt the additive Foundation entrypoints

    manual

    Replace source deep imports with the documented package subpaths.

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

    1. Import tenant governance contracts, fixtures, and validation from their companyos-spec subpaths.
    2. Import the temporal reference fake from companyos-runtime/temporal-store.
    3. Import provider observations and aggregation from provider-spec public subpaths.

  • Supply explicit activation authorization refs

    manual

    Learned-rule activation now fails closed unless the policy request, action packet, work item, and routing-rule target are explicitly bound.

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

    1. Add activationAuthorization to governed learning-loop envelopes that may promote a rule.
    2. Reference an action packet already present in actionPacketRefs and the exact routing-rule candidate.
    3. Provide the referenced policy-gate request to the runtime projection.

  • Adopt the additive P1/P2 public entrypoints

    manual

    Replace local/deep implementations with the documented deterministic package subpaths.

    Packages: @lssm-tech/lib.companyos-spec, @lssm-tech/lib.companyos-runtime, @lssm-tech/lib.provider-spec, @lssm-tech/lib.communication-spec, @lssm-tech/integration.communication-os-runtime, @lssm-tech/lib.contracts-integrations

    1. Import provider metering and shadow selection from provider-spec; selectors never dispatch.
    2. Import sequence intent from communication-spec and the pure scheduler from communication-os-runtime.
    3. Import CRM proposal/dry-run from contracts-integrations; no mutation method is included.
    4. Keep learned rules as candidates until the existing ActionPacket, ApprovalDecision, DecisionLog, policy, and replay gates approve promotion.

  • Adopt the declared public entrypoints

    manual

    Replace source deep imports with documented public subpaths.

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

    1. Replace any source deep imports with the documented public subpaths.

  • Review Layer 0 routing rules before activation

    manual

    Active Layer 0 routing rules with reviewRequired still true are rejected by schema and refused by runtime matching.

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

    1. Set reviewRequired to false only after the scoped or global rule has completed human review.
    2. Include actor and evidence refs when transitioning Layer 0 packets to exported.

  • Project outcome claims into business value reports

    assisted

    Use CompanyOS runtime helpers to derive value reports and review queues from ContractSpec outcome claim refs.

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

    1. Import CompanyOS projection contracts from `@lssm-tech/lib.companyos-spec/types/outcome-value`.
    2. Use `projectBusinessValueReport` from `@lssm-tech/lib.companyos-runtime/outcome-value-projections`.
    3. Keep provider calls, persistence, and production side effects outside these projection helpers.

  • 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.

  • Compose the fixture ingress runtime at an adapter boundary

    auto

    Inject tenant-scoped secret resolution, F002 authorization evidence, and a delivery callback into the reference runtime.

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

    1. Import the additive `@lssm-tech/lib.companyos-runtime/ingress` entrypoint.
    2. Keep raw secrets in the injected resolver and bind authorization decisions to the signed tenant, workspace, actor, and governance refs.
    3. Replace the in-memory fixture stores with deployment-owned adapters before production use.

  • 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.

  • 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.

  • 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 `[]`.

  • 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.

Unique release changes

  • - Add governed, deterministic P1/P2 decision and zero-effect execution-preparation contracts.

    6 packages · 6 occurrences

  • - Replace local/deep implementations with the documented deterministic package subpaths.

    6 packages · 6 occurrences

  • - 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

  • - Declare the neutral GTM platform compatibility surface for packed consumers.

    4 packages · 4 occurrences

  • - Harden the reusable CompanyOS P0 governance, temporal, communication-ingestion, and provider contracts.

    4 packages · 4 occurrences

  • - Learned-rule activation now fails closed unless the policy request, action packet, work item, and routing-rule target are explicitly bound.

    4 packages · 4 occurrences

  • - Replace source deep imports with documented public subpaths.

    4 packages · 4 occurrences

  • - Add append-only governed learning with 25 stable gates, deterministic rollback and replay, and existing-table FORCE-RLS persistence.

    3 packages · 3 occurrences

  • - Add CompanyOS projections for evidence-backed outcome value reports.

    3 packages · 3 occurrences

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

    3 packages · 3 occurrences

  • - Add immutable evidence-backed Company Brain editions, lifecycle, projections, gaps, remediation, and bounded compiled artifacts.

    3 packages · 3 occurrences

  • - Add schema-constrained evidence-linked structured extraction, trusted review gates, redacted deterministic receipts, immutable corrections, and PostgreSQL qualification.

    3 packages · 3 occurrences

  • - Apply additive migration 0026 and run pure, repository, and PostgreSQL proofs.

    3 packages · 3 occurrences

  • - Expose additive CompanyOS Foundation contracts through fingerprinted public entrypoints.

    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

  • - Replace source deep imports with the documented package subpaths.

    3 packages · 3 occurrences

  • - Run the exact golden, unsafe, replay, package, and PostgreSQL acceptance before adoption.

    3 packages · 3 occurrences

  • - Run the pure runtime suite and disposable PostgreSQL proof.

    3 packages · 3 occurrences

  • - Use CompanyOS runtime helpers to derive value reports and review queues from ContractSpec outcome claim refs.

    3 packages · 3 occurrences

  • - Active Layer 0 routing rules with reviewRequired still true are rejected by schema and refused by runtime matching.

    2 packages · 2 occurrences

  • - Add bounded authorization-first grounded retrieval with deterministic redacted citations, independent claim verification, and exact replay receipts.

    2 packages · 2 occurrences

  • - Add canonical tenant-scoped Company Intelligence records with semantic validation, canonical serialization, versioned SHA-256 fingerprints, and additive operation/event contracts.

    2 packages · 2 occurrences

  • - Add deterministic bitemporal graph integrity, bounded query, replay and reviewed identity lineage.

    2 packages · 2 occurrences

  • - Bind only authorized runtime channels and independent providers, then run the deterministic golden, adversarial, and replay acceptance commands before production composition.

    2 packages · 2 occurrences

  • - Document sponsor-neutral Layer 0 CompanyOS contracts and runtime helpers while tightening stable reason codes, order-stable replay governance refs, review-gated routing, and export accountability invariants.

    2 packages · 2 occurrences

  • - Run pure graph, repository and constrained PostgreSQL proofs.

    2 packages · 2 occurrences

  • - Validate and fingerprint immutable records before persistence or API transport while keeping legacy adapters until downstream cutover evidence is complete.

    2 packages · 2 occurrences

  • - Add a tenant-safe signed webhook and API ingress reference runtime for CompanyOS fixtures.

    1 packages · 1 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 neutral bitemporal assertion contracts and fixtures.

    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

  • - Inject tenant-scoped secret resolution, F002 authorization evidence, and a delivery callback into the reference runtime.

    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.api-application-monolith

    Layer: apps · 2 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 4 changes

  • @lssm-tech/bundle.marketing

    Layer: bundles · 4 changes

  • @lssm-tech/integration.communication-os-runtime

    Layer: integrations · 2 changes

  • @lssm-tech/lib.communication-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.contracts-integrations

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.evolution

    Layer: libs · 2 changes

  • @lssm-tech/lib.knowledge

    Layer: libs · 2 changes

  • @lssm-tech/lib.provider-spec

    Layer: libs · 2 changes

  • @lssm-tech/module.companyos

    Layer: modules · 2 changes

  • @lssm-tech/module.examples

    Layer: modules · 4 changes