Back to changelog index

3.13.16

Aug 01, 2026 · 5 packages · 11 unique changes · 7 release entries

appsbundles

This release affects the solutions family.

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

Release summaries

  • category-defining-positioning

    Reframe ContractSpec and Managed CompanyOS public positioning into a category-defining two-front story.

    maintainer

    Public docs, landing copy, LLMS summaries, and managed landing guardrails now distinguish the open ContractSpec substrate from the managed CompanyOS application.

    integrator

    ContractSpec remains the open technical substrate; Managed CompanyOS is an invite-led managed application and should not be treated as included in the OSS package surface.

  • companyos-expert-mission-control

    Add Expert Network Mission Control as a reusable CompanyOS starter workflow and expose a Workflow Fit Audit path for self-qualifying governed workflow templates.

    customer

    CompanyOS now presents expert-led mission control as a repeatable starter workflow with intake, expert crew registry, decision packets, weekly command cycles, evidence replay, ROI leverage, and a product-led pricing ladder instead of bespoke agency positioning.

    maintainer

    The public site adds a Workflow Fit Audit checklist that scores opportunity follow-up, invoice approval, expert mission control, or bring-your-own workflows without adding a backend, credentials, or production workflow execution.

  • companyos-gtm-learning-loop

    Position CompanyOS as the horizontal governed-workflow platform and add GTM Learning Loop as its first visible specialized workflow.

    customer

    CompanyOS now presents its horizontal governed-workflow capabilities and links GTM Learning Loop to its dedicated GTM site as the first visible specialized workflow.

    maintainer

    Marketing contracts, localized content, navigation, metadata, SEO, and discovery surfaces preserve routes while adding the non-breaking CompanyOS and GTM positioning.

  • companyos-public-domain-migration

    Move CompanyOS public website and GTM discovery surfaces to the new companyos.run domains.

    customer

    CompanyOS website links now use the www.companyos.run domain and GTM links use the gtm.companyos.run domain.

  • full-docs-markdown-coverage

    Serve substantive markdown for every static web-landing docs route registered through the API markdown endpoint.

    maintainer

    Static web-landing docs routes now have markdown overrides when the presentation registry would otherwise fall back to placeholder coverage.

    integrator

    `/mdx/docs/**` consumers receive substantive route markdown for docs pages such as the Drizzle database guide.

    customer

    AI and markdown readers can load full docs pages instead of placeholder links back to the interactive site.

  • mobile-expo-landing-companion

    Add a shared marketing content/navigation surface and convert the Expo demo into a native public-nav companion for the ContractSpec OSS-first story.

    maintainer

    Marketing now exposes React-free landing story, page, navigation, and CTA data through `@lssm-tech/bundle.marketing/content`, and the Expo demo consumes that content through mobile-native components and ContractSpec handlers.

    integrator

    Integrators can import shared ContractSpec landing copy, public navigation, page content, and CTA metadata from `@lssm-tech/bundle.marketing/content` without pulling web-only React components into native shells.

    customer

    The Expo demo now presents native Home, Product, Templates, Pricing, Docs, and Changelog companion routes instead of the previous task-list demo.

  • web-monolith-marketing-i18n

    Preserve active marketing locale across web monolith navigation and page content rendering.

    customer

    CompanyOS marketing pages keep the selected language when visitors navigate between pages.

    integrator

    The marketing bundle now exposes an i18n subpath consumed by the web monolith's combined locale runtime.

Upgrade steps

  • Review public copy for substrate vs managed application boundaries

    manual

    Keep README, marketing landing, managed landing, package READMEs, and `/llms*` summaries aligned around the two-front story.

    Packages: @lssm-tech/bundle.marketing, @lssm-tech/app.web-landing, @lssm-tech/bundle.managed-companyos, @lssm-tech/app.web-application-monolith

    1. Use ContractSpec for the open contract-first substrate and Managed CompanyOS for the invite-led operating application.
    2. Do not add managed pricing, formal compliance claims, or OSS-includes-managed-product claims without a new approval artifact.
  • Prefer `/mdx/docs/**` for agent-readable docs context

    auto

    Existing markdown URLs continue to work and now return substantive markdown for static docs pages.

    Packages: @lssm-tech/bundle.marketing, @lssm-tech/app.api-library

    1. Keep using existing `/mdx/docs/**` URLs.
    2. Refresh cached markdown if an agent previously stored placeholder-only docs output.
  • Prefer the platform-neutral content export for native or non-web shells

    assisted

    Use `@lssm-tech/bundle.marketing/content` when a shell needs landing story, navigation, or public page data without importing web components.

    Packages: @lssm-tech/bundle.marketing

    1. Import `contractspecLandingStory`, `contractspecPublicNavigation`, or `contractspecLandingPages` from `@lssm-tech/bundle.marketing/content`.
    2. Map the exported `iconKey` strings to platform-specific icon components.
    3. Resolve CTA targets with `resolveContractspecLandingCtaUrl` when opening links outside the web app.
  • Use the marketing i18n subpath for app-level runtime composition

    auto

    Import `createMarketingI18n` from `@lssm-tech/bundle.marketing/i18n` when composing marketing keys into an application locale provider.

    Packages: @lssm-tech/app.web-application-monolith, @lssm-tech/bundle.marketing

    1. Ensure application bundlers can resolve the package export.

Unique release changes

  • - Keep README, marketing landing, managed landing, package READMEs, and `/llms*` summaries aligned around the two-front story.

    4 packages · 4 occurrences

  • - Reframe ContractSpec and Managed CompanyOS public positioning into a category-defining two-front story.

    4 packages · 4 occurrences

  • - Move CompanyOS public website and GTM discovery surfaces to the new companyos.run domains.

    3 packages · 3 occurrences

  • - Add Expert Network Mission Control as a reusable CompanyOS starter workflow and expose a Workflow Fit Audit path for self-qualifying governed workflow templates.

    2 packages · 2 occurrences

  • - Existing markdown URLs continue to work and now return substantive markdown for static docs pages.

    2 packages · 2 occurrences

  • - Import `createMarketingI18n` from `@lssm-tech/bundle.marketing/i18n` when composing marketing keys into an application locale provider.

    2 packages · 2 occurrences

  • - Position CompanyOS as the horizontal governed-workflow platform and add GTM Learning Loop as its first visible specialized workflow.

    2 packages · 2 occurrences

  • - Preserve active marketing locale across web monolith navigation and page content rendering.

    2 packages · 2 occurrences

  • - Serve substantive markdown for every static web-landing docs route registered through the API markdown endpoint.

    2 packages · 2 occurrences

  • - Add a shared marketing content/navigation surface and convert the Expo demo into a native public-nav companion for the ContractSpec OSS-first story.

    1 packages · 1 occurrences

  • - Use `@lssm-tech/bundle.marketing/content` when a shell needs landing story, navigation, or public page data without importing web components.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.api-library

    Layer: apps · 2 changes

  • @lssm-tech/app.web-application-monolith

    Layer: apps · 2 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 1 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 2 changes

  • @lssm-tech/bundle.marketing

    Layer: bundles · 2 changes