Skip to content
← Back to changelog index

3.0.5

Nov 05, 2026 · 41 packages · 68 unique changes · 36 release entries

appsbundlesintegrationslibsmodulesBreaking changes

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

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

Release summaries

  • authos-product-admission

    Separate central organization session context and global identity roles from CompanyOS admission, personal provisioning and product authorization.

    integrator

    personal-context.ensure retains its v1 operation and input shape but refuses missing product admission with PRODUCT_ACCESS_REQUIRED (403).

    maintainer

    Central organization/team sessions use separate nullable columns. Existing product audit triggers, canonical grants and old session contexts remain intact.

  • builder-delivery-runtime-extraction

    Move existing draft Builder delivery services and generic host ports to their reusable lower owners with compatible workspace forwarding exports.

    integrator

    Adopt the BuilderRuntime builder-delivery entry without changing draft simulation behavior or host policy.

  • canonical-company-context-contracts

    Complete canonical CompanyOS and context contract ownership

    integrator

    Existing CompanyOS and context contracts forward to canonical owners without changing authority.

  • canonical-managed-company-semantics

    Preserve Managed CompanyOS semantics through canonical CompanySpec ownership

    integrator

    Historical CompanyOS imports resolve the same canonical operations, schemas and keyed maps; concrete host profiles retain existing bindings.

  • cmp-calendar-attendee-addresses

    Calendar readers keep attendee e-mail addresses under a documented purpose, retention, access and logging policy

    customer

    Shared pre-meeting briefs now propose named attendees as recipients, not only attendees whose calendar entry shows a bare address. You still review and can remove every recipient before anything is sent.

    integrator

    CalendarIntelligenceMeeting.attendees (contract 2.7.0) and GoogleCalendarIntelligenceEvent.attendees are optional { email, displayName? } lists beside the unchanged attendeeLabels. Treat them as personal data under COMPANYOS_CALENDAR_ATTENDEE_ADDRESS_POLICY: use them only for owner-reviewed follow-up recipients, keep them server-side, never send them to a model and pass free-text log fields through redactCalendarAttendeeAddresses. Readers that keep no addresses omit the field, so consumers must keep their label fallback.

  • cmp-company-bootstrap-cleanup

    Retire the Hirly bootstrap profile and collaborator phase behind a deprecation window; NDconsulting seeds become reference-only

    maintainer

    Bootstrap accepts only legacy-reference (local), core-workspaces and all; lssm-hirly is refused locally and live, and no collaborators:hirly phase is resolved or recorded. The NDconsulting special-ops seed and the G004 ND artifact validator are reference-only, and the seed requires an explicit tenant and workspace. The local E2E calendar seed covers only the live LSSM and CompanyOS workspaces. No migration: the 0038/0042 CHECK constraints still accept the retired literals so historical receipts stay valid.

    integrator

    Behavior-compatible: resolveOrganizationBootstrapPhases no longer returns collaborators:hirly, a phase no runner executes since the Hirly decommission. Type surfaces are unchanged. The lssm-hirly profile id, its slug/manifest entries, LSSM_HIRLY_OWNER_BINDINGS and the collaborators:hirly phase literal are deprecated and will be removed at the next major of @lssm-tech/lib.companyos-spec.

  • cmp-coverage-managed-composition

    Managed-ecosystem compositions for the CommunicationOS MCP gateway, CommunicationOS and Discord workers and the Marketing Operations shell

    integrator

    A managed CompanyOS host can launch the CommunicationOS MCP gateway with a CompanyOS host assertion (COMMOS_MCP_HOST_ASSERTION) plus an explicit COMMUNICATION_OS_HOST_MEMBERSHIPS tuple instead of a pre-minted access token. The gateway exchanges and verifies the assertion and fails closed (anonymous) on any mismatch. The managed session lasts 5 minutes from launch; relaunch with a fresh assertion. Launches without an assertion are unchanged.

    maintainer

    COMMUNICATION_OS_WORKER_HOSTING=lssm_managed and DISCORD_WORKER_HOSTING=lssm_managed start the existing worker compositions only when the managed binding is complete, and otherwise name the missing keys (never their values). Marketing Operations installations that declare deployment: 'managed' must publish an HTTPS, non-loopback public origin; an existing managed installation with an http:// or loopback origin now refuses to start. Self-hosted deployments are unchanged.

  • cmp-fix-w7-packed-spec-build-entries

    Emit existing published CompanyOS and provider-spec entrypoints and qualify packed Builder lazy resolution

    integrator

    Existing CompanyOS shared-brief, OPA home-mode and transcription-settings subpaths and the provider streaming-transcription catalog now include their advertised runtime artifacts. No contracts, export keys, model allowlists, dependencies or authorization semantics are added or changed.

    maintainer

    Run each package's scripts/check-built-exports.mjs after build to inspect reproducible local tarballs, every advertised target and built-byte parity. Packaged CLI smoke requires a local Builder command-pack tarball and checks actual installed help, in-memory approval reads and effect-free plan/complete dry runs with unavailable provider command fixtures. It never runs paid models.

  • communicationos-mcp-subject-resolver

    The CommunicationOS MCP gateway verifies a scoped access token at startup and acts for that subject until the token expires.

    integrator

    With COMMOS_MCP_ACCESS_TOKEN, COMMOS_MCP_TENANT_ID, COMMOS_MCP_WORKSPACE_ID, COMMOS_MCP_SPACE_ID and COMMUNICATION_OS_ACCESS_TOKEN_SECRET set, the stdio gateway runs every tool call as the token's principal ({ actor: 'user', userId, tenantId, workspaceId, roles }, plus policyContext.spaceId) until the token's exp. Without them, or when verification fails, calls stay anonymous and the MCP auth gate rejects them, as before. The provider diagnostics answer FORBIDDEN unless the input tenantId is the subject's tenant and the subject holds the admin role. The exported server singleton is no longer the instance startCommunicationOsMcpServer connects.

    maintainer

    The app now depends on @lssm-tech/integration.communication-os-host-auth. Verification uses the shared HS256 secret, so the gateway belongs inside the communicationos-api secret boundary. A client-distributed gateway would need a contract-first introspection route instead. Provider diagnostics bind through requireProviderSubject (provider-scope.ts), because the MCP tool ctx carries no policy decider and the MCP gate only checks for an authenticated actor.

  • company-canonical-lower-imports

    Consume canonical portable declarations and unchanged translation factories in CompanyOS composition.

    maintainer

    Existing imports and provider boundaries retain compatibility while internal canonical owners are used.

  • companyos-api-monolith-extraction-x2

    Managed CompanyOS host policy moves from the API monolith to companyos-spec and companyos-runtime

    integrator

    New explicit subpaths expose the server-side context authority model, context ref/projection/resolution, design-partner scope admission, readiness and approval workflow, personal-context lifecycle use cases, the Company Intelligence ingestion orchestrator and ports, source tombstone propagation, the briefing run, self-service organization and membership services with store ports, Company Intelligence graph persistence admission rules and the briefing email renderer that the managed CompanyOS API host previously kept locally.

  • companyos-authorization-hygiene

    Security fix. CompanyOS read routes now require their declared capability instead of a tenant match alone. Authority jsonb is stored as real JSON, and self-service joiners get a valid CompanyOS persona.

    integrator

    Security fix. CompanyOS status and read routes enforce the capability of the route (protectManagedCompanyOsAction, including role-bounded action ceilings), no longer a tenant match alone: workspace.read for health, workspace, workflow, integrations, providers, product surfaces and the workspace list; evidence.read for evidence; evidence.read plus replay.read for replay, Vercel replay evidence and snapshots; integration.configure for sync trigger and integration setup; special_ops.dashboard.read and special_ops.draft.write for Special Ops. GET /api/companyos/database has no declared capability and now answers 403 for every session. Callers that relied on tenant-only access (for example frontline_staff or ai_operator reading evidence) now receive 403. lib.companyos-spec adds SELF_SERVICE_JOINED_PERSONA (frontline_staff) and joinedPersona on the self-service composition (additive).

    maintainer

    postgres.js clients in the API install a pg-compatible json/jsonb serializer (withPgJsonSemantics), because postgres.js stored JSON.stringify output bound to jsonb parameters as a jsonb string. New postgres.js clients that bind jsonb parameters must install it (a source guard test enforces this).

    customer

    People who joined an organization through a verified domain or an approved access request can open CompanyOS, where they previously got an access error. Removing a capability from a role now also removes access to evidence and replay views on the next request.

  • companyos-authorization-hygiene-complete

    Security fix. The last CompanyOS routes that admitted any organization member now require their declared capability. Workspace reads redact evidence and replay for roles that lack those capabilities, and every raw postgres.js client stores real JSON.

    integrator

    Security fix. These routes now require workspace.read, checked against the persona matrix and the custom-role ceiling: smart-meeting reads, the design tenant policy and hydration, the workspace AI briefing model, Company Intelligence reads, GET /api/companyos/auth/roles and the CommunicationOS native session. Design audit requires replay.read. Built-in roles keep access. A custom role without the capability gets 403. auth.role.list adds the ROLE_LIST_FORBIDDEN error, and owners and admins can always read roles. GET /api/companyos/workspace and /surface/:surfaceId now return evidenceReceipt and replay as { redacted: true, requires } unless the caller holds the matching capability: evidence.read for evidenceReceipt, evidence.read and replay.read for replay. Personal API keys also need the companyos.evidence.read scope. The contract is @lssm-tech/lib.companyos-spec/managed-companyos/workspace-read-redaction.

    maintainer

    withPgJsonSemantics now lives in @lssm-tech/integration.provider-database/postgres-json-semantics. It is installed on every raw postgres.js client of communicationos-api and supportos-api, and of the job-application, osint and supportos workers. Each of these packages has a guard test. A new raw postgres.js client must either install withPgJsonSemantics or be wrapped by Drizzle.

    customer

    A custom role without workspace access no longer opens meeting, design, briefing, company knowledge or role directory data. The roles section explains that the role does not include the directory. Built-in roles see no change.

  • companyos-brain-public-projection

    Public Company Intelligence Brain entry projection moves to companyos-runtime

    integrator

    A new provider-neutral subpath exposes the public Brain entry projection, filter and point/list projection over host-read rows. It drops tombstoned entries and reports only withheld public fields; the existing historical projectBrainEntry is unchanged.

  • companyos-decommission-hirly-ndconsulting

    Hirly and NDconsulting are decommissioned; live seed profiles and booking surfaces cover only LSSM and CompanyOS

    maintainer

    The all and core-workspaces seed/bootstrap profiles now select only lssm and companyos. Live seed and live bootstrap refuse legacy-reference and lssm-hirly because they would recreate decommissioned organizations. Booking surfaces are /u/lssm, /u/companyos and /u/theo. Two tracked operator commands close accounts and decommission organizations with dry-run, approval ref and post-condition checks.

    integrator

    Additive exports only (DECOMMISSIONED_ORGANIZATION_SLUGS, LIVE_ORGANIZATION_SLUGS, isDecommissionedOrganizationSlug, decommissionedSlugsInProfile). Profile ids and the slug union are unchanged; manifest data narrows for the all and core-workspaces profiles.

  • companyos-hirly-owner-only

    Hirly is owner-only; the bootstrap and booking-surface manifests no longer seed Hirly collaborators

    maintainer

    CORE_WORKSPACE_MEMBERSHIPS keeps only the owner entry per organization, so the core-workspaces and all bootstrap profiles stop creating Hirly admin members, grants and team rows for collaborators. COMPANYOS_REQUIRED_BOOKING_SURFACES drops the two Hirly collaborator personal surfaces (4 canonical surfaces, personalSurfaceCount 1). The OPA meeting authority reconcile only targets the owner.

    integrator

    Element and field shapes are unchanged; only the manifest data narrows. Hirly collaborators join through the organization invitation flow instead of the seed.

  • companyos-local-e2e-lane

    Local authenticated Playwright lane for CompanyOS with a test-only, production-refused local-e2e-v1 auth topology.

    maintainer

    bun run e2e:local in the web app provisions a fresh local stack and runs the authenticated sign-in, account, organization, security, OPA, public booking and CommunicationOS specs headless.

    integrator

    @lssm-tech/lib.companyos-spec/managed-companyos/auth-production-topology exports the additive local-e2e-v1 topology contract with its DocBlock.

  • control-plane-contract-owner

    Canonical control-plane contract ownership and unchanged nominal registry signatures

    integrator

    Control-plane operations, events and capability registration now have canonical Builder runtime leaves; pure authority models have LSSM OS spec leaves.

  • economic-evidence-production-declarations

    Separate production declarations from source-only tests

    integrator

    Production declarations exclude source-only test inputs while the strict source typecheck retains them.

  • fo2-s02-d36-review-threshold

    Human-approved low-confidence Company Intelligence records become valid with a trusted review attestation (D36)

    integrator

    Claims, entities and relations below 0.9 confidence can be committed as approved when they carry a reviewDecision attestation by a human reviewer distinct from the extracting agent; confidence is unchanged and everything else below 0.9 still requires review_required.

  • fo2-s02-founder-context

    CompanyOS spec adds the founder context registry, account authority resolver, executive federation grants, additive founder bootstrap and profile loader

    integrator

    New subpath @lssm-tech/lib.companyos-spec/managed-companyos/founder-context exposes stable founder context IDs and alias resolution, typed account authority bindings with a fail-closed resolver, scoped private executive federation grants, an additive founder bootstrap planner, a founder profile loader and ten founder-context operation contracts with DocBlocks.

  • fo2-s02-founder-context-persistence

    Founder context bindings, grants, slot resolutions, bootstrap receipts and operating outcomes become durable and are served by the CompanyOS API

    integrator

    An append-only founder context store (port, in-memory and Postgres), thirteen founder-context operations served by the CompanyOS API, evidence-backed slot resolution, the FW-001 desired operating outcome on LSSM OS goal contracts, and the canonical account-to-context ownership resolver used by the email channel.

  • fo2-s03-gmail-durable-mailbox

    Gmail mailboxes synchronize durably per account, keep lossless evidence, and act only through exact-bound authorized operations

    integrator

    Gmail connections can backfill and follow history with a durable cursor, retain recipients, reply headers, labels, attachment part references and timestamp provenance, hand original attachments to document custody, and run drafts, threaded replies and mailbox operations through an exact action binding with explicit indeterminate outcomes. Knowledge ingestion can bind Gmail documents to a connection and withdraw deleted threads.

  • fo2-s03-mail-live-readiness

    Founder Gmail mailboxes go live through Connect Gmail alone; one bad message, a transient outage or a wrong-mailbox credential no longer stalls or silently misattributes a mailbox

    integrator

    Gmail sync pages no longer stall on one malformed message: it becomes a message_held sync invalidation and coverage stays partial until reconciled. createDeferredGmailOAuth2Client lets hosts read a mailbox credential from custody (for example the CommunicationOS vault written by the Gmail OAuth callback) instead of a refresh token in configuration. GmailMailboxReader.getMessage raises non-retryable payload_invalid for untransformable payloads.

    maintainer

    The CommunicationOS worker checks that each Gmail credential authenticates the connection's own mailbox, keeps transiently failing connections schedulable (offline, not revoked), marks /health no-store, lists migration ids on schema_version_mismatch and reports tls_handshake / tls_not_offered for TLS failures. The founder runbook docs/operations/founder-ops-v2/gmail-connect.md lists the Google console scopes, publishing status, redirect URI and variable names; the only remaining live step is the founder consenting through Connect Gmail.

  • fo2-s13-founder-canary

    The G1 founder canary turns one authorized mailbox message into retained evidence, canonical Work and a cited private brief, with restart-safe checkpoints and executive screens.

    maintainer

    New contracts founder.canary.intake.run, founder.canary.status.read, founder.privateBrief.read and founder.canary.context.confirm (FounderCanaryOperationRegistry) with original-evidence, context-resolution, grounded-brief and checkpoint schemas. The runtime adds runFounderCanary, confirmFounderCanaryContext, the grounding gate and an extractive composer. The managed bundle adds the founder-canary composition (Work, S04 custody/readability, S02 account routing, PostgreSQL canary store) and the founder-executive Today, Needs you, Brief, Evidence and Recovery screens over contract data views with EN/FR/ES catalogs.

    integrator

    Hosts bind createFounderCanaryService with a mailbox source (S03 reader), custody, the account binding store, a WorkManagementService over the durable Work store and a PostgresFounderCanaryStore, then expose the four operations behind server-derived authority. Apply founderCanaryMigrationStatements before use.

  • fo2-s13-founder-canary-day-ledger

    Today renders the owner's validated S06 morning/EOD brief, canary evidence is recorded in the Knowledge ledger so thread withdrawal reaches it, and manual item review is the recorded classification policy.

    maintainer

    Adds founder.dayBrief.read with FounderDailyBriefSchema (validated, stripped S06 brief), an optional FounderEvidenceLedgerPort called after context resolution, createKnowledgeEvidenceRecorder and S03/S04-compatible canary source keys. The service's original-status port is now withdrawn(evidence).

    integrator

    The API serves founder.dayBrief.read from S06 occurrence artifacts (OPA_BYOK_* cipher, owner calendar target); readiness reports item_classifier: manual_review_policy; the canary binds the durable Company Intelligence ledger from LSSM_STUDIO_DATABASE_URL and fails closed without it.

  • fo2-s13-founder-canary-host

    The founder canary is served by the CompanyOS API and web shell, follows S03 history sync, and fails closed on wrong accounts, unconfirmed context, changed bindings and withdrawn evidence.

    maintainer

    Ports gained a bound mailbox connectionId, item signals, binding verification, context-scoped Work identity and a resumable keyset scan; runs guard each message. Context resolutions carry the S02 binding revision; briefs gain the evidence_withdrawn disclosure. The bundle mailbox adapter is driven by S03 createGmailMailboxSync; the service requires an original-status port and returns briefs without withdrawn citations.

    integrator

    POST /api/companyos/founder-canary/operations/:key and GET /api/companyos/founder-canary/readiness (owner-only, Personal context). Configure FOUNDER_CANARY_CONNECTION_ID, FOUNDER_CANARY_SOURCE_ACCOUNT_REF, FOUNDER_CANARY_GMAIL_CLIENT_ID/_CLIENT_SECRET/_REFRESH_TOKEN, optional FOUNDER_CANARY_GMAIL_QUERY, FOUNDER_CANARY_CONTEXT_SCOPES (JSON context → organizationId/workspaceId) and the Company Intelligence originals S3 inputs. Pages: /companyos/executive{,/needs-you,/brief,/evidence,/recovery}.

  • opa-ai-briefing-notes-tasks-sources

    OPA AI briefings can cite the owner's related meeting notes and open tasks when selected

    customer

    In Settings → Personal briefings you can now add your OPA meeting notes and your open tasks to AI briefings. Each statement drawn from them is footnoted as a meeting note or task. Only titles, status, due dates, note dates and short note text are sent; links, e-mail addresses, phone numbers, task descriptions, transcripts and private reflections never are.

    integrator

    OPA_AI_BRIEFINGS_CONTRACT gains sourcePayloads (fields and caps per source kind) and promptVersion opa-ai-briefing-2. The settings view reports availableSources knowledge, meeting-notes and tasks; email-bodies stays unavailable and is still rejected with AI_BRIEFINGS_SOURCE_UNAVAILABLE.

    maintainer

    createOpaBriefingContextLoader (api calendar) returns nothing when neither kind is selected, reads each candidate workspace (personal + calendar-mapped, max 6) in its own transaction through loadCompanyOpaBackgroundAuthority, decrypts meeting state only when OPA intake recorded a related meeting, replays canonical Work events without enrolling identities, and logs opa_ai_briefing.context_degraded with counts only.

  • opa-calendar-scope-states

    Booking vs personal calendar explanations and explicit Microsoft not-connected state.

    customer

    OPA settings explain booking vs personal calendars and show consistent connect, disconnect, retry and reconnect states for Google and Microsoft.

    integrator

    The personal Microsoft calendars list query adds the MICROSOFT_NOT_CONNECTED (409) error; existing error codes are unchanged.

  • opa-microsoft-connection-truth

    Microsoft calendar panel shows connected only after a successful load; unconfigured deployments get a neutral notice.

    customer

    OPA settings no longer show a contradictory Connected state for Microsoft when it is not set up or the check failed.

    integrator

    The personal Microsoft calendars list query adds MICROSOFT_CALENDAR_NOT_CONFIGURED (503) for hosts without a Microsoft OAuth application.

  • opa-today-timeline-insights

    OPA Today shows a live timeline, Insights shows honest signals, and public booking routes load a third less JavaScript

    integrator

    The personal daily-operations query and commands declare personal_context_required (409) and daily_operations_unavailable (503) instead of failing with an unhandled 500, and the calendar projection now starts 24 hours before the request. Hosts rendering public booking management, public profiles or the OPA booking tab can import the narrow ./ui/public-booking-manage, ./ui/public-profile and ./ui/booking-admin entries instead of ./ui/templates.

  • s3-opa-shared-pre-meeting-briefs

    OPA meetings S3: calendar intake hosted as a CompanyOS API cron with a kill switch, private pre-meeting briefs up to 24 hours ahead, and owner-approved participant-safe shared pre-reads delivered by email.

    integrator

    Additive contracts: calendar-intelligence.personal-preferences.update 3.2.0 (wider preparationLeadMinutes set, optional sharedBriefEnabled whose omission keeps the stored value), calendar-intelligence.shared-briefs.list@1.0.0 and calendar-intelligence.shared-briefs.decide@1.0.0 (digest-bound approve or skip, recipients can only be removed). Runtime adds SqlMeetingIntakeJobQueue.provisionJob and deferJob; existing queue methods are unchanged.

    maintainer

    Apply migration 0166 (companyos/opa-shared-briefs-0166). Two new Vercel crons: /api/cron/meeting-intake and /api/cron/meeting-shared-briefs (every 5 minutes, service principal only). Both do nothing until their kill switch is 1 (OPA_MEETING_INTAKE_ENABLED, OPA_SHARED_BRIEFS_ENABLED). When enabled but misconfigured they answer 503 and list missing key names only. Run one meeting intake host per owner scope: either this cron or the standalone meeting-intake worker.

    customer

    Private meeting briefs can arrive up to 24 hours before a meeting. Owners can opt in to a shared pre-read for attendees. It contains only the meeting's own calendar details plus what the owner writes, and nothing is sent until the owner approves it. A meeting that moves or is cancelled cancels the pending pre-read.

  • ts-01-p-email

    Gmail readonly reader, one-attempt Gmail delivery with Message-ID reconciliation and a zero-network controlled fixture in provider-email

    integrator

    Additive subpaths ./impls/gmail-readonly-reader, ./impls/gmail-delivery and ./impls/gmail-fixture. gmail-mime gains an optional messageId build option and decodeGmailHeaderWords; without messageId the built MIME is unchanged. GmailMailboxReader and its gmail.metadata path are untouched. The reader and delivery take a grant source ({ accessToken, scopes }) and an injectable fetch; they do not run OAuth.

    maintainer

    Delivery never retries a POST. An uncertain outcome must be reconciled by Message-ID (read-only) and never resent; an empty Sent search proves nothing. Scope refusals happen before any network call. Live Gmail behavior is unqualified: only fixture/fake transports were exercised.

  • ts-01-size-fu

    Internal file split of the Gmail reader, delivery and fixture and the Gateway LLM provider under the 250-line limit, with no behavior or surface change

    maintainer

    Internal file split, no behavior or surface change. Runtime export keys and declaration types of impls/gmail-readonly-reader, impls/gmail-delivery, impls/gmail-fixture, impls/gateway-llm, both impls barrels and both package roots are identical to the previous release.

  • web-01-board-rt

    Board decision-workspace semantics in founder-intelligence (backup v1, merge, tombstones, revision state machine, intake and recipient projection)

    integrator

    Compose a BoardProfile (storage key, backup format, contexts, taxonomies, seeds and recipient copy) and a private-store implementation in the host. The legacy Board keeps the storage key lssm-funding-workspace-iteration11 and backup format lssm-funding-workspace (owner decision 2b). Supply a synchronous storage adapter to createBoardStore; the browser-local adapter is host-owned.

    maintainer

    Spec and runtime Board code never import module.forms, UI or browser storage. A blocked store never writes; reset requires an export of the exact current state (or the recovery copy); a recipient export requires approval of the exact current projection inputs; tombstoned cases are never resurrected.

  • x11-cli-extraction-owners

    CLI and IDE behavior moves to Builder runtime, execution-lanes, harness, cli-runtime, contracts-library and bundle.workspace owners

    integrator

    New owner subpaths expose the Builder production run workflow behind store and provider ports (lib.builder-runtime/production/workflow), lane launch policy (lib.execution-lanes/launch), local harness auto-approval (lib.harness/policy/local-runtime), example stub planning (lib.cli-runtime/example-catalog/stub), example maturity gating (lib.contracts-library/examples/maturity) and registry install planning, OpenAPI serialization and default spec scaffolds (bundle.workspace).

    maintainer

    Completed Builder production runs now carry an economic replay packet. The Builder CLI token must be provided as CONTROL_PLANE_API_TOKEN, and the tmux workbench passes API keys through the pane environment instead of the command line.

Deprecations

  • LSSM_HIRLY_OWNER_BINDINGS is removed at the next major; use CORE_WORKSPACE_OWNER_BINDINGS for live owner bindings.
  • The collaborators:hirly OrganizationBootstrapPhase literal is kept only for historical receipts and removed at the next major.
  • The legacy-reference and lssm-hirly seed profiles are reference-only and must not be applied live.
  • The lssm-hirly seed/bootstrap profile (OrganizationSeedProfileId member, ORGANIZATION_SEED_PROFILE_IDS entry, ORGANIZATION_SEED_PROFILE_SLUGS and ORGANIZATION_SEED_MANIFESTS keys) is retired and removed at the next major of @lssm-tech/lib.companyos-spec.

Migration guide

  • Apply the additive identity session context migration

    Required

    Apply 0205 before activating the central organization session mapping.

    1. Include 0205 in the reviewed selective identity migration manifest.
    2. Verify both physical identity context columns and central Drizzle metadata.
    3. Preserve all existing CompanyOS context values and audit triggers.
  • Implement transactional admission in custom lifecycle stores

    The optional proveProductAccess port extension fails closed when absent; stores must implement it to continue offering personal ensure.

    1. Reprove current product admission before receipt replay or provisioning.
    2. Do not infer admission from identity, organization membership or global role.
  • Select core-workspaces or all instead of lssm-hirly

    Callers that still pass lssm-hirly to the bootstrap get "MANAGED_COMPANYOS_SEED_PROFILE must be one of legacy-reference, core-workspaces, or all." Live seed already refused it.

    1. Set MANAGED_COMPANYOS_SEED_PROFILE to core-workspaces or all.
    2. Replace LSSM_HIRLY_OWNER_BINDINGS reads with CORE_WORKSPACE_OWNER_BINDINGS.
  • Normalize string-encoded jsonb after deploying

    Rewrites the jsonb values that the old postgres.js writers stored as JSON text in 17 non-authority columns.

    1. Set LSSM_STUDIO_DATABASE_URL to the tracked operator database URL (a role that bypasses RLS). Run COMPANYOS_JSONB_NORMALIZE=dry-run bun --cwd packages/apps/api-application-monolith run companyos:jsonb:normalize-text and review the counts.
    2. Run the same command with COMPANYOS_JSONB_NORMALIZE=1. It is idempotent. If it exits 3, a relay held some rows locked, so run it again. A second dry run reports only unparseable and report-only rows.
  • Run the authority repair after deploying

    Converts authority jsonb stored as a string and moves member grants to the joined persona.

    1. With the tracked operator database URL (a role that bypasses RLS) in LSSM_STUDIO_DATABASE_URL, run COMPANYOS_AUTHORITY_REPAIR=dry-run bun --cwd packages/apps/api-application-monolith run companyos:authority:repair-jsonb and review the counts.
    2. If any count is non-zero, run it again with COMPANYOS_AUTHORITY_REPAIR=1. The repair is idempotent, and a second dry run reports zero.
  • Stop expecting seeded Hirly collaborators

    No code change is required. Operators must not rely on bootstrap or booking-surface activation to (re)create Hirly collaborator memberships or personal booking pages.

    1. Invite Hirly collaborators through the organization invitation flow when access is needed again.
  • Declare reviewerKind on trusted review decisions

    Optional. Hosts that want reviewed low-confidence facts committed pass reviewerKind 'human' from their authenticated reviewer identity; without it behaviour is unchanged.

    1. Set reviewerKind on CompanyIntelligenceTrustedReviewDecision from the authenticated reviewer, never from model output.
  • Apply migration 0100 before enabling the founder-context routes

    Additive schema founder_context.records with owner-scoped forced RLS; no existing table, tenant or membership changes. Bootstrap apply records associations only and defers membership changes to the canonical organization membership operations.

    1. Run the API migration catalog through 0100 on a backed-up database.
    2. Register founderContextHandler in the API app and bind sessions with fresh context authority.
    3. Wire createAccountContextResolver with createStoredBindingSource for the email channel.
  • Optionally resolve source account authority through the founder context resolver

    Additive only; existing imports, tenants and the organization-bootstrap:v3 receipt are unchanged. Alias mapping migrates no data and grants no access.

    1. Import resolveAccountAuthority or createAccountAuthorityResolver from @lssm-tech/lib.companyos-spec/managed-companyos/founder-context.
    2. Treat every denied resolution as fail-closed; pin expectedBindingId/expectedBindingVersion for resumed runs.
    3. Bind handlers for founderContextOperationRegistry in the host before exposing the operations.
  • Bind Gmail knowledge ingestion to a connection

    Without a source binding, GmailIngestionAdapter keeps legacy thread-only document ids labelled unqualified_legacy. Pass options.source.connectionRef (and a withdrawal port) to get account-bound ids and deletion withdrawal; re-index affected threads once after enabling it.

    1. Construct GmailIngestionAdapter with { source: { connectionRef }, withdrawal: createVectorGmailWithdrawal(...) }.
    2. Re-run Gmail ingestion so account-bound ids replace legacy thread-only ids.
  • Treat response_unverified as an indeterminate send

    Required

    GmailOutboundProvider.sendEmail now throws GmailProviderError('response_unverified') when Gmail returns no message id. Callers must hold the action for reconciliation instead of resending.

    1. Map GmailProviderError code response_unverified to an indeterminate outcome in custom callers.
  • Apply app migration 0115

    Creates the founder_canary schema (checkpoints with hold_code and resumable index, cursors, briefs, runs) with forced tenant RLS.

    When: Before enabling the founder canary on a host.

    1. Run the app migration ledger through 0115.
    2. Bind an S02 mailbox account binding for the founder before the first run.
  • Create the founder_canary schema

    Additive tables for checkpoints, cursors, private briefs and run receipts with forced tenant RLS.

    When: When an installation enables the one-mailbox founder canary.

    1. Run migrateFounderCanaryStore (or register founderCanaryMigrationStatements in the host migration order).
    2. Grant the runtime role select/insert/update on founder_canary tables only.
  • Import public booking and profile templates from their narrow entries

    Optional. Importing ./ui/templates from a Next.js route registers every template as a client reference; the narrow entries keep anonymous pages small. Existing imports keep working.

    1. Replace PublicBookingManageTemplate, getManageBookingCopy and resolveBookingLifecycleCopy imports with ./ui/public-booking-manage.
    2. Replace PublicCommsProfileTemplate imports with ./ui/public-profile and PublicCommsAdminTemplate with ./ui/booking-admin.
  • Apply migration 0166

    Required

    Widens the lead-time check, adds shared_brief_enabled (default false) and creates companyos_opa_shared_briefs with forced RLS.

    1. Run the tracked CompanyOS migration runner so 0166 is applied after 0165.
    2. Verify companyos_opa_shared_briefs has row-level security forced and the runtime role can read and write it.
  • Enable API-hosted meeting intake

    Optional; leave OPA_MEETING_INTAKE_ENABLED unset to keep intake off.

    1. Set the owner scopes, protected configs, Granola credential and OPA_MEETING_ACCESS_GRANT_PEPPER / OPA_BYOK_* keys, then OPA_MEETING_INTAKE_ENABLED=1.
    2. Do not also deploy the standalone meeting-intake worker for the same owner scopes.
  • Use the all or core-workspaces profile for live seed/verify

    MANAGED_COMPANYOS_SEED_PROFILE=all now verifies lssm and companyos only. Live commands reject legacy-reference and lssm-hirly.

    1. Run live seed/verify with MANAGED_COMPANYOS_SEED_PROFILE=all (or core-workspaces).
  • Treat message_held invalidations as coverage gaps

    Consumers of Gmail sync pages may now receive email.sync.invalidation events with metadata.changeKind message_held (messageId, heldCode). They record a message that was skipped and keep coverage partial; they are not deletions.

    1. Ignore or surface events whose metadata.changeKind is message_held; do not withdraw records for them.
    2. Read describeGmailSyncCoverage(cursor).held to disclose skipped messages.
  • Configure a scoped access token to use the gateway

    Optional. Leave the variables unset to keep the previous anonymous, fail-closed behaviour.

    1. Mint a CommunicationOS access token for the operator principal through communicationos-api, scoped to one tenant, workspace and space.
    2. Set COMMOS_MCP_ACCESS_TOKEN, COMMOS_MCP_TENANT_ID, COMMOS_MCP_WORKSPACE_ID, COMMOS_MCP_SPACE_ID and COMMUNICATION_OS_ACCESS_TOKEN_SECRET on the server that runs the gateway, next to communicationos-api.
    3. Restart the gateway with a fresh token before the current one expires; check the subject field of the communicationos-mcp.started log line.
  • Optionally import the new CompanyOS owner subpaths

    Additive only; existing imports are unchanged. Hosts may import the context authority types and the runtime policies from their owners instead of keeping local copies, implementing the declared store ports.

    1. Import context authority types from @lssm-tech/lib.companyos-spec/managed-companyos/context-authority.
    2. Import the runtime policy from the matching @lssm-tech/lib.companyos-runtime subpath (for example ./personal-context-lifecycle, ./design-partner-approval-workflow, ./company-intelligence-ingestion or ./calendar-intelligence-run).
    3. Implement the subpath's store/sender/clock ports over host persistence and providers; keep SQL, secrets and environment reads in the host.
  • Optionally use the runtime public Brain projection

    Additive only; existing imports and projectBrainEntry behaviour are unchanged. Hosts serving the public Brain API may call the new subpath instead of a local projection copy.

    1. Import projectPublicBrainEntry, readProjectedPublicBrainEntry or listProjectedPublicBrainEntries from @lssm-tech/lib.companyos-runtime/company-intelligence-brain-public-projection and pass rows read by the host, newest first per entry.
  • Optionally call the new owner subpaths

    Additive; existing CLI and bundle imports keep working (CLI launch-specs and agent adapters stay as compatibility forwards). Hosts may call the owner subpaths instead of reimplementing the policy.

    1. Import production workflow, lane launch, harness approval, example stub/maturity or registry/OpenAPI helpers from the owner subpath.
  • Use CONTROL_PLANE_API_TOKEN for the Builder control-plane token

    Required

    The Builder CLI and doctor no longer read arbitrary environment variable names from builder.api.controlPlaneTokenEnvVar. Workspaces that configured another name must export the token as CONTROL_PLANE_API_TOKEN.

    1. Set builder.api.controlPlaneTokenEnvVar to CONTROL_PLANE_API_TOKEN (the default) or remove it.
    2. Export the token as CONTROL_PLANE_API_TOKEN.
  • Existing contracts-spec paths remain supported with identical exports and nominal registry...

    Existing contracts-spec paths remain supported with identical exports and nominal registry parameter and return types.

    1. Existing contracts-spec paths remain supported with identical exports and nominal registry parameter and return types.

Upgrade steps

  • Qualify central and product hosts against the shared native schema

    manual

    Run separate real HTTP hosts with CompanyOS audit triggers enabled.

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

    1. Verify central organization invitation acceptance and switching use only identity context columns.
    2. Verify central password, OTP and magic-link sessions cannot provision product rows.
    3. Verify promoted native product signup and legitimate legacy product grants still work.
    4. Verify raw product admin HTTP denial, credential isolation and entitlement revocation.
    5. Prove a concurrent raw revoked INSERT cannot escape the missing-entitlement legacy fence; verify bounded timeout and higher-isolation denial.
    6. Use READ COMMITTED for legacy admission; higher transaction isolation intentionally fails closed.
  • Publish an HTTPS, non-loopback public origin for managed Marketing Operations installations

    manual

    Installations that declare deployment: 'managed' now start through the managed composition, which refuses (MARKETING_MANAGED_BINDING) a publicOrigin that is not HTTPS or is a loopback or unspecified host. Self-hosted installations are unchanged.

    Packages: @lssm-tech/app.communicationos-mcp, @lssm-tech/app.communicationos-worker, @lssm-tech/app.communicationos-discord-worker

    1. Before upgrading, check every installation module that declares deployment: 'managed' and set its publicOrigin to the HTTPS, non-loopback origin browsers use (not http://, localhost, *.localhost, 127.0.0.0/8, 0.0.0.0, ::1 or ::).
    2. Installations that are really self-hosted, such as local development or loopback test hosts, declare deployment: 'self-hosted' instead.
  • Relaunch the managed CommunicationOS MCP gateway before its 5-minute session ends

    manual

    A gateway launched with COMMOS_MCP_HOST_ASSERTION holds the exchanged session for 5 minutes, then every tool call is anonymous. Hosts that adopt the managed launch relaunch it with a fresh assertion.

    Packages: @lssm-tech/app.communicationos-mcp, @lssm-tech/app.communicationos-worker, @lssm-tech/app.communicationos-discord-worker

    1. Supply COMMUNICATION_OS_HOST_MEMBERSHIPS, COMMUNICATION_OS_COMPANYOS_ISSUER and both secrets from operator-controlled deployment configuration; only the assertion and its scope are per-launch input.
    2. Relaunch the gateway with a fresh assertion before the 5-minute session ends.
  • Run the local authenticated E2E lane

    manual

    Requires Docker and Playwright Chromium; nothing reaches production or Google.

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

    1. cd packages/apps/web-application-monolith && bun run e2e:local
    2. Set E2E_LOCAL_REUSE_BUILD=1 to skip an identical next build on later runs.

Unique release changes

  • Additive; existing CLI and bundle imports keep working (CLI launch-specs and agent adapters stay as compatibility forwards). Hosts may call the owner subpaths instead of reimplementing the policy.

    11 packages · 11 occurrences

  • CLI and IDE behavior moves to Builder runtime, execution-lanes, harness, cli-runtime, contracts-library and bundle.workspace owners

    11 packages · 11 occurrences

  • The Builder CLI and doctor no longer read arbitrary environment variable names from builder.api.controlPlaneTokenEnvVar. Workspaces that configured another name must export the token as CONTROL_PLANE_API_TOKEN.

    11 packages · 11 occurrences

  • Rewrites the jsonb values that the old postgres.js writers stored as JSON text in 17 non-authority columns.

    9 packages · 9 occurrences

  • Security fix. The last CompanyOS routes that admitted any organization member now require their declared capability. Workspace reads redact evidence and replay for roles that lack those capabilities, and every raw postgres.js client stores real JSON.

    9 packages · 9 occurrences

  • Complete canonical CompanyOS and context contract ownership

    4 packages · 4 occurrences

  • A gateway launched with COMMOS_MCP_HOST_ASSERTION holds the exchanged session for 5 minutes, then every tool call is anonymous. Hosts that adopt the managed launch relaunch it with a fresh assertion.

    3 packages · 3 occurrences

  • Additive schema founder_context.records with owner-scoped forced RLS; no existing table, tenant or membership changes. Bootstrap apply records associations only and defers membership changes to the canonical organization membership operations.

    3 packages · 3 occurrences

  • Additive tables for checkpoints, cursors, private briefs and run receipts with forced tenant RLS.

    3 packages · 3 occurrences

  • Board decision-workspace semantics in founder-intelligence (backup v1, merge, tombstones, revision state machine, intake and recipient projection)

    3 packages · 3 occurrences

  • Calendar readers keep attendee e-mail addresses under a documented purpose, retention, access and logging policy

    3 packages · 3 occurrences

  • Callers that still pass lssm-hirly to the bootstrap get "MANAGED_COMPANYOS_SEED_PROFILE must be one of legacy-reference, core-workspaces, or all." Live seed already refused it.

    3 packages · 3 occurrences

  • Canonical control-plane contract ownership and unchanged nominal registry signatures

    3 packages · 3 occurrences

  • Consumers of Gmail sync pages may now receive email.sync.invalidation events with metadata.changeKind message_held (messageId, heldCode). They record a message that was skipped and keep coverage partial; they are not deletions.

    3 packages · 3 occurrences

  • Creates the founder_canary schema (checkpoints with hold_code and resumable index, cursors, briefs, runs) with forced tenant RLS.

    3 packages · 3 occurrences

  • Existing contracts-spec paths remain supported with identical exports and nominal registry parameter and return types.

    3 packages · 3 occurrences

  • Founder context bindings, grants, slot resolutions, bootstrap receipts and operating outcomes become durable and are served by the CompanyOS API

    3 packages · 3 occurrences

  • Founder Gmail mailboxes go live through Connect Gmail alone; one bad message, a transient outage or a wrong-mailbox credential no longer stalls or silently misattributes a mailbox

    3 packages · 3 occurrences

  • Gmail mailboxes synchronize durably per account, keep lossless evidence, and act only through exact-bound authorized operations

    3 packages · 3 occurrences

  • GmailOutboundProvider.sendEmail now throws GmailProviderError('response_unverified') when Gmail returns no message id. Callers must hold the action for reconciliation instead of resending.

    3 packages · 3 occurrences

  • Installations that declare deployment: 'managed' now start through the managed composition, which refuses (MARKETING_MANAGED_BINDING) a publicOrigin that is not HTTPS or is a loopback or unspecified host. Self-hosted installations are unchanged.

    3 packages · 3 occurrences

  • LSSM_HIRLY_OWNER_BINDINGS is removed at the next major; use CORE_WORKSPACE_OWNER_BINDINGS for live owner bindings.

    3 packages · 3 occurrences

  • Managed-ecosystem compositions for the CommunicationOS MCP gateway, CommunicationOS and Discord workers and the Marketing Operations shell

    3 packages · 3 occurrences

  • Move existing draft Builder delivery services and generic host ports to their reusable lower owners with compatible workspace forwarding exports.

    3 packages · 3 occurrences

  • OPA meetings S3: calendar intake hosted as a CompanyOS API cron with a kill switch, private pre-meeting briefs up to 24 hours ahead, and owner-approved participant-safe shared pre-reads delivered by email.

    3 packages · 3 occurrences

  • Optional; leave OPA_MEETING_INTAKE_ENABLED unset to keep intake off.

    3 packages · 3 occurrences

  • Retire the Hirly bootstrap profile and collaborator phase behind a deprecation window; NDconsulting seeds become reference-only

    3 packages · 3 occurrences

  • The collaborators:hirly OrganizationBootstrapPhase literal is kept only for historical receipts and removed at the next major.

    3 packages · 3 occurrences

  • The founder canary is served by the CompanyOS API and web shell, follows S03 history sync, and fails closed on wrong accounts, unconfirmed context, changed bindings and withdrawn evidence.

    3 packages · 3 occurrences

  • The G1 founder canary turns one authorized mailbox message into retained evidence, canonical Work and a cited private brief, with restart-safe checkpoints and executive screens.

    3 packages · 3 occurrences

  • The lssm-hirly seed/bootstrap profile (OrganizationSeedProfileId member, ORGANIZATION_SEED_PROFILE_IDS entry, ORGANIZATION_SEED_PROFILE_SLUGS and ORGANIZATION_SEED_MANIFESTS keys) is retired and removed at the next major of @lssm-tech/lib.companyos-spec.

    3 packages · 3 occurrences

  • Today renders the owner's validated S06 morning/EOD brief, canary evidence is recorded in the Knowledge ledger so thread withdrawal reaches it, and manual item review is the recorded classification policy.

    3 packages · 3 occurrences

  • Widens the lead-time check, adds shared_brief_enabled (default false) and creates companyos_opa_shared_briefs with forced RLS.

    3 packages · 3 occurrences

  • Without a source binding, GmailIngestionAdapter keeps legacy thread-only document ids labelled unqualified_legacy. Pass options.source.connectionRef (and a withdrawal port) to get account-bound ids and deletion withdrawal; re-index affected threads once after enabling it.

    3 packages · 3 occurrences

  • Additive only; existing imports are unchanged. Hosts may import the context authority types and the runtime policies from their owners instead of keeping local copies, implementing the declared store ports.

    2 packages · 2 occurrences

  • Apply 0205 before activating the central organization session mapping.

    2 packages · 2 occurrences

  • Booking vs personal calendar explanations and explicit Microsoft not-connected state.

    2 packages · 2 occurrences

  • Consume canonical portable declarations and unchanged translation factories in CompanyOS composition.

    2 packages · 2 occurrences

  • Emit existing published CompanyOS and provider-spec entrypoints and qualify packed Builder lazy resolution

    2 packages · 2 occurrences

  • Hirly and NDconsulting are decommissioned; live seed profiles and booking surfaces cover only LSSM and CompanyOS

    2 packages · 2 occurrences

  • Hirly is owner-only; the bootstrap and booking-surface manifests no longer seed Hirly collaborators

    2 packages · 2 occurrences

  • Human-approved low-confidence Company Intelligence records become valid with a trusted review attestation (D36)

    2 packages · 2 occurrences

  • Internal file split of the Gmail reader, delivery and fixture and the Gateway LLM provider under the 250-line limit, with no behavior or surface change

    2 packages · 2 occurrences

  • Managed CompanyOS host policy moves from the API monolith to companyos-spec and companyos-runtime

    2 packages · 2 occurrences

  • MANAGED_COMPANYOS_SEED_PROFILE=all now verifies lssm and companyos only. Live commands reject legacy-reference and lssm-hirly.

    2 packages · 2 occurrences

  • Microsoft calendar panel shows connected only after a successful load; unconfigured deployments get a neutral notice.

    2 packages · 2 occurrences

  • No code change is required. Operators must not rely on bootstrap or booking-surface activation to (re)create Hirly collaborator memberships or personal booking pages.

    2 packages · 2 occurrences

  • OPA AI briefings can cite the owner's related meeting notes and open tasks when selected

    2 packages · 2 occurrences

  • OPA Today shows a live timeline, Insights shows honest signals, and public booking routes load a third less JavaScript

    2 packages · 2 occurrences

  • Optional. Hosts that want reviewed low-confidence facts committed pass reviewerKind 'human' from their authenticated reviewer identity; without it behaviour is unchanged.

    2 packages · 2 occurrences

  • Optional. Importing ./ui/templates from a Next.js route registers every template as a client reference; the narrow entries keep anonymous pages small. Existing imports keep working.

    2 packages · 2 occurrences

  • Preserve Managed CompanyOS semantics through canonical CompanySpec ownership

    2 packages · 2 occurrences

  • Run separate real HTTP hosts with CompanyOS audit triggers enabled.

    2 packages · 2 occurrences

  • Separate central organization session context and global identity roles from CompanyOS admission, personal provisioning and product authorization.

    2 packages · 2 occurrences

  • The legacy-reference and lssm-hirly seed profiles are reference-only and must not be applied live.

    2 packages · 2 occurrences

  • The optional proveProductAccess port extension fails closed when absent; stores must implement it to continue offering personal ensure.

    2 packages · 2 occurrences

  • Additive only; existing imports and projectBrainEntry behaviour are unchanged. Hosts serving the public Brain API may call the new subpath instead of a local projection copy.

    1 package · 1 occurrence

  • Additive only; existing imports, tenants and the organization-bootstrap:v3 receipt are unchanged. Alias mapping migrates no data and grants no access.

    1 package · 1 occurrence

  • CompanyOS spec adds the founder context registry, account authority resolver, executive federation grants, additive founder bootstrap and profile loader

    1 package · 1 occurrence

  • Converts authority jsonb stored as a string and moves member grants to the joined persona.

    1 package · 1 occurrence

  • Gmail readonly reader, one-attempt Gmail delivery with Message-ID reconciliation and a zero-network controlled fixture in provider-email

    1 package · 1 occurrence

  • Local authenticated Playwright lane for CompanyOS with a test-only, production-refused local-e2e-v1 auth topology.

    1 package · 1 occurrence

  • Optional. Leave the variables unset to keep the previous anonymous, fail-closed behaviour.

    1 package · 1 occurrence

  • Public Company Intelligence Brain entry projection moves to companyos-runtime

    1 package · 1 occurrence

  • Requires Docker and Playwright Chromium; nothing reaches production or Google.

    1 package · 1 occurrence

  • Security fix. CompanyOS read routes now require their declared capability instead of a tenant match alone. Authority jsonb is stored as real JSON, and self-service joiners get a valid CompanyOS persona.

    1 package · 1 occurrence

  • Separate production declarations from source-only tests

    1 package · 1 occurrence

  • The CommunicationOS MCP gateway verifies a scoped access token at startup and acts for that subject until the token expires.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/app.communicationos-api

    Layer: apps · 2 changes

  • @lssm-tech/app.communicationos-discord-worker

    Layer: apps · 3 changes

  • @lssm-tech/app.communicationos-mcp

    Layer: apps · 2 changes

  • @lssm-tech/app.communicationos-worker

    Layer: apps · 2 changes

  • @lssm-tech/app.supportos-api

    Layer: apps · 2 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 1 change

  • @lssm-tech/bundle.workspace

    Layer: bundles · 1 change

  • @lssm-tech/integration.cli-contractspec-ai

    Layer: integrations · 3 changes

  • @lssm-tech/integration.cli-contractspec-builder

    Layer: integrations · 3 changes

  • @lssm-tech/integration.cli-contractspec-examples

    Layer: integrations · 3 changes

  • @lssm-tech/integration.communication-channel-email

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-managed-runtime

    Layer: integrations · 2 changes

  • @lssm-tech/integration.osint-managed-runtime

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-calendar

    Layer: integrations · 1 change

  • @lssm-tech/integration.provider-database

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-email

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-llm

    Layer: integrations · 1 change

  • @lssm-tech/integration.supportos-worker-managed

    Layer: integrations · 2 changes

  • @lssm-tech/integration.workspace-ai

    Layer: integrations · 3 changes

  • @lssm-tech/lib.agent-protocol-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.authos-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.builder-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.cli-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.companyos-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.companyos-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.context-storage

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-library

    Layer: libs · 3 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.economic-evidence

    Layer: libs · 1 change

  • @lssm-tech/lib.execution-lanes

    Layer: libs · 3 changes

  • @lssm-tech/lib.founder-intelligence-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.founder-intelligence-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.harness

    Layer: libs · 3 changes

  • @lssm-tech/lib.knowledge

    Layer: libs · 3 changes

  • @lssm-tech/lib.lssm-os-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.organization-planning-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.provider-spec

    Layer: libs · 1 change

  • @lssm-tech/module.auth-os

    Layer: modules · 2 changes

  • @lssm-tech/module.builder-workbench

    Layer: modules · 3 changes

  • @lssm-tech/module.companyos

    Layer: modules · 1 change

  • @lssm-tech/module.founder-intelligence

    Layer: modules · 1 change