Skip to content
← Back to changelog index

2.0.4

Nov 05, 2026 · 125 packages · 242 unique changes · 148 release entries

appsbundlesintegrationslibsmodulestoolsBreaking 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

  • adoption-catalog-build-metadata

    Select installed adoption inventories by release and source priority.

    maintainer

    Version build metadata no longer outranks catalog source provenance.

  • agentpack-contractspec-claude-hooks

    Consumer-pack Claude Code hooks use the Claude blocking protocol, cover PowerShell, emit one line of catalog context, and scope the catalog memory rule.

    integrator

    Regenerated Claude Code settings run the adoption hooks with --host claudecode, so adoption denials block in Claude Code and adoption reviews follow the session permission mode: no prompt in bypassPermissions/dontAsk (the review is deferred and recorded), a prompt in default, a deny in plan. A workspace without connect.enabled (the contractspec init default) is not prompted: the adoption hooks exit 0 silently there. Evaluation failures in a Connect-enabled workspace still fail closed with a prompt. The shell hook matcher is Bash|PowerShell. SessionStart adds one line of catalog context (can-help catalog status --host claudecode) instead of raw JSON, and the catalog memory rule loads only for package.json, **/package.json, and .contractspec/**. Codex and OpenCode entries are unchanged.

  • agentpack-published-dist

    Include built Agentpack artifacts required by existing published exports.

    integrator

    Existing published exports retain their paths and now include their built artifacts in the files allowlist.

  • app-extraction-lane-x7

    PersonalOS host offline replay, offline admission, presentation access, journey catalog, command context, command builders and governed projection transport move to owner packages

    integrator

    New owner subpaths expose the canonical PersonalOS offline replay state machine, offline admission and queue integrity, the fail-closed presentation access policy, the journey action catalog, the journey command context projection, a native-safe digest-port binding lane, progress-celebration and life-admin command builders, support notification validation, the health authorization connect command and a server-only governed projection transport.

    customer

    PersonalOS web, desktop and mobile now apply one presentation and offline replay policy, so a stale presentation blocks actions everywhere and queued offline work retries with the same bounded backoff.

  • authos-account-security-completion

    Trusted devices, gated connect-with-LSSM, social provider readiness, gated phone/SMS second factor, and recent authentication for sensitive actions.

    integrator

    Additive operations/security contracts (trusted devices, connect with LSSM, provider readiness, phone, SMS second factor) and the recent-authentication policy. auth.mfa.verify, auth.account.get, auth.account.changePassword and auth.apiKey.create move to 1.1.0 with optional fields only. Hosts gating sensitive settings (for example SSO) should require recent authentication and declare REAUTHENTICATION_REQUIRED / RECENT_SIGN_IN_REQUIRED.

    customer

    Tick "Remember this device for 30 days" when you enter your authentication code; see and remove trusted devices on the Security page (changing your password removes them all). The Security page shows when your password last changed. Creating an API key asks for your password if you signed in more than 10 minutes ago. Administrators can check which sign-in providers are live under Security → Sign-in providers. Connect with LSSM and text-message codes appear only once enabled on the deployment.

  • authos-account-self-service

    AuthOS account self-service — profile, password, verified email change, secondary emails, and account deletion

    integrator

    New additive contracts (auth.account.get/updateProfile/changePassword/delete), an AuthAccountAdapter port with account hooks and organisms, and the authOs.account.* translations. SecuritySettings now hides actions whose callbacks are not provided instead of rendering dead buttons.

    customer

    CompanyOS users can edit their name, change their password and sign-in email, manage secondary emails, and delete their account from Account settings.

  • authos-auth-domain-ownership

    AuthOS auth-audit, email-address, waitlist-admin, operator-auth and dev binding rules move to their AuthOS owners

    integrator

    lib.authos-runtime adds ./auth-audit, ./auth-email-address, ./waitlist-admin and ./operator-auth (rules over injected ports with injectable clock/ids); integration.authos-better-auth exports pure PROPOSED_NOT_ADMITTED dev issuance, registration and security-review binding checks through ./server; module.auth-os WaitlistJoinForm marks its consent checkbox aria-required.

  • authos-central-foundation-20261101

    Sixteen-provider AuthOS configuration, guarded official plugin wiring, and central passwordless MFA and email fixes.

    integrator

    New social provider identifiers and optional official plugins require host-specific authority configuration, schemas and callbacks. Credential readiness is distinct from production proof. Existing authos.v0 declarations remain valid.

    customer

    Central identity preserves passwordless destinations and supports its own authenticator challenge and reset pages. Production rollout and provider activation are still pending and are tracked separately.

  • authos-central-management-20261101

    Independent central identity registration, management, reviewed applications and separately consented platform reads.

    integrator

    Additive central contracts, explicit host policy, scoped connection readers and reviewed confidential OIDC clients extend the identity platform. Existing product authority remains local, and anonymous dynamic registration remains disabled.

    customer

    Central account, organization, key, agent and security management are implemented with EN/FR/ES support. Availability depends on the separately verified deployment and provider activation matrix; configuration alone is not a login canary.

  • authos-custom-roles

    Organization custom roles as capability bundles over a declared catalog, with versioned grant rewrites and impact previews.

    integrator

    New additive contracts auth.role.{catalog,list,create,update,delete,assign,unassign} in @lssm-tech/lib.authos-spec/operations/roles with a declared capability catalog and read-only built-in templates. Hosts must accept only catalog capabilities, refuse owner-only capabilities and capabilities the caller cannot hand out, and bump grant authority versions on every assignment. Grants carrying the authority.role_bounded marker cap governed actions (roleActionCeiling); ManagedCompanyOsAccessContext gains an optional actionCeiling. module.auth-os adds OrganizationRoleAdapter, useOrganizationRoles and OrganizationRolesPanel.

    customer

    Owners and admins can open Organization → Roles and access, duplicate a built-in role, choose exactly what it allows, and give it to members. Before saving, CompanyOS shows who loses or gains access; changes apply to sessions and API keys on the next request.

  • authos-enterprise-sso

    Per-organization enterprise SSO (OIDC + SAML 2.0) with verified domains, enforcement, JIT provisioning and SCIM 2.0.

    integrator

    Additive contracts in @lssm-tech/lib.authos-spec/operations/sso (auth.sso.*, auth.scim.*). The authos-better-auth bridge gains a runtime-wired sso plugin id backed by @better-auth/sso 1.7.5; enabling it closes the plugin's provider-management endpoints over HTTP (hosts call auth.api after their own authorization), turns off the plugin's organization auto-provisioning, and installs a validateUserInfo gate that checks the OIDC nonce before the host policy and passes the verified ID token claims / SAML attributes through for the host's identity-provider MFA check (ssoClaimsAssertMfa, SSO_MFA_REQUIRED). OIDC client secrets are encrypted at rest by withSsoSecretEncryption (an adapter wrapper keyed by the auth secret). Hosts own provider trust (domainVerified), domains, enforcement and provisioning. Identity provider create/update/delete, settings update and SCIM token issue/rotate declare the recent-authentication errors and a transient password; auth.role.delete 1.1.0 adds ROLE_IN_USE_BY_SSO. module.auth-os adds OrganizationSsoAdapter (sensitive calls take an optional step-up password), useOrganizationSso (step-up prompt state), OrganizationSsoPanel, SsoStepUpDialog and SsoSignInForm.

    customer

    Owners and admins can open Organization → Single sign-on, connect Okta, Entra ID, Google or any OIDC/SAML identity provider, verify their email domain with a DNS record, require SSO for that domain (owners keep a recorded break-glass sign-in), create members on first sign-in with a default role, and sync people and groups with SCIM. People sign in with "Continue with SSO". Removing someone in the identity provider ends their CompanyOS sessions and API keys immediately. By default CompanyOS trusts the identity provider for multi-factor authentication and does not ask for its own second factor after SSO; owners can instead require MFA from the identity provider, and sign-ins without it are refused. Changing identity providers, the sign-in policy or SCIM tokens asks for your password if you signed in more than 10 minutes ago.

  • authos-local-disposable-custody

    PROPOSED_NOT_ADMITTED additive local immutable OS custody review and private native composition, preserving V1 and mandatory runtime qualification.

    maintainer

    V1, native signing and current canonical SQL review/policy locks remain. Local V2 requires exact security-owner admission and real Windows OS, native issuance, SQL revocation and physical cleanup qualification. No source test creates runtime authority or production enablement. Compatible root registry bindings retain all inherited contract instances and select the existing domain authority union without policy changes.

  • authos-organization-page

    Complete the AuthOS Organization page with profile editing, server-enforced membership guardrails, a leave flow, and honest settings.

    integrator

    OrganizationSettings drops its dead Manage/Configure and invitee accept/decline props in favour of onUpdateProfile, onManageInvitations, and onLeaveOrganization, and needs currentUserId to offer member controls. useOrganizationSettings reports mutation failures in actionError. Better Auth hosts get the organizationGuardrails plugin automatically with the organization plugin.

    customer

    Organization owners and admins can rename the organization; the sole owner can no longer demote or remove themselves, members leave through a confirmed flow, and the page no longer promises SSO, domains, branding, or teams.

  • authos-personal-api-keys

    Personal, read-only, organization-bound AuthOS API keys with one-time reveal, expiry, rate limits, and live grant checks.

    integrator

    New additive contracts auth.apiKey.{list,options,create,revoke} and the AUTH_API_KEY_SCOPES catalog in @lssm-tech/lib.authos-spec/operations/api-keys. Hosts implementing API keys must derive their route allowlist from the catalog, store only hashes, and re-check the owner's grant on every request. module.auth-os adds the ApiKeyAdapter port, useApiKeys, and ApiKeysPanel.

    customer

    Create personal API keys under Account → API keys to read CompanyOS workspace status, evidence, or your OPA daily operations from scripts. Keys are shown once, expire (90 days by default), and stop working immediately when revoked or when you lose access to the organization.

  • authos-subject-crosswalk

    Resolve the canonical principal from a verified admitted pairwise product subject.

    integrator

    The new subject-crosswalk subpaths expose an identity-owned server-side resolver and adapter. They do not issue tokens, change grants, or authorize an operation.

  • billing-01b

    Shared subscription-store conformance subpath in billing runtime and Stripe test-mode subscription webhook and snapshot mapping in provider-payments (BILLING-01b).

    integrator

    Configure Stripe price bindings (price id to plan key, version and interval), scope resolution and the event source, set STRIPE_TEST_WEBHOOK_SECRET, and feed receiveStripeTestModeSubscriptionWebhook results into applySubscriptionStateEvent. After an unknown outcome, fetch subscription listings and pass stripeTestModeSubscriptionSnapshot output to reconcileSubscription. Live mode is refused.

    maintainer

    Hirly lineage tryhirly/hirly@f19b041 backend/server.py (stripe_webhook, _subscription_period_timestamp, _reconcile_stripe_subscriptions_once). Durable adapters run the shared suites from @lssm-tech/lib.billing-runtime/subscriptions/durable/conformance.

  • brand-01a-governance-rows

    Career brand, Fairelio and Hirly disposition rows in the LSSM OS and AuthOS governance catalogs; draft applications hidden on passport pages.

    maintainer

    resolveLssmProductScopes now also publishes app_tafio, app_jobrally, app_crossrole, app_lettercase, app_dunbonpas and app_fairelio scopes; the new relying parties are disabled in production and the applications are draft, so no sign-in is enabled. Markets are recorded as market.eu / market.fr policy refs. The Tendframe callback already in the catalog is now expected by the relying-party reconciliation and store tests.

  • brand-01b-portfolio-registry-rows

    Tellshift, Patio, GTM, Taketide and Sarla rows in the LSSM OS and AuthOS governance catalogs, with status-gated governed exchange bindings.

    maintainer

    AUTH_OS_ECOSYSTEM_APPLICATIONS gains app_tellshift, app_patio, app_gtm_learning_loop, app_taketide and app_sarla (draft, contract-only); AUTH_OS_ECOSYSTEM_RELYING_PARTIES is unchanged. New exports through ./ecosystem-catalog: AUTH_OS_GOVERNED_EXCHANGE_ENTRIES, AUTH_OS_GOVERNED_EXCHANGE_BINDING_ROWS, AUTH_OS_GOVERNED_EXCHANGE_BINDINGS, AUTH_OS_GOVERNED_EXCHANGE_CATALOG, AuthOsGovernedExchangeBindingSchema, buildAuthOsGovernedExchangeBindings, resolveAuthOsGovernedExchangeBinding(In) and two DocBlocks. The LSSM OS catalog has 31 products and 39 bindings; the derived firstPartyConsumerRefs of authos, communicationos, companyos and connect gain the new dependants. Consumers that iterate applications see five more draft rows.

  • brand-01f-authos-app-path-rules

    AuthOS ecosystem origin routes declare required appPathPrefixes and expose pure app-path rule helpers.

    maintainer

    AuthOsEcosystemOriginRouteSchema and AuthOsEcosystemOriginRoute require appPathPrefixes (single lowercase leading-slash segments, unique, never /api). New exports: AUTH_OS_ECOSYSTEM_APP_PATH_PREFIXES, AuthOsEcosystemAppPathRule, listAuthOsEcosystemAppPathRules, matchesAuthOsEcosystemAppPath. Breaking (D-088) only for consumers that build or parse route objects; readers of the catalog are unaffected.

  • canonical-delivery-policy-contracts

    Own deterministic delivery policy contracts in LSSM OS Spec

    integrator

    Legacy delivery paths share canonical policy contracts without changing execution authority.

  • canonical-durable-queue-primitives

    Preserve pure queue declarations through canonical orchestration ownership

    integrator

    Queue declarations and predicates retain exact singleton identity while Builder references the canonical digest-reference schema.

  • canonical-lssmos-configuration-models

    Expose the existing complete LSSM OS configuration declaration family through its canonical Spec owner.

    integrator

    Existing imports preserve tuple identity and full configuration types without changing runtime policy behavior.

  • career-taketide-scoped-foundation

    Add scoped Career cockpit composition and fail-closed Taketide tracking and campaign guards.

    integrator

    Use the existing job-application experience entrypoint for the verified cockpit projection and the owned creator/tracking runtime seams for no-effects acceptance.

    maintainer

    Product host composition, scoped persistence and native migration rehearsals remain separate. The new seams do not grant publishing, payment or candidate command authority.

  • cli-bun-windows-glob-queue

    Serialize overlapping filesystem adapter glob traversals under Bun on Windows.

    integrator

    Bun on Windows schedules glob calls sharing an adapter in FIFO order without narrowing discovery.

  • cli-catalog-workspace-candidate

    The adoption catalog loader reads the catalog package's own catalog.json from the workspace.

    maintainer

    In the ContractSpec monorepo, can-help catalog status now reports the tracked workspace catalog as an installed, non-degraded source instead of the CLI-embedded fallback.

  • cli-host-runtime-extraction

    Extract shared CLI composition and neutral host assembly without host-to-host dependencies.

    integrator

    Existing custom hosts retain automatic canonical actions; new portable declaration entries support explicit action suppliers.

  • cli-inline-ai-state

    Own neutral per-program inline AI bindings in cli-runtime.

    integrator

    Existing bundle functions retain exact host types and mutable reference identity.

  • cli-shared-command-helpers

    Own existing generic command input and error helpers in CLI runtime.

    integrator

    Existing imports forward to the same implementations with unchanged signatures and behavior.

  • cli-workspace-parsing-runtime-closure

    Move generic workspace parsing, rendering, diff, snapshot, impact, and DocBlock extraction into canonical CLI runtime leaves with compatible workspace forwards.

    integrator

    CLI packs can use the existing parser and renderer without depending on the workspace module.

  • close-out-harden-store-parity

    Operator-auth store parity (stale-claim takeover) and one strict SupportOS origin validator

    integrator

    InMemoryOperatorAuthRepository lets a new claim take over a processing invitation claim that is at least 5 minutes old, matching durable stores. The superseded claimant can no longer complete or release; expiry and invitee lockout still refuse a takeover.

    maintainer

    SupportOS authority origins and endpoint URLs are validated on the raw configured value; a value with surrounding whitespace, an empty query or fragment, userinfo, or a non-canonical host fails startup instead of being repaired by the URL parser.

  • cmp-cli-runtime-bridge-ports

    lib.cli-runtime reaches the integration runtime and the TypeScript tool through runtime ports bound by bundle.workspace, deleting both lane-12b CLI bridges (10 edges)

    customer

    No change for CLI or editor users. The contractspec and sdd bins and the app CLI create their programs through the workspace composer, which binds the TypeScript, environment and Connect channel ports before any command runs. The VS Code extension and the JetBrains bridge import the bundle.workspace root entry, which binds the same ports on import. Connect hook entries pass the channel explicitly.

    integrator

    bundle.workspace behaves as before: importing its root entry binds every port, so library callers of runDoctor, runCiChecks, the validators, the test service, the module-loader and env-template forwards and the Connect services need no change. Code that calls lib.cli-runtime DocBlock analysis, the env-example templates, the Node fallback of loadAuthoredModule or createConnectControlPlaneRuntime, or the module.workspace DocBlock analysis forwards (analyzePackageDocBlocks, buildPackageDocManifest, extractModuleDocData), without importing bundle.workspace or creating a ContractSpec CLI program, must bind the matching port first with bindCliRuntimePorts from @lssm-tech/lib.cli-runtime/ports/runtime. An unbound port throws CliRuntimePortError (code missingHostBinding) naming the port; loadAuthoredModule rethrows it unchanged. Public signatures accept the same arguments as before. lib.cli-runtime no longer installs integration.runtime or lib.typescript-runtime.

    maintainer

    The lane-12b-cli bridge ledger is empty (cli-runtime-runtime-link and cli-runtime-typescript-tooling are deleted). Tests that run the real suppliers bind them explicitly; the Connect link and replay tests in cli-runtime use a deterministic channel fake, and the real channel, environment and TypeScript bindings are exercised by bundle.workspace src/cli/program/runtime-ports*.test.ts and, from a fresh unbound process through the root entry, src/index.runtime-ports.test.ts.

  • cmp-fix-local-qualification-fixtures

    Normalize workspace library-definition paths consistently across host platforms

    integrator

    Library-definition filtering normalizes Windows and POSIX separators before both library exclusions and allowed authored-spec exceptions. Windows and UNC paths classify consistently on POSIX hosts; signatures and patterns are unchanged.

  • cmp-identity-rp-catalog

    The AuthOS ecosystem catalog marks the CompanyOS relying party production-enabled under its recorded security review, keeps it invite-only and refuses production entries without review evidence

    integrator

    AUTH_OS_ECOSYSTEM_RELYING_PARTIES now reports rp_companyos_web (client companyos-web) with productionEnabled true and securityReviewRef owner-decision-2026-10-20-connect-lssm-security-review. It keeps inviteOnly true, and the other three registrations stay production-disabled. The schema, existing exports and subpaths are unchanged; AuthOsEcosystemRelyingPartiesDocBlock is a new export.

    maintainer

    The catalog throws at load when a registration is production-enabled without a non-empty securityReviewRef, so production admission cannot be declared without review evidence. Runtime admission still comes from each host's reviewed environment binding (LSSM_RP_ENABLED, LSSM_RP_SECURITY_REVIEW_REF, LSSM_RP_CLIENT_SECRET for CompanyOS) and from the identity authority's reconciled client and product entitlements.

  • cmp-personal-meeting-context

    PersonalOS companyos_meeting_context consent consumer, the consented CompanyOS meeting-context binding and adapters for every follow-up target

    customer

    A PersonalOS consent can now name "CompanyOS meeting context". While it is current, OPA meeting preparation may read the few fields you declared for it, privately and only for you, and an approved meeting follow-up can land in your private PersonalOS memory. Revoking or letting the consent expire ends every later read and stops new memory entries. Nothing is read or written until the operator connects PersonalOS.

    integrator

    @lssm-tech/lib.personal-os-spec adds the companyos_meeting_context consent consumer (additive enum member), ./meeting-context-consumer (read request, declaration, projection with consent and retention window, granted/withheld answer, PERSONAL_MEETING_CONTEXT_ROUTES_V1) and ./meeting-memory-intake (entry and stored/withheld receipt). @lssm-tech/lib.personal-os-runtime adds answerPersonalMeetingContextReadV1 and decidePersonalMeetingMemoryIntakeV1, pure host decisions on the host clock. The opa-meeting-context-bridge adds ./personalos-meeting-context (client plus HTTPS transport). A consumer that exhaustively matches PersonalConsentConsumerV1 must handle the new member.

    maintainer

    The CompanyOS API binds createProductionPersonalContextPort in place of UNBOUND_PERSONAL_CONTEXT_PORT; it stays fail-closed until OPA_PERSONALOS_BRIDGE_URL and OPA_PERSONALOS_BRIDGE_TOKEN are set, and AI briefing reads (restrictTo) never fetch PersonalOS. The account ref is companyos:user:<userId>; the PersonalOS host resolves it to its own subject. knowledge:personalos-context never caches results; every preparation/reproof read revalidates current consent, expiry, revocation and retention. Follow-up adapters now exist for personalos_private_memory, hcircle_space and pactena_workspace; the last two answer adapter_unavailable until a product host is bound (B231, B240). No migration, no new cron, no new table.

  • cmp-product-channel-composition

    Product notification preference centers and producers on CommunicationOS, plus Pactena and PersonalOS channel composition

    customer

    Messages sent from a Pactena conversation now reach CommunicationOS; the send previously failed. Notification preferences and calendar import are prepared but stay unavailable until they are switched on for your workspace.

    integrator

    @lssm-tech/lib.notification/product-channels composes a product preference center and producer over CommunicationOS routing. Hosts supply a ProductNotificationHostV1 (CommunicationOS routing port, opaque route directory, eligibility evidence and delivery admission) and a revision-CAS ProductNotificationPreferenceStoreV1 keyed by product, person and full scope (productNotificationPreferenceKeyV1). Mint consent evidence from the authenticated session with mintProductNotificationConsentRefV1. The producer never dispatches: delivery happens only after the host admission accepts the authority-free prepared delivery. Use ./product-channels/testing in tests only.

    maintainer

    The Pactena BFF forwards POST /api/v1/communication-os/communication/message/send/v3.0.0 to the CommunicationOS contract route after checking the app origin, matching idempotency-key header and body key, the session-derived workspace and space, and a 64 KB limit enforced while streaming. The preference and calendar intake mutations require the app origin and x-csrf-token equal to the session id (added to the CORS preflight allow-list), cap their bodies, and the BFF mints consent refs from the session. A stale preference revision answers 409 idempotency_conflict. Pactena's OPA owner scope derivation moved to pactena-owner-scope.ts unchanged so calendar intake and meetings share it. PersonalOS effect executors check the RT-008 life-admin activation before decrypting state and report provider errors as indeterminate; a notification effect leased before its scheduledAt returns deferred with the availableAt to release the lease to.

  • codemods-chrome-marker-guide-path

    The CodeBlock codemod chrome marker points at the codemods package migration guide.

    maintainer

    Migrated CodeBlock callsites that dropped chrome props carry a RICH_REF_CHROME_RESTORED comment that names packages/tools/contractspec-codemods/MIGRATION.md (section "CodeBlock chrome props") for the re-add patterns. The root MIGRATION.md and the package guide now document that marker instead of the retired TODO(rich-ref migration) anchor.

  • communication-os-client-session-ownership

    CommunicationOS client session, delivery, community and live-room behavior moves to its owners

    integrator

    New subpaths expose the shared CommunicationOS client session engine and durable outbox, the bounded live workspace projection, the outbound delivery dispatcher, the Discord installation lifecycle, Discord community analysis and seven-day record rules, the canonical preference vocabulary and the embedded live-room controller. Hosts inject transport, storage and redirects.

    maintainer

    DefaultCommunityRedaction is stricter (URLs and opaque tokens are redacted). CommunicationOS direct-session grants for owners and administrators now carry forms.platform and supportos.case.read; the standalone shell no longer adds capabilities client-side.

  • communication-os-outbox-payload-sealing

    Shared scope-bound outbox payload sealing primitives; CommunicationOS mobile seals its outbox

    integrator

    The session-engine subpath exposes a platform-neutral outbox payload cipher port, scope-bound additional data, the v2 envelope codec and a strict UTF-8 codec. Hosts keep the AES-GCM adapter and key custody; CommunicationOS desktop (WebCrypto) and mobile (expo-crypto) both use them.

  • communicationos-oauth-host-issuer-return

    Host-exchanged CommunicationOS sessions carry the signed host issuer, so provider OAuth callbacks started from CompanyOS return to the CompanyOS origin configured in COMMUNICATION_OS_OAUTH_HOST_ORIGINS.

    integrator

    createCommunicationAccessTokenIssuer().issue accepts an optional hostIssuer, signed as the hostIssuer claim. The host session exchanger sets it to the verified host assertion issuer. The verifier returns hostIssuer on CommunicationAccessPrincipal only for a non-empty string claim; issuer remains https://api.hcircle.app. hostIssuer is display and return routing only, never authority.

    maintainer

    COMMUNICATION_OS_OAUTH_HOST_ORIGINS keys are host-exchange issuers (the COMMUNICATION_OS_COMPANYOS_ISSUER value), for example {"https://companyos.hcircle.app":"https://www.companyos.run"}. Never map the shared access issuer https://api.hcircle.app. Sessions without hostIssuer, including host sessions minted before the deploy (5 minute TTL), fall back to COMMUNICATION_OS_WEB_ORIGIN. No environment variable is renamed.

    customer

    Connecting a provider from CommunicationOS inside CompanyOS returns to CompanyOS instead of the standalone hCircle chat shell.

  • connect-hook-package-turbo-root

    Connect hooks resolve the repository root from inside packages that carry their own turbo.json

    maintainer

    findWorkspaceRoot (workspace/detection/roots.ts) skips a turbo.json whose top level has an extends key, because that file configures one workspace package rather than the monorepo. resolveWorkspace therefore merges the repository .contractsrc.json, and Connect evaluates hooks run from any package directory instead of failing closed with LSSM_HOOK_AUTHORITY_DENIED.

  • connect-run-mode-agent-guidance

    Agent guidance for Connect run modes in the consumer agent pack and generated AGENTS/USAGE guides.

    integrator

    Agents in consumer repositories learn that Connect host hooks follow the host permission mode, that a hook deny carries a reason to follow rather than retry, that contractspec connect mode show explains the active mode, and that granting a mode or editing hook settings is operator-only.

  • connect-shell-policy-hardening

    Connect shell policy denies compound, normalized-git and wrapped forms of a denied command, and governs the Claude Code PowerShell tool.

    integrator

    Connect command policy evaluates every command a shell line runs and lets the strictest verdict win. cd <dir> && git push --force, git -C <dir> push -f, git push origin +ref, bash -c "...", pwsh -Command "..." and wrapped forms are denied at the same destructive or configured deny rule as the plain command; an allow rule now needs every executed command to be allowed. Heredoc text fed to cat/python -, commit messages and echo/grep arguments are data and no longer denied. Honest callers keep their verdicts.

    maintainer

    The generated Claude Code PreToolUse shell hook matches Bash|PowerShell; Codex and Cursor already deliver every shell call through their shell-execution event. analyzeShellCommand and shellCommandForms are exported from the Connect services entry of @lssm-tech/lib.cli-runtime. The W5 trial probe gains --extended and --permission-mode.

  • content-01d-analysis-replay

    Content analysis re-authorizes replays, enforces duration and cost budgets, validates evidence against decomposed segments and resumes interrupted runs.

    integrator

    ContentAnalysisRuntimeDependenciesV1 requires a budget port (reserve idempotent per receiptId, settle idempotent per reservationRef). The repository save must be an upsert by receipt id. Replays are re-authorized and return the current decisionRef. Providers may report costMicros. Major bump rationale: a new required dependency and changed replay ordering; the only in-repository consumer is a pure re-export.

  • content-01f-analysis-durable-repository

    Content analysis gains a durable claim/fence repository with a terminal-event outbox, an unsettled-reservation sweep, a SQL store and Gemini usage/billed-cost reporting.

    integrator

    Hosts composing runContentAnalysisV1 supply a claim/lease/fence repository (SqlContentAnalysisStore or an equivalent), a positive integer leaseMs at least as long as the model deadline, and run relayContentAnalysisOutboxV1 and sweepContentAnalysisReservationsV1 per tenant workspace. Gemini clients return { output, usage?, billedCostMicros? }. Major bump rationale (D-088): the repository port and the Gemini client port change shape; the only in-repository runtime consumer is a pure re-export and the Gemini content-analysis adapter has no in-repository consumer.

  • content-analysis-canonical-owner

    Canonical content-analysis declarations now live in their content domain owner with legacy forwarding compatibility.

    integrator

    Existing legacy imports remain supported; narrow domain contract imports share the same canonical declarations.

  • content-generation-spec-extraction

    Content-generation contract definitions move from the contracts-spec compatibility facade to the content domain spec @lssm-tech/lib.content-analysis-spec with identity-preserving forwards

    integrator

    Import content-generation contracts from @lssm-tech/lib.content-analysis-spec/content-generation/<leaf>; every former @lssm-tech/lib.contracts-spec/content-generation/<leaf> import keeps working and resolves to the same objects.

  • customer-support-csat-owner

    Canonical CustomerSupport runtime contract ownership with compatible legacy forwards

    integrator

    Import complete CustomerSupport contracts and synchronous CSAT input digest from their canonical owner; existing Legacy imports preserve behavior and singleton identity.

  • customer-support-runtime-shared-module-instances

    Customer support runtime subpaths share module instances, restoring 4 facade re-exports

    integrator

    Values imported from different @lssm-tech/lib.customer-support-runtime subpaths are now the same instances, so support authority errors pass instanceof across subpaths, and the compatibility facade's root and ./customer-support entries again expose the SupportAuthority*UnavailableError classes and assertSupportPlatformAuthorityConformance.

  • cving-01b-cv-ingestion-stages

    CV ingestion stages (chronology with source spans and confidence, typed candidate question drafts through the existing question owner, de-duplication against confirmed facts, candidate-private evidence-graph read model, qualification-gated OCR and fact-extraction ports).

    integrator

    New subpaths contracts/cv-ingestion-{chronology,chronology-audit,questions,questions-answers,dedup,evidence-graph,ports} and headless/cv-ingestion-{questions,stages}. Compose createCvIngestionStagesV1({ confirmedFacts, extractor }) as the optional CvIngestionDepsV1.refinePlan; without it the CVING-01a plan is unchanged. Question delivery needs an explicit application target and the composed question port; otherwise drafts stay held in the sealed plan.

    customer

    Facts read from a CV remain proposals. Gaps, overlaps, undated items and conflicts with already confirmed facts are surfaced as questions instead of guesses; nothing is auto-confirmed and no OCR or model provider is called.

    maintainer

    Question text and reasons are message keys (cv.question.*) for brand i18n. OCR and model adapters are not selected (qualified false); classification (donor A4) is not ported.

  • cving-01c-profile-questions

    Profile-scoped candidate questions for CV ingestion (D-181), answer-driven re-run and re-seal of the CV stage plan, candidate-scoped confirmed-facts read for de-duplication and managed composition of the CV stages.

    integrator

    New subpaths runtime contracts/candidate-question-profile and headless/cv-ingestion-questions-answers; store candidate-questions-profile, candidate-questions-profile-migration, candidate-questions-profile-reseal and cv-ingestion-confirmed-facts. Apply migration 0032_candidate_profile_questions.sql (generated verbatim from candidateProfileQuestionsMigrationSqlV1). The managed CV deps now set refinePlan; createManagedCvProfileQuestionDepsV1 composes delivery and answers.

    customer

    CV questions can be answered before any job application. Answers only refine the CV reading (dates, confirmations); facts stay proposals until the candidate confirms them. Facts already confirmed are not proposed again.

    maintainer

    The sealed plan with stages was bounded by the 64 KiB vault payload (measured largest = 26 proposed writes); CVING-01c2 (D-184d) lifts that limit by re-projecting the evidence graph on read and splitting sealed documents into ordered parts, so the largest CV at the 40 000-character text limit now proposes. OCR and model ports stay unqualified and unwired.

  • cving-01c2-vault-bound

    CV proposal plans and stages sealed as bounded, ordered vault parts with the evidence graph re-projected on read (D-182b); the largest synthetic CV at the 40 000-character limit proposes.

    integrator

    No new subpath, no migration. The runtime headless/cv-ingestion-stages subpath adds sealableCvStagesV1 and withProjectedCvEvidenceGraphV1, and stage output now carries the extractor identity. The store seals the plan head profile-evidence:cv-proposal:<key> as a manifest, the stages under profile-evidence:cv-proposal-stages:<key>, and parts under profile-evidence:cv-proposal-part:<digest>:<i>, all in the namespace that candidate erasure (0022) already tombstones. Heads sealed before this change are read as before; their first re-seal converts them.

    customer

    CVs up to the full text limit can now be read into profile proposals. Before, a CV with more than about 25 items was refused at that step.

    maintainer

    The vault payload bound (64 KiB) is unchanged. Sealed documents are split into at most 16 parts; beyond that, propose fails closed with nothing written. A read with a missing or altered part fails closed (JOB_APPLICATION_PROFILE_INTERVIEW_MATERIAL_UNAVAILABLE).

  • cving-01d-profile-question-surfaces

    Candidate surfaces (REST/SDK/MCP/CLI) to list and answer the profile-scoped CV ingestion questions (D-181), wired in the operation handler and the managed composition, with a two-connection PostgreSQL proof of the profile question lock and currency.

    integrator

    New operations job-application.cv-ingestion.questions.list (GET /cv-imports/:cvImportId/questions, candidate_read) and job-application.cv-ingestion.questions.answer (POST /cv-imports/:cvImportId/questions/answers, candidate_admin, mutation envelope with expectedRevision = payload.textRevision). New runtime subpaths contracts/cv-ingestion-profile-questions, contracts/cv-ingestion-profile-questions-transport and headless/cv-ingestion-profile-questions-dispatch. The managed handler composes them only when profileEvidenceKey and cvOriginalCustody are both present. Per D-184a and D-185c, job-application.question.ask and job-application.question.answer refuse profile-context payloads with JOB_APPLICATION_QUESTION_PROFILE_CONTEXT_REQUIRES_CV_ROUTE (HTTP 422). CV ingestion creates its own profile questions and accepts answers via job-application.cv-ingestion.questions.answer. No migration.

    customer

    CV questions can be seen and answered before any job application. Answers only refine the CV reading; facts stay proposals until the candidate confirms them.

    maintainer

    The store Docker conformance runs conformance/profile-question-concurrency.sh (two runtime-role connections on the profile advisory lock; stale revision refused). Both operations are classified candidate-private and stay off every feature until the CV candidate surface lands. No outbox event (profile questions are candidate-private, D-181).

  • cving-01ui-context

    Add candidate-private source context to revision-pinned CV profile question lists.

    customer

    When CV questions have the same wording, a short excerpt can identify the specific education or experience item.

    integrator

    A revision-pinned CV question list can return optional sourceContext. Each item has up to two verified source spans with a page number and a plain-text excerpt of at most 160 UTF-16 code units. Treat items as private and exclude them from logs, telemetry and shared caches.

    maintainer

    The list reads at most one sealed proposal and requires matching candidate, import, revision and quote provenance before projecting context. No migration is required.

  • cving-01ui-http

    Protect candidate CV question responses from HTTP caching and preserve declared safe refusal codes.

    integrator

    The CV import metadata, question list and answer endpoints send Cache-Control private, no-store. The question endpoints project exact declared error codes with their contract status; other domain errors remain redacted.

  • cving-01ui-month

    Accept month precision for undated-start CV profile answers.

    customer

    Answer the CV undated-start question with a month and year. Chronology places the affected entry using month precision.

    integrator

    job-application.cv-ingestion.questions.answer accepts YYYY-MM for the profile date question whose key is cv.question.undated_item. Legacy YYYY-MM-DD answers retain their stored values. Generic application date questions and other profile date questions require a real calendar day.

  • d117-datamap-01

    Add the ecosystem data-ownership map catalog and validator to lssm-os-spec (D117-DATAMAP-01).

    integrator

    Import validateLssmDataOwnershipMapV1 and the projection, store and discovery helpers from @lssm-tech/lib.lssm-os-spec/catalog/data-ownership. The map is catalog data; planned, pending and unknown owners and stores are explicit and are not completed ownership. Pass brandIdentifiers to the validator to refuse brand names in owner or store packages.

    maintainer

    Owners follow design section 7.1 and decisions D-024, D-112, D-117, D-122 and D-124 (A7 is published by the personal-agency owner, planned by PEOPLE-01a). checkBrandComposition refusal case 7 and the D117-GATE-01 data-ownership guard are the intended consumers.

  • d117-fix-01-brand-neutral-owners

    Brand-neutral domain owners (D117-FIX-01) - company.offering@1 projection, consumer-isolated OSINT deployment row, catalog-driven founder contexts and organization slugs, neutral recruiting and creator copy.

    maintainer

    Breaking points: (1) projection id patio.company_offering.v1 becomes company.offering.v1 (catalog entry company.offering@1, COMPANY_OFFERING_CATALOG_ENTRY_REF); (2) error codes PATIO_PROJECTION_* become COMPANY_OFFERING_PROJECTION_* (osint spec, module and osint-store projection source); (3) Patio* names stay only as deprecated aliases for one release (CompanyOfferingProjectionV1 and the COMPANY_OFFERING_* names are canonical); (4) OSINT capability row osint.operations.hirly-france is replaced by osint.operations.consumer-isolated-deployment; (5) FOUNDER_CONTEXT_IDS is removed; (6) FounderContextId and CanonicalOrganizationSlug become branded types validated against a registry or manifest; (7) ORGANIZATION_BOOTSTRAP_PHASES is a readonly OrganizationBootstrapPhase[] (no longer a tuple); (8) the listFounderContextRegistryIssues and normalizeContextAlias implementations moved to context-registry, and the alias resolvers take a registry. talent-spec and creator-operations-spec change DocBlock copy only.

  • d117-fix-01b-governed-seed-catalogs

    Brand-specific OSINT deployment profiles, founder-context and organization-bootstrap seeds, seed-map paths and donor provenance move to governed lssm-os-spec G catalogs; domain and integration owners become brand-neutral.

    integrator

    lib.osint-runtime removes HirlyFranceInternshipApprenticeshipProfileV0 and HirlyFranceInternshipApprenticeshipProgramV0; resolveOsintDeploymentProfileV0 and resolveKnownOsintDeploymentProfileV0 take a required registry built by defineOsintDeploymentProfileRegistryV0 (refuses duplicates, dangling references and invalid isolation fields with OSINT_DEPLOYMENT_PROFILE_REGISTRY_INVALID). integration.osint-managed-runtime createManagedOsintOperationHandlerV0 requires that registry. lib.lssm-os-spec adds ./catalog/osint-deployment-profiles, ./catalog/founder-contexts, ./catalog/organization-bootstrap and ./catalog/donor-sources and removes the three brand-named seed-map path constants in favour of SEED_MAP_CATALOG_INDEX_V1 and seedMapCatalogPathV1(mapId) (SEED_MAP_UNKNOWN). lib.companyos-spec reads FOUNDER_CONTEXT_REGISTRY_SEED_V1 and ORGANIZATION_BOOTSTRAP_SEED_V3 from the G catalogs with unchanged values, ids, digests and receipt keys; OrganizationSeedProfileId is derived from the catalog keys (same union). integration.job-sources DONOR_PINS_V1 entries replace repository with the opaque sourceRef 'donor-source.career-b2c-focused@1' (the serialized reconciliation report digest changes). bundle.creator-platform readiness owner 'hirly' becomes 'host_product' and capability id hirly-export-cutover becomes legacy-host-export-cutover. lib.creator-operations-spec DocBlock copy and integration.job-application-browser matrix copy are brand-neutral (patch). A catalog row grants no collection, provider or network authority.

  • data-exchange-core-organization-grant

    Add organization-subject governed grant primitives with contract or legitimate-interest lawful bases and tenant-bound grants.

    integrator

    New leaves governed/organization-grant, -issue, -subject and -validation. Organization offers carry projectionId and projectionSchemaVersion. Hosts derive subject references from a trusted binding with an injected hash (keyed HMAC recommended), build grants with createGovernedOrganizationGrant and validate them with validateGovernedOrganizationGrant({ ..., subjectBinding, sha256Hex }) before storing; governedOrganizationOfferBindingRefusals checks an offer against its catalog entry.

    maintainer

    Primitives only. No host issuance, entitlement or tenant-administrator check, gateway composition, catalog organization offers or stored source-rights binding is added. The person-consent grant, offer and enum are byte-identical.

  • decisioning-decision-runtime-extraction

    Decisioning contracts and ports move from the contracts-spec compatibility facade to @lssm-tech/lib.decision-runtime/contracts with identity-preserving forwards

    integrator

    Import decisioning contracts and ports from @lssm-tech/lib.decision-runtime/contracts[/<leaf>]; former @lssm-tech/lib.contracts-spec/decisioning imports keep working with identical objects.

  • dev-authos-canonical-lifecycle

    PROPOSED_NOT_ADMITTED additive canonical development lifecycle, native provider registration, durable journal and secret custody composition.

    maintainer

    Exact native reserved-sub semantics and canonical policy are preserved. Actual review/issuer/key custody, same-target role/lock/schema admission, adoption, contract validation, consumer tests and runtime qualification remain required and unexecuted. No production topology is changed. Exact resource configuration drift denies; persisted credential resume requires genuine native proof and currently quarantines. Native callback transaction locks do not establish issuance atomicity.

  • dev-authos-resource-authority

    PROPOSED_NOT_ADMITTED private contract-first development resource JWT/workload registration and durable scoped OSINT authority receipt/revocation preparation. Registration rejects before effects without actual canonical reviewed-profile verification.

    maintainer

    Optional source preparation preserves existing defaults. Actual adoption, contract validation, security review, canonical lifecycle integration and registered issuer/runtime qualification remain required and unexecuted.

  • execution-declaration-orchestration

    Give execution and coordination declarations a canonical pure owner while retaining the execution runtime.

    maintainer

    Pure lane, plan, evidence, collaboration and program models use the orchestration spec owner; runtime execution stays separate.

  • execution-lanes-evidence-backed-completion

    Team tasks complete only with their declared evidence, and team runs finalize only with an independent verifier

    integrator

    TeamBacklogTaskSpec accepts an optional requiredEvidence list of evidence classes. Completing such a task requires fresh, same-run bundles attached to the task that cover every declared class. TeamTaskRecord gains optional claimHistory and completedBy. Verifier approvals decided by a task participant (a current or reclaimed claimant, or a principal that claimed, attached work evidence to, or completed a task) no longer count, and newly created code-producing team runs (tasks with writePaths) must keep verificationLane.required set to true. validateTeamRunSpec accepts an optional amend mode that skips that creation-only rule.

    agent

    A worker's self-report or self-signoff never completes a team run. Attach evidence bundles whose classes match the task declaration, and leave the verifier decision to an actor that did no task work: it never claimed, attached work evidence to, or completed a task, even under a lease that was later reclaimed.

  • explicit-shared-library-entries

    Preserve shared library exports with explicit package entries

    integrator

    Supported imports remain stable while private files stop becoming public entries.

  • fo2-s07-activation-migration

    PersonalOS activation carry-forward migration, live host-binding probes, gated health/life-admin routes, encrypted health routine and FinanceOS company tax handoff

    integrator

    PersonalOS hosts must inject domainActivation whenever finance, health or life-admin ports are composed; the server refuses to start otherwise. Use createPostgresPersonalDomainActivationHost in production and run the carry-forward backfill before enabling the gate.

    maintainer

    Encryption and authority bindings are proven by live probes, not function presence. Health and life-admin routes are gated; export and erasure remain available after consent withdrawal.

  • fo2-s07-private-domains

    PersonalOS activation boundary, tax recovery dossiers, scoped finance review and subject-private health routines

    integrator

    PersonalOS hosts can inject a domainActivation gate and activation-gated finance into createPersonalOsProductionApiInput. Finance without the gate is a composition error. Blocked activation returns a stable no-detail reason and never touches state or crypto.

    maintainer

    New additive contracts PersonalDomainActivationV1, PersonalTaxRecoveryRequestV1/DossierV1, PersonalTaxObligationTrackV1, PersonalFinanceCompanyProjectionGrantV1 and PersonalHealthRoutine*V1 with same-file DocBlocks; runtimes add the activation evaluator, dossier builder, obligation transitions, company projection resolver, routine proposer and disclosure guard.

  • fo2-s10-support-durable-routes

    Support action custody and resolutions persist in Postgres, resolution operations get HTTP routes bound to the canonical approval runtime, and personal device events ingest read-only into CommunicationOS

    integrator

    Apply migration 0059 before enabling support resolution writers; compose scoped Postgres stores, the Intercom executor and an OperationApprovalPort into the communicationos-api support resolution routes; ingest personal device events only through ingestPersonalDeviceEvents on a device-placed personal_mode connection.

  • fo2-s11-durable-economics

    Durable Postgres agreement, mandate, collection, pilot-acceptance and termination stores with non-superuser RLS proof

    integrator

    Persist collection through ServiceCollectionStorePort (receiveServicePaymentEvent for verified webhooks, issueStoredServiceInvoice under an approval receipt) and agreement, mandate, pilot and termination state through the new managed-economics ports; in-memory collection store remains for fixtures.

    maintainer

    Migrations 0190–0194 add managed_economics_* tables with forced tenant RLS, grant SELECT/INSERT/UPDATE (never DELETE) on all managed_economics_* tables to managed_companyos_app when that role exists, and revoke every managed_economics_* table and sequence from anon and authenticated when those roles exist.

  • forms-public-not-found-404

    Forms HTTP handler maps typed Forms errors (unknown public token returns 404 form_not_found, not 500)

    integrator

    GET /api/forms/v1/public/:token with an unknown, closed or archived token now returns 404 { error: { code: 'form_not_found', correlationId } } instead of HTTP 500 with an internal message. Other contracted Forms errors on public and protected routes now return the HTTP status declared in formsOperationErrors instead of 500.

    maintainer

    createFormsHttpHandler awaits route handlers inside its try block, so FormsPlatformError rejections reach the error mapper. An optional reportUnexpectedError({ error, correlationId }) hook observes the remaining sanitized 500s; the CompanyOS API logs the correlation id and error name through appLogger. The message is not logged.

  • founder-intelligence-intake-form-blank-defaults

    Board intake form untouched fields are unknown, never invalid (WEB-01-BOARD-HOST)

    integrator

    BoardIntakeForm now passes the blank intake draft (plus participantChoseExport false) as the form default values, so untouched fields stay empty and the participant can export a partially answered intake.

  • governed-organization-production-ports

    Production organization issuance composes real offers, subject-binding and source-rights ports; OSINT owns append-only trusted organization subject bindings; governed bearer env names derive from the AuthOS registry.

    integrator

    New subpaths ./governed/organization-catalog-offers and ./governed/person-grant-rights (data-exchange-core, also in the ./governed barrel), ./organization-offer-lookup (governed-data-postgres; no longer re-exported from ./catalog-store), ./governed-subject-binding-store and ./governed-subject-binding-schema (osint-store; no longer re-exported from ./rights-source-outbox) and ./contracts/governed-subject-binding (osint-spec, also in the ./contracts barrel; not in the public OSINT operation registry or transport bindings). osint-store adds migration 0037_osint_governed_subject_bindings.sql (osint_core.governed_subject_bindings: append-only trigger, forced RLS, runtime roles SELECT and INSERT only). The OSINT API host mounts GET /internal/osint/governed-subject-bindings and POST .../set and .../withdraw; writes answer 403 operator_required until an operator authority is composed, and every route answers 503 subject_bindings_unavailable without OSINT_SOURCE_RIGHTS_DISPATCH_SCOPE. Environment: OSINT host OSINT_GOVERNED_SUBJECT_BINDINGS_READ_TOKEN; identity host LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDINGS_ORIGIN and LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDINGS_READ_TOKEN (without them issuance answers organization_issuance_unavailable:subjects) and the derived LSSM_GOVERNED_<APP>_CATALOG_TOKEN and LSSM_GOVERNED_<APP>_SOURCE_RIGHTS_TOKEN for each active app_<key> registration (the HCIRCLE, PACTENA, COMPANYOS and LSSM_OS names derive byte-identically). No provider, mail or network effect is added.

  • governed-source-rights-lifecycle

    OSINT rights lifecycle emission published through the governed source-rights publisher, the sourceRights.current read and the LSSM OS host source-rights mount.

    customer

    To let OSINT rights decisions revoke dependent grants, set a distinct 32+ character COMPANYOS_GOVERNED_OSINT_RIGHTS_TOKEN (LSSM OS - LSSM_OS_GOVERNED_OSINT_RIGHTS_TOKEN) on the source product host and give the same value to the OSINT rights service. Until it is set the ingress answers 503 osint_rights_ingress_unconfigured. The LSSM OS host uses LSSM_OS_GOVERNED_SOURCE_RIGHTS_* for the publisher and LSSM_OS_GOVERNED_SOURCE_RIGHTS_OPERATOR_USER_IDS with LSSM_OS_GOVERNED_SOURCE_RIGHTS_OPERATOR_SECURITY_REVIEW_REF for operators. A delivery that keeps failing transiently now becomes failed retry_exhausted after 24 attempts and needs an operator re-drive or resolution.

    integrator

    POST /internal/governed-data/source-rights/osint-lifecycle takes one strict osint.source_rights.lifecycle.v0 emission with idempotency-key equal to eventId and x-lssm-application-id naming the host application; it answers 200 recorded or replayed with changeId and revision (basedOnRevision + 1), 409 revision_stale, change_conflict or idempotency_mismatch, 413/422 invalid input, 401 bad bearer, 403 source_application_mismatch and 503 when unconfigured, inactive in AuthOS or unavailable. GET /internal/governed-data/source-rights/current and the operator GET /api/governed-data/source-rights/current return identity.governed.source_rights.current.v1 (unknown, current or withdrawn; permitted uses known, none or unknown; head outbox state). The OSINT runtime exports buildOsintSourceRightsLifecycleEmissionV0 and emitOsintSourceRightsChangeForRequestV0, and applyApprovedOsintRightsRequestV0 accepts an optional sourceRights binding.

    maintainer

    New monolith modules product-governed-source-rights-{current,osint-lifecycle,osint-route,lssm-os}.ts, new osint runtime module rights-source-change.ts and identity spec module governed-source-rights.ts. Their package exports and focusedTests, the CompanyOS app.ts ingress mount and the LSSM OS cron entry are requested from the integration owner. The monolith mirrors the OSINT emission and the AuthOS read shape structurally because it does not depend on lib.osint-runtime. Nothing is logged.

  • governed-subject-scoped-source-rights

    Subject-scoped source-rights refs per organization binding, source-rights outbox operator resolve, worker expiry sweep and the D-160 subjectRef hand-back (osint-store 0038, EXCHANGE-01m).

    integrator

    Behaviour change: organization grant records now carry subject-scoped source-rights refs (osintSubjectScopedSourceRightsRefV0), and an erasure or restriction that resolves to entities no longer touches the base ref; pre-01m base-ref grants are legacy and are revoked only by organization_all (D-163a). New osint-store subpaths ./rights-source-subject-emissions, ./rights-source-subject-schema, ./rights-source-outbox-operator-resolve, ./governed-subject-binding-ref-store and ./governed-subject-binding-port; osint-spec ./contracts/source-rights-outbox-operator (also in the ./contracts barrel; internal service routes, not in the public OSINT registry, D-163b). The OSINT API host mounts GET /internal/osint/source-rights-outbox/attention, POST .../redrive and .../resolve (writes 403 until an operator authority is composed) and POST /internal/osint/governed-subject-binding-refs; without OSINT_SOURCE_RIGHTS_DISPATCH_SCOPE they answer 503 source_rights_internal_unavailable. Environment - identity host: LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDING_REFS_ORIGIN, LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDING_REFS_WRITE_TOKEN; OSINT host: OSINT_GOVERNED_SUBJECT_BINDING_REFS_WRITE_TOKEN (same value), OSINT_SOURCE_RIGHTS_OPERATOR_TOKEN, OSINT_SOURCE_RIGHTS_EXPIRY_SWEEP_OWNER; osint-worker: OSINT_SOURCE_RIGHTS_EXPIRY_SWEEP_SCOPE, OSINT_SOURCE_RIGHTS_EXPIRY_SWEEP_INTERVAL_MS, OSINT_GOVERNED_COMPANY_PROJECTION_READER_ACTOR_ID, OSINT_GOVERNED_COMPANY_PROJECTION_SOURCE_APPLICATION_ID, OSINT_GOVERNED_COMPANY_PROJECTION_MAX_AGE_SECONDS.

  • job-application-account-deletion-consumer

    AuthOS account-deletion governed-exchange consumer for candidate erasure and a destination-specific disclosure caller for submit (additive, not yet composed).

    maintainer

    JobApplicationAccountDeletionConsumerV1.processRights mirrors the governed processRights erasure shape without depending on data-exchange-core; refusals are retryable_failure (the governed worker's max-attempt dead-letter is the terminal path) and unknown failures are indeterminate. The managed account-deletion path now derives its receipt id through jobApplicationAccountDeletionReceiptIdV1 (same derivation as before). submitJobApplicationWithDestinationDisclosureV1 wraps submitJobApplicationV1 unchanged; the disclosure is bound by the pre-reservation check, the dispatch-time effect gate and the effect evidence ref, not by the request or packet digest. Producer binding (EXCHANGE-01k), the subject-binding store and the destination-disclosure store/operation remain open.

  • job-application-authority-expiry

    Reject unparseable expiration timestamps on job application authority decisions.

    integrator

    Managed AuthOS and injected command authority must return a parseable future expiry. Existing valid grants and command bindings are unchanged.

  • job-application-candidate-erasure

    Candidate profile-evidence erasure (erased tombstones, prior-revision redaction, per-candidate key crypto-erase, replay fence, value-free receipt) with store migration 0022, a fresh-MFA candidate operation and an AuthOS account-deletion path.

    integrator

    CANDIDATE_PROFILE_FACT_LIFECYCLES and INACTIVE_LIFECYCLES gain 'erased' (exhaustive consumers must handle it); CandidateProfileFactValueV1.encryptedValueRef must match CANDIDATE_PROFILE_FACT_VALUE_REF_PATTERN and the store requires the writing scope's fingerprint; revise/correct refuse caller-written erased revisions (JOB_APPLICATION_PROFILE_FACT_ERASED_WRITE_DENIED); disclosure staleness gains 'fact_erased'; packet binding gains the refusal APPLICATION_PACKET_CANDIDATE_ERASED; JobApplicationOperationHandlerV1 takes an optional seventh erasure port (absent → JOB_APPLICATION_OPERATION_UNSUPPORTED); jobApplicationTransportBindingsV1 gains DELETE /profile-evidence (candidate_admin), projected to REST/OpenAPI/SDK/CLI/MCP; PostgresCandidateMaterialVaultV1 accepts { profileEvidenceDeploymentKey } for profile-evidence refs under per-candidate keys, and the legacy key form refuses those refs; recordProfileFactInvalidations results may carry erased = 1.

    customer

    Apply store migration 0022 before deploying a runtime that composes erasure; a runtime deployed before it fails closed (every fact write and invalidation read calls the 0022 guard). AuthOS must return the fresh-MFA assurance for the candidate erasure decision. Profile-evidence values must be written through a profile-evidence vault built from the deployment key (wiring of the railway effects dependencies is a follow-up). The global kill switch also blocks the candidate erasure operation; the account-deletion path is not gated by it.

    maintainer

    Erasure is per exact scope (ecosystem, tenant, workspace, candidate, deployment); the same person in another scope is not erased. Destroyed wrapped keys and pre-redaction payloads persist in database backups until they expire. Tombstones emit no outbox event; dependents learn of erasure through the submit refusal. resource_mutations.request_digest of earlier fact writes is kept (a digest of the whole request, not of a value).

  • job-application-candidate-opportunities

    Candidate-private opportunity intake with sealed source provenance and append-only candidate availability observations, store migration 0023 and managed/API/MCP composition.

    maintainer

    The operation list, jobApplicationTransportBindingsV1 and handledJobApplicationOperationKeysV1 gain job-application.opportunity.intake and .source.observe (candidate_write, POST) and .get and .list (candidate_read, GET); JobApplicationOperationHandlerV1 takes an optional tenth opportunity port and returns JOB_APPLICATION_OPERATION_UNSUPPORTED without it. The managed runtime composes PostgresCandidateOpportunityStoreV1 only when profileEvidenceKey is set; the MCP host now also passes the key from JOB_APPLICATION_MATERIAL_KEY_BASE64, which also enables job-application.profile.evidence.write there. Deploy store migration 0023 before the runtime. Brand-specific listing copy and availability wording stay in hosts and presentation (D-117); a shared public listing is referenced by sharedListingRef and never read or copied.

  • job-application-candidate-question-read

    Candidate-side list/get queries of the typed candidate questions and a pinned answer-ref resolver; no migration.

    maintainer

    The operation list, jobApplicationTransportBindingsV1 and handledJobApplicationOperationKeysV1 gain job-application.question.list and job-application.question.get (GET, candidate_read). JobApplicationOperationHandlerV1 takes an optional read port after the E-01g question deps and returns JOB_APPLICATION_OPERATION_UNSUPPORTED without it. The managed runtime composes PostgresCandidateQuestionReaderV1 when profileEvidenceKey is set; the railway effects dependencies route candidate-question-answer refs to PostgresCandidateQuestionAnswerResolverV1. Requires the E-01g candidate questions migration; adds none. Question copy and presentation stay in brand composition (D-117).

  • job-application-candidate-questions

    Typed asynchronous candidate questions with a required-unknown distinct from a refusal, sealed immutable answers, store migration 0027.

    maintainer

    The operation list, jobApplicationTransportBindingsV1, jobApplicationEvents and handledJobApplicationOperationKeysV1 gain job-application.question.ask (candidate_execute, POST) and job-application.question.answer (candidate_admin, POST) and three value-free events; JobApplicationOperationHandlerV1 takes an optional twelfth { port, packets } argument (after P-01n destinationDisclosures) and returns JOB_APPLICATION_OPERATION_UNSUPPORTED without it. Compose PostgresCandidateQuestionStoreV1 with the deployment key used for candidate data keys and jobApplicationQuestionPacketCurrencyV1 over the existing store and packet source. Deploy store migration 0027 before the runtime. Question copy and presentation stay in brand composition (D-117).

  • job-application-cv-ingestion

    Single brand-neutral candidate-private CV ingestion owner (encrypted original custody with write-ahead intents, bounded PDF/DOCX/text extraction into immutable private text revisions, candidate review, proposed facts through the single profile-evidence writer, gated image transcription port).

    integrator

    New subpaths contracts/cv-ingestion* and headless/cv-ingestion* (runtime), cv-ingestion and cv-ingestion-migration (store), docx-text (media-processing-local), cv-ingestion (managed runtime) and the Railway createRailwayCvOriginalCustodyV1. Four operations job-application.cv-ingestion.import, .text.review, .propose-facts (POST, candidate_write) and .get (GET, candidate_read) on rest/sdk/mcp/cli; value-free events imported, text.revised and facts.proposed. Registration, exports and the numbered migration are delivered by the integration owner.

    customer

    A CV upload (PDF, DOCX or UTF-8 text, at most 5 MiB and 20 pages) is stored only as ciphertext under a random per-original key sealed in the candidate vault; its extracted text is private and never AI-allowed until the candidate reviews it; facts extracted from reviewed text are proposals only. Image transcription needs JOB_APPLICATION_CV_IMAGE_TRANSCRIPTION_ENABLED=true and explicit candidate consent; no OCR adapter ships yet.

    maintainer

    Text above 40,000 characters or 65,536 UTF-8 bytes is refused, never truncated (deliberate deviation from the donor). The synthetic deterministic extractor is the only fact extractor; there is no model adapter. Candidate erasure deletes the CV rows and the original document rows and crypto-erases keys, text, quotes and plans; custody objects are deleted only by the intent sweep.

  • job-application-email-negatives

    Verification links must be https and on the expected domain, and the managed webhook environment is validated before any client or module is created (E-01m)

    integrator

    A non-https or off-domain verification candidate link is now refused before the verification effect is reserved or resolved. The managed Resend webhook validates every environment value and the dependency module allowlist before it creates a Postgres client or imports the dependencies module; an invalid deployment fails at startup instead of on the first request.

  • job-application-exact-packet-binding

    Exact packet binding in the submit effect identity, typed non-effect submit result and live profile staleness

    integrator

    JobApplicationServiceV1 takes an optional fifth constructor argument, a JobApplicationSubmitPacketSourceV1 (getProfile, getProfileRevision, getDocument, getDocumentRevision). With it, submit binds job-application.packet-binding@1, reserves job-application.submit-request@2 and refuses stale, absent or revoked profile, mandate or document revisions with typed codes before any reservation. Mandate profile refs must use job-application-profile:<id>:<revision>; an opaque ref is refused as absent. Without it, the request and digest are unchanged.

    maintainer

    JobApplicationExternalEffectPortV1.submit may return { outcome: 'not_submitted', reason } only when nothing was sent outward. The runtime records it through the additive submit_refused lifecycle action (ready_to_submit, awaiting_review or failed) with a failed effect receipt; a refused effect key is consumed and never replayed as ambiguous. The focused composition returns not_submitted for its typed refusals and refuses an effect reserved without a packet binding (input_refused).

  • job-application-fact-invalidation

    Record no-longer-confirmed fact invalidations and refuse submit packets that bind an invalidated revision.

    integrator

    Run ManagedJobApplicationProfileFactInvalidationConsumerV1.poll() for each candidate scope (worker role) so withdrawn facts invalidate exact dependents. With packetBindingEnabled, a submit that binds an invalidated profile, document or answer revision is refused before reservation with APPLICATION_PACKET_DEPENDENCY_INVALIDATED; re-issue the dependent as a new revision and a new mandate revision to proceed.

    maintainer

    JobApplicationSubmitPacketSourceV1 gains an optional listProfileFactInvalidations; PostgresJobApplicationResourceServiceV1 implements it. A source without it checks nothing. The generic outbox stream broker stalls on the unregistered job-application.document.changed key, so the consumer reads its own event key directly.

  • job-application-fact-invalidation-2

    Worker invalidation consumer with durable cursors, stale disclosure snapshots, packet/application dependent enforcement and deletion coverage of profile facts.

    integrator

    JobApplicationSubmitPacketSourceV1.listProfileFactInvalidations is now required (fail closed); custom packet sources must implement it. Set JOB_APPLICATION_PROFILE_FACT_INVALIDATION_ENABLED=1 on the worker to run the consumer (default off). Packet dependents are identified as packet:<applicationId> (D-059).

    customer

    Apply job-application-store migration 0018 after 0017, then run the store conformance. It adds the value-free profile_fact_invalidation_cursors table under FORCE RLS (worker writes, no deletes), a worker-only pending-candidates function and a runtime-only deletion scrub function, and grants the runtime role UPDATE on documents for the deletion scrub.

    maintainer

    Disclosure staleness is derived at read time (fact_missing, fact_no_longer_confirmed, fact_revised, dependent_invalidated, snapshot_mismatch); the snapshot guard is tested but not yet wired into a submit or share path. Candidate-wide erasure of profile facts is not implemented.

  • job-application-fact-revised-consumer

    Revised-event invalidation contract and the submit packet disclosure snapshot guard seam; revised-event consumption awaits a store migration.

    integrator

    bindJobApplicationPacketV1 and recheckJobApplicationPacketV1 accept an optional disclosure (approved snapshots plus exact fact reads); without it the binding is unchanged. JobApplicationPacketBindingRefusalCodeV1 additionally includes PROFILE_FACT_DISCLOSURE_SNAPSHOT_STALE and PROFILE_FACT_DISCLOSURE_SNAPSHOT_DENIED, and CandidateProfileFactInvalidationV1.reason additionally includes revised (additive union widening; exhaustive switches must handle the new members).

    maintainer

    No current submit or share path binds a fact disclosure; a wiring test fails when a job-application source file uses the disclosure snapshot vocabulary without the guard. profile.fact.revised is parsed but not yet recorded or consumed; that needs a new migration widening profile_fact_invalidations_reason_check and the worker pending-candidates event filter.

  • job-application-feature-surfaces

    Brand-neutral career FeatureModuleSpecs and operation classification map in the job-application runtime; no contract change.

    maintainer

    Generators read jobApplicationOperationClassificationsV1 (candidate-private or operator; never public) to filter surfaces; brands pick features, copy overrides and data-view filters through composition. JOB_APPLICATION_INTERNAL_OPERATION_KEYS_V1 lists the operator quarantine operations and the four job-application.opportunity.* operations pending D117-SURF-01a slice 2.

  • job-application-opportunity-surfaces

    Brand-neutral job-application.opportunities FeatureModuleSpec; opportunity operations leave the internal list; no contract change.

    maintainer

    The four candidate opportunity operations (intake, source.observe, get, list) are now covered by job-application.opportunities instead of JOB_APPLICATION_INTERNAL_OPERATION_KEYS_V1. Brands choose whether to include the feature, copy overrides, board filters, the host componentMap and whether to bind sharedListingRef.

  • job-application-packet-source-flag

    Managed packet source behind a deployment control, non-effect killed submits and shared destination and revision-ref helpers

    integrator

    ManagedJobApplicationControlsV1.packetBindingEnabled (host env JOB_APPLICATION_PACKET_BINDING_ENABLED, parsed with parseManagedJobApplicationBooleanV1, fallback false) passes the resource service as the managed submit packet source. Enabled submits bind exact profile and document revisions and refuse opaque profile refs as APPLICATION_PROFILE_REVISION_ABSENT before any reservation; disabled submits keep the legacy digest byte-for-byte.

    maintainer

    killedJobApplicationEffectsV1.applications.submit returns { outcome: 'not_submitted', reason: 'disabled' } and the runtime records ready_to_submit with a failed effect receipt and a consumed effect key; accounts.execute still throws. formatJobApplicationRevisionRefV1 and jobApplicationDestinationAllowedV1 are exported from contracts/packet-binding; the runtime packet binding and the focused admission accept URL-form, mixed-case and parent-domain allowedDestinations entries exactly as the form agent does.

  • job-application-profile-evidence-writer

    Single candidate-private profile-evidence writer (vault value under the candidate key plus fact revision in one erasure-guarded transaction), Railway vault wiring and a two-connection erasure lock conformance proof.

    integrator

    New subpaths contracts/profile-evidence-writer, contracts/profile-evidence-writer-operations, contracts/profile-evidence-writer-transport and headless/profile-evidence-writer (runtime), profile-evidence-writer and material-vault-write (store), profile-evidence-writer (managed runtime). JobApplicationProfileEvidenceWriterPortV1 binds one exact scope; the Railway dependencies return RailwayJobApplicationEffectDependenciesV1 with profileEvidenceVaultForScope. JobApplicationResourceMutationStoreV1.mutate accepts an optional beforeReserve hook.

    customer

    The writer needs migration 0022 and JOB_APPLICATION_MATERIAL_KEY_BASE64 (32 bytes, canonical base64) as the wrapping key; without the key the operation fails closed. The global kill switch refuses it like every mutation once it is registered.

    maintainer

    The same deployment key is both the legacy material key (key_version 0) and the wrapping key of candidate data keys (distinct AAD). resource_mutations.request_digest covers the fact including its value digest and is kept after erasure, as for P-01k fact writes.

  • job-application-profile-fact-correction

    Atomic profile fact correction and the value-free no-longer-confirmed notification.

    integrator

    Correct a confirmed fact with job-application.profile.fact.correct (POST /profile-facts/:factId/corrections, candidate_write) instead of two fact.revise calls. Consumers holding approved disclosures, packets or documents derived from a fact should subscribe to job-application.profile.fact.no-longer-confirmed and invalidate the listed dependents. The event never carries a value or digest.

    maintainer

    Profile fact writes take pg_advisory_xact_lock keys over (table, candidate identity, id) in sorted order. The headless dispatcher in resource-operations.ts and the optional correctProfileFact port method need their integration lines, and real-Postgres two-connection blocking is not yet exercised (PGlite is single-backend).

  • job-application-profile-fact-lifecycle

    Enforce profile fact lifecycle transitions and Sarla-normalized private employer exclusion.

    integrator

    Changing a confirmed fact's value in place is now refused. Use a correction, which creates a new confirmed fact citing fact:<old id> and supersedes the old one. Employer-name exclusion must run where plaintext is available, and fails closed otherwise.

    maintainer

    A correction is still two writes. The successor read is not yet serialized within the same transaction (follow-up hook in resource-mutations), and there is no atomic correction operation yet.

  • job-application-profile-facts

    Typed candidate profile facts with source-faithful lifecycle and value-state vocabulary

    integrator

    Three additive candidate-private operations and one event are registered on the job-application.core capability. fact.revise is a POST binding and goes through command authority. The resource port gains optional reviseProfileFact, listProfileFacts and getProfileRevision methods. A port without them fails closed with JOB_APPLICATION_RESOURCE_OPERATION_UNSUPPORTED.

    maintainer

    Apply migration 0016_candidate_profile_facts.sql with the candidate-private migrator role before enabling the new operations. The table is FORCE RLS and append-only. The runtime, worker and readonly roles have no UPDATE, DELETE or TRUNCATE grant on it.

  • job-application-profile-interview

    Headless adaptive candidate profile interview with four registered commands, refusal memory and explicit adoption into the candidate-private profile (additive; store and hosts not composed yet).

    maintainer

    The operation list, jobApplicationTransportBindingsV1 and handledJobApplicationOperationKeysV1 gain the four profile-interview keys (start, answer and turn.next under candidate_write; proposal.review under candidate_admin); JobApplicationOperationHandlerV1 takes an optional ninth interview dependency and returns JOB_APPLICATION_OPERATION_UNSUPPORTED without it. Brand-specific question wording, prompts, tone, consent text and revision live behind the injected model port and deps.consentRevision (D-117); the French/English non-answer lexicon is a language default pending i18n configuration. JobApplicationProfileInterviewStorePortV1 has no store implementation or migration yet, and API, MCP and managed hosts do not compose the dependencies yet.

  • job-application-profile-interview-expected-revision

    The four profile-interview commands move to contract 2.0.0 and declare the integer expectedRevision that command authority requires, as a compare-and-set on the interview session revision.

    integrator

    job-application.profile.interview.start, .answer, .turn.next and .proposal.review are now version 2.0.0 (fingerprint contract:<key>@2.0.0; input/output schema names end in V2). Every input requires an integer expectedRevision. Version 1.0.0 omitted it, so mutationAuthorityV1 refused every interview command dispatched through JobApplicationOperationHandlerV1 with JOB_APPLICATION_INPUT_INVALID. expectedRevision is the session revision (candidateProfileInterviewSessionRevisionV1). It is 0 before start, 1 after start, and then increases by 1 for each turn, answer and proposal review. A stale value fails with JOB_APPLICATION_PROFILE_INTERVIEW_REVISION_CONFLICT (REVISION_CONFLICT, 409) and writes no session record. A stale turn.next with a new key finishes its claim as failed stale_revision before any model call. Idempotent replays are answered before the check, and so is the no-write open_question result. Every output adds the resulting session revision. Adopted facts keep their own fact CAS (0 for a new fact; the superseded revision for a correction).

  • job-application-quarantine-operator

    Operator list/resolve of quarantined invalidation events with operator grants, fresh-MFA AuthOS assurance, store migration 0021 and grant-gated CLI/MCP surfaces.

    integrator

    JobApplicationGrantV1 gains operator_invalidation_read and operator_invalidation_resolve; the command authority decision gains optional assurance {freshMfaVerifiedAt?, impersonated} (JobApplicationAuthorityAssuranceV1); JobApplicationOperationHandlerV1 takes an optional sixth quarantine port (absent → JOB_APPLICATION_OPERATION_UNSUPPORTED for the operator operations); jobApplicationTransportBindingsV1 gains POST /operator/invalidation-quarantine/:sourceEventId/resolve and GET /operator/invalidation-quarantine, so REST/OpenAPI/SDK/CLI/MCP project them with their operator grants. The managed AuthOS decision parser accepts the operator grants and refuses a decision whose assurance is malformed.

    customer

    The AuthOS decision endpoint behind JOB_APPLICATION_AUTHORITY_URL must return assurance {freshMfaVerifiedAt, impersonated:false} and the operator grants for operator principals; until it does, resolve fails closed with JOB_APPLICATION_FRESH_MFA_REQUIRED. Apply store migration 0021 before exposing the operations. Static stdio MCP contexts refuse operator grants.

    maintainer

    The list query is GET, so it is gated by the operator read grant of the per-request AuthOS context decision and not by a per-operation fresh decision or MFA. Operators act only inside the exact candidate scope AuthOS authorizes; there is no cross-candidate operator listing. A retry under a new decisionRef records a different evidence ref and conflicts rather than replays.

  • job-application-subject-binding-destination-disclosure

    Cross-product candidate subject binding with per-product consent (migration 0025) and destination-disclosure store and operations (migration 0026), with erasure removal and managed composition.

    maintainer

    The operation list, jobApplicationTransportBindingsV1 and handledJobApplicationOperationKeysV1 gain job-application.destination-disclosure.record and .revoke (candidate_write, POST) and .get (candidate_read, GET); JobApplicationOperationHandlerV1 takes an optional eleventh destination-disclosure port and returns JOB_APPLICATION_OPERATION_UNSUPPORTED without it. PostgresJobApplicationSubjectBindingStoreV1 (./subject-binding) is bound to one product application id; createManagedJobApplicationSubjectBindingV1 refuses every bind without an AuthOS admission verifier and createManagedJobApplicationAccountDeletionConsumerV1 composes the P-01m consumer. Deploy store migrations 0025 and 0026 before the runtime. Product application ids are data; brand copy and consent wording stay in hosts and presentation (D-117).

  • job-source-personal-field-classification

    Job-source observations classify personal fields (withheld) and fail closed to restricted; Greenhouse first_published maps to publishedAt

    integrator

    osintJobObservationsV1 returns sensitivityByField and personalFieldsWithheld. Recruiter, contact and other personal data copied from a source payload is classified personal and no longer reaches OSINT job assertions. Raw payload keys that are neither shared normalized job facts nor declared public by the connector are stored as restricted instead of public, so job projections hide them unless the request holds the restricted_field grant. Pass connector.fieldSensitivity to osintJobObservationsV1 to apply a source's public declaration (currently Greenhouse).

    maintainer

    Greenhouse first_published maps to publishedAt and validFrom, so a rescan of identical bytes keeps the listing contentHash and id. Listings without first_published still default validFrom to observedAt.

  • lssm-current-package-binding-locators

    Retain stable LSSM package binding IDs at current domain owner locators

    maintainer

    Canonical binding identities and authority remain stable across physical relocation.

  • lssm-os-spec-platform-spec-purity

    LSSM OS spec becomes a pure platform spec; the filesystem catalog locator moves to lssm-os-runtime and catalog validation takes an injected clock

    integrator

    Import validateLssmCanonicalLocatorInWorkspace from @lssm-tech/lib.lssm-os-runtime/catalog-locator-node and pass an explicit now to validateLssmCanonicalCatalogV2; all other lssm-os-spec imports are unchanged.

  • lssm-os-spec-seed-map

    SeedMapV1 contract, checker, SQL inventory parser and a reviewed-pending Tafio seed map in lssm-os-spec.

    maintainer

    checkSeedMapV1 fails on any mapped user, candidate, profile, application, document, message, session, token, email, phone or payment table or column, on tampering, weakened deny terms, owner drift, count drift and a fake review. The Tafio map is reviewed=false and authorizes no ingestion.

  • lssm-planning-handoff-public-map

    Stable planning-handoff public maps and preserved browser output

    integrator

    Planning handoff retains its browser entry and exposes its existing canonical leaf modules.

  • managed-companyos-mcp-fail-closed-actor

    The Managed CompanyOS MCP server no longer grants admin to any API key and denies commands outside opt-in reference mode.

    integrator

    An unverified MANAGED_COMPANYOS_MCP_API_KEY now resolves to a role-less user instead of an admin. Queries and read-only resources keep working; tenant.onboard and builder.readiness.evaluate are refused with PolicyDenied unless MANAGED_COMPANYOS_MCP_REFERENCE_MODE=1 is set outside production.

  • opa-ai-cited-briefings

    OPA morning recaps and meeting preparation can be written by an allowlisted, EU-routed model through the Vercel AI Gateway once the owner opts in. Every claim links to its source. Otherwise the labelled standard template is sent.

    integrator

    The Gateway model allowlist now lives in @lssm-tech/lib.provider-spec/gateway-model-catalog. The communication-spec ai-model-catalog entry point aliases it unchanged. New contracts are companyos.calendar_intelligence.ai_briefings.settings.read|save, .workspace_model.read|save and the settings_changed event. CalendarIntelligenceInsight gains an optional cited, the e-mail draft an optional generation, provenance 1.1.0 optional sourcesDigest, generatedAt, modelSource and citationCount, and the private draft result optional generation and briefing.

    maintainer

    AI briefings stay off until OPA_AI_BRIEFINGS_ENABLED=1, OPA_AI_BRIEFINGS_PROCESSING_APPROVAL_REF and OPA_AI_BRIEFINGS_GATEWAY_TRANSIT_APPROVAL_REF are set and a Gateway credential resolves for the request: AI_GATEWAY_API_KEY, or on Vercel the per-invocation x-vercel-oidc-token header (shared resolver in @lssm-tech/lib.ai-providers/vercel-gateway-auth), or VERCEL_OIDC_TOKEN. /api/companyos/health/degraded reports opaAiBriefings: enabled | disabled_flag | missing_approval | no_gateway_auth. OPA_AI_DEFAULT_MODEL is optional and must be a catalog id. Each owner must still opt in, and the organization policy must allow intelligence.generate. Apply migration 0125 for the workspace default model. Without it everything else works and the workspace default stays empty. Gateway request processing is global; only provider inference is EU-routed.

    customer

    In Settings → Personal briefings you can let AI write your briefings, pick the model and see exactly what is sent. Each AI briefing says which model wrote it and links every statement to its calendar event or company knowledge source. If you turn it off, or anything goes wrong, you get the standard template, and it says so.

  • opa-gateway-meeting-transcription

    OPA meeting recordings are transcribed only through the Vercel AI Gateway with EU inference, zero data retention and no training. The feature stays disabled until the Gateway lists an EU transcription endpoint.

    integrator

    gateway-transcription-catalog is the single allowlist for Gateway speech models; it is empty today and changes only by reviewed code. opa.capture.processing 1.2.0 relaxes "missing speaker labels" to a declared capability; opa.capture-session 1.3.0 adds transcript erasure to capture deletion. The browser import checkpoint gains an optional source (import or microphone) and older checkpoints parse as imports.

    maintainer

    Enabling needs, in addition to the existing capture prerequisites (OPA_CAPTURE_PROCESSING_ENABLED=1, MANAGED_COMPANYOS_CAPTURE_PROCESSING_DATABASE_URL, CRON_SECRET, BYOK keys): OPA_TRANSCRIPTION_ENABLED=1, OPA_TRANSCRIPTION_PROCESSING_APPROVAL_REF, OPA_TRANSCRIPTION_GATEWAY_TRANSIT_APPROVAL_REF, Gateway auth, and a catalog release that qualifies an EU model. /api/companyos/health/degraded reports opaTranscription (disabled_flag, missing_approval, no_eu_model, no_gateway_auth, enabled).

    customer

    In a private meeting you can record with your microphone or import a file once transcription is available, search the timed transcript, see which model transcribed it, and delete the recording together with its transcript. Until then the page explains that transcription is off and private notes keep working.

  • opa-transcription-non-eu-gate

    OPA meeting transcription can be enabled through an explicitly owner-approved non-EU Gateway model (microsoft/mai-transcribe-2, zero data retention, no training) while no EU transcription zone exists; it stays no_eu_model until the approvals are recorded. The capture worker gains exponential backoff, HTTP status classification, fenced idempotent completion, structured logs and a usage metering hook.

    integrator

    Additive. GatewaySttRequestAuthority/GatewaySttAuthorization.inferenceRegion widens to 'eu' | 'non_eu' (authorizations must now match the request region); the adapter defaults to 'eu'. Settings output gains nonEuApproved, processingRegion and per-model processingRegion/processingLocation. QualifiedCaptureProvider evidence may be non_eu only with nonEuApproval.

    maintainer

    To enable: record the owner decision in docs/evidence/opa/meeting-transcription-2026-10-19.md, then set OPA_TRANSCRIPTION_ENABLED=1, OPA_CAPTURE_PROCESSING_ENABLED=1, OPA_TRANSCRIPTION_GATEWAY_TRANSIT_APPROVAL_REF, OPA_TRANSCRIPTION_NON_EU_PROCESSING_APPROVAL_REF, OPA_TRANSCRIPTION_NON_EU_TRANSFER_APPROVAL_REF (optionally OPA_TRANSCRIPTION_NON_EU_MODELS) with Gateway auth. Unset either non-EU ref to roll back. Watch opa_capture_processing_job and opa_transcription_usage logs and opaTranscriptionProcessingRegion on /api/companyos/health/degraded.

    customer

    When the service operator approves it, meeting recordings are transcribed by a model outside the EU with zero data retention and no training; the transcription settings say so plainly. Transcripts without speaker names explain that the model does not separate speakers.

  • opportunity-wave

    Screen and export distribution-first opportunity drafts without fabricating mature evidence or customer economics.

    integrator

    Import lightweight drafts, preserve scoped unknowns and promote only with complete independently supplied mature requirements.

  • opportunity-wave-sales-assisted

    Screen sales-assisted, creative-aware and channel-diverse opportunity drafts without weakening 1.0.0 waves or inventing customer economics.

    integrator

    Capture 1.1.0 waves with bounded sales motions and production assets; keep 1.0.0 waves on the frozen schema.

  • orchestration-canonical-capability-ref

    Resolve canonical capability references and preserve blocked export maps.

    integrator

    Workflow declarations resolve the existing canonical capability reference type.

  • orchestration-durable-queue-owner

    Own provider-neutral Durable Queue V2 definitions in orchestration-spec.

    integrator

    Existing queue imports retain their canonical schemas and validators.

  • osint-governed-company-projection

    Add the patio.company_offering.v1 governed company/offering projection contract and a pure public-only OSINT flattener.

    integrator

    New leaf exports @lssm-tech/lib.osint-spec/contracts/governed-company-projection(-schema) and @lssm-tech/module.osint/governed-company-projection. Every field is an exact top-level key with its own envelope, so the governed gateway can select it without nested traversal.

    maintainer

    The flattener carries no authority. A governed source reader must still enforce rights, suppression, dataset grants and subject binding before records are produced. No producer, grant path or consumer is admitted by this change.

  • osint-privacy-d057

    OSINT privacy keeps dates and references, withholds messaging URLs, gates personal embedding behind personal_field and ranks projection assertions over rows hidden by RLS

    integrator

    Public job text keeps date ranges, date lists, clock times, references after Ref/ID/Job labels and dated job URL slugs. WhatsApp (wa.me, whatsapp.com/send), Telegram (t.me), Messenger (m.me), Signal (signal.me), tel: and sms: URLs, and URLs whose path or query holds a country-coded French number or a phone parameter, are replaced by [withheld] and their provider-search canonical key is digested. More obfuscated contacts are withheld (spaced -at-, (a), odd phone separators, (06) prefixes, LinkedIn ccTLD and root-path profiles, Braille blanks, \x40 and %u0040 escapes). Declared-public role keys such as workAuthorization are kept. A personal value enters an embedding or knowledge document only with the personal_field grant.

    maintainer

    New field-sensitivity-dates, field-sensitivity-contact-urls and field-sensitivity-values modules; normalizeJobSourceTextV1 exposes separatedSpanOfText. Migration 0034 adds a security-definer function whose owner must bypass RLS on osint_core.assertions (as for 0031); otherwise projections fail closed (empty). Accepted residuals stay documented by tests: person names, a bare " at " with a plain or spelled-out dot, defanged profile hosts and a chain of small slash-separated numbers (01/02/03/04/05), which stays withheld as a phone.

  • osint-privacy-d062

    OSINT privacy decodes the complete HTML5 entity table, lists unsafe keys by index, matches profile hosts on any TLD and keeps URL reference numbers

    integrator

    Contacts written with any HTML5 named or zero-padded numeric character reference are withheld. personalFieldsWithheld never echoes a key holding six or more digits in any script, an @, a contact or a non-identifier character such as a space; such keys, and the parent key of a named-entry list, are listed by index. Profile URLs of LinkedIn, lnkd, Viadeo, Xing, Malt and Welcome to the Jungle on any TLD, and LinkedIn member paths under organization pages, are withheld and their provider-search canonical key is digested. Job URLs keep reference numbers in ref/id/job/req/reference/offre parameters and under jobs/offre/careers segments.

    maintainer

    New field-sensitivity-entities (decoder), field-sensitivity-html-entities (generated table, provenance and SHA-256 in its DocBlock) and field-sensitivity-reference-urls modules; HTML_NAMED_ENTITIES_V1 is removed from field-sensitivity-tables (it was not exported by the package). Free-text privacy remains open pending the D-050 option B owner decision; the residuals outside D-062 are documented by field-sensitivity-d062-residuals.test.ts.

  • osint-privacy-d064

    OSINT privacy never emits an unsafe key in any output structure and matches profile host families on any host label

    integrator

    Fields whose own key, nested keys, kept entry names or extra entry keys hold six or more digits in any script, an @, a contact or a non-identifier character such as a space are withheld whole; the key never appears in fields, sensitivityByField or personalFieldsWithheld. Custom metadata whose kept entry names contain spaces is therefore withheld whole. Profile URLs on any host whose labels include linkedin, lnkd, viadeo, xing, malt or welcometothejungle are withheld and their provider-search canonical key is digested, including public-suffix second levels such as asso.fr, gouv.fr, firm.in and info.pl.

    maintainer

    New field-sensitivity-emitted-keys module (emitted-key rule, named-entry list guard, shared depth bound). Profile host detection uses a label set instead of a TLD-shaped expression; a single-label family host is a candidate only with a scheme. Free-text privacy remains open pending the D-050 option B owner decision.

  • osint-privacy-d066

    OSINT privacy keeps ordinary ATS labels with spaces and punctuation while key triggers still withhold the whole field

    integrator

    Field keys, nested keys and named-entry names with spaces and the punctuation - _ . , : ; ' ’ & / ( ) # + % are kept again (Employment Type, Salary (EUR), Lieu / Ville), so Greenhouse-style custom metadata and declared-public structures with such labels are emitted. Six or more digits in any script, an @ in any decoded form, a contact, or a control, invisible, private-use or unassigned character still withholds the whole field and never appears in fields, sensitivityByField or personalFieldsWithheld. Other symbols such as € or ? stay withheld, fail closed. Labels can carry a person name; that residual is accepted.

    maintainer

    New field-sensitivity-key-shape module (allowed character set and trigger characters) used by jobSourcePathLabelV1 and therefore by the emitted-key rule. The D-064 property generator uses only D-066 triggers, and its controls include spaced and punctuated labels. Free-text privacy remains open pending the D-050 option B owner decision.

  • osint-privacy-fail-closed

    OSINT field classification fails closed; public job text is redacted, personal search results need personal_field, and runtime lease deletes stay in their own tenant

    integrator

    Extractors that set no sensitivityByField now produce restricted assertions, so projections hide those fields without the restricted_field grant; classify fields explicitly to keep them public. Generic provider-search company and job results are classified by the job-source classifier (provider becomes restricted) and person results are personal. Public job text carrying an email, phone or profile URL is stored with those values replaced by [withheld]. Declared-public structured fields (for example Greenhouse departments, offices, data_compliance and pay_input_ranges) are restricted until the declaration lists their documented sub-keys in publicSubKeys. hybridSearch callers must pass a context carrying personal_field to receive personal fields. Apply migration 0033_osint_runtime_lease_delete_scope.sql.

    maintainer

    The OsintSqlScopeOptionsV0 option added by osint-runtime-writer-restricted-append is removed before release; the restricted claim is set by a module-private helper in postgres.ts and a repo-wide git grep test pins it. conformance/rls.sql adds a refused restricted append without the claim and a base-tenant lease delete that removes 0 rows; a pglite test proves the claim does not survive the committed append on the same pooled connection.

  • osint-privacy-normalized-scan

    OSINT public text is decoded before scanning, profile URLs are matched by host, withheld paths are structural, withheld search URLs are digested in canonical keys and projections hold no personal values

    integrator

    Public job text carrying an encoded or obfuscated email, phone or profile URL is stored with the whole original span replaced by [withheld]; LinkedIn URLs other than organization pages, lnkd.in links and github.com/<user> links are withheld too. Keys such as auteur, référent, nom, tel, mail, manager and assignee are now personal and withheld. personalFieldsWithheld may list a key by index ([3]) when the key text is not a plain identifier. Provider-search observations whose URL is not an unchanged public field carry a sha256 canonical key hint instead of the URL. Projection rows and embeddings no longer contain personal values, so personal fields are absent from projection data even with personal_field; read them from the governed core store.

    maintainer

    Sensitivity in module.osint projection is a set: personal and restricted are independent and both grants are needed when both are present. projectPerson tolerates a person without restrictedFields. The governed company projection reports a personal-only field as unknown, like a restricted-only field, because that material no longer leaves the store. Person names in free text are still not detected (documented residual).

  • osint-privacy-parse-normalize

    OSINT privacy scan normalizes to a fixpoint, detects phones on a separator-folded view, parses profile URLs with WHATWG URL and projections require that no cited evidence is non-public

    integrator

    More encoded and obfuscated contacts in public job text are replaced by [withheld]: Unicode-dash, comma, underscore and multi-space phones, Arabic-Indic and Devanagari digits, combining marks, up to eight entity or percent rounds (more is withheld whole), (a), <at>, -at- emails, and LinkedIn, GitHub, lnkd.in, Xing, Viadeo, Malt and Welcome to the Jungle profile URLs with a port, trailing dot, backslashes, JSON-escaped slashes, dot segments or an embedded /in/ redirect. Provider-search results with such URLs get a sha256 canonical key hint. "Engineer @ Acme.io", Malt /s/ search pages and salary ranges are kept. Encoded personal keys are withheld and listed by index. Projection data omits a field whose current assertion cites any non-public evidence.

    maintainer

    normalizeJobSourceTextV1 now returns saturated and a separated phone view; field-sensitivity-urls parses candidates with WHATWG URL; field-sensitivity-mapped holds the span mapping. Accepted residuals stay documented by tests: person names in free text and identifier-shaped keys, and a bare " at " with a plain dot.

  • osint-reference-taxonomy

    Brand-neutral public reference taxonomy across osint spec, runtime, module and store, with store migration 0035.

    maintainer

    Hosts register createReferenceTaxonomyMcpToolsV1 and the CLI commands with createReferenceTaxonomyOperationHandlerV1; the bindings are not appended to osintTransportBindingsV0. Source rights for ESCO, ROME, NAF and NACE are recorded but unreviewed; review them before production publication. Deploy osint-store migration 0035 before the runtime.

  • osint-source-rights-outbox

    OSINT source-rights outbox (osint-store migration 0036) with dispatch to the source product hosts, the production sourceRights issuance port and a separate read bearer for sourceRights.current.

    maintainer

    Apply osint-store migration 0036 before enabling dispatch. OSINT host env: OSINT_SOURCE_RIGHTS_INGRESS_ORIGIN, OSINT_SOURCE_RIGHTS_INGRESS_TOKEN, OSINT_SOURCE_RIGHTS_INGRESS_APPLICATION_ID, OSINT_SOURCE_RIGHTS_DISPATCH_SCOPE, OSINT_SOURCE_RIGHTS_DISPATCH_INTERVAL_MS (setting the dispatch env without the outbox binding fails startup with OSINT_SOURCE_RIGHTS_OUTBOX_UNBOUND). Identity host env: LSSM_GOVERNED_COMPANYOS_SOURCE_RIGHTS_CURRENT_ORIGIN, LSSM_GOVERNED_COMPANYOS_SOURCE_RIGHTS_CURRENT_TOKEN, LSSM_GOVERNED_LSSM_OS_SOURCE_RIGHTS_CURRENT_ORIGIN, LSSM_GOVERNED_LSSM_OS_SOURCE_RIGHTS_CURRENT_TOKEN. Source product host env: COMPANYOS_GOVERNED_SOURCE_RIGHTS_CURRENT_READ_TOKEN and LSSM_OS_GOVERNED_SOURCE_RIGHTS_CURRENT_READ_TOKEN (32+ characters, distinct from the OSINT ingress bearer and the reserved secrets; equal to the identity host CURRENT_TOKEN of that source).

  • osint-spec-contracts-extraction

    OSINT contract definitions move from the contracts-spec compatibility facade to their existing owner @lssm-tech/lib.osint-spec with identity-preserving forwards

    integrator

    Import OSINT contracts from @lssm-tech/lib.osint-spec/contracts/<leaf>; every former @lssm-tech/lib.contracts-spec/osint/<leaf> import keeps working and resolves to the same objects.

  • osint-worker-domain-ownership

    OSINT worker domain behavior moves to osint-runtime and job-source-runtime

    integrator

    New provider-neutral subpaths expose source lifecycle mutation input, embedding projection identities, scheduled work planning, operator recovery admission, webhook/deletion retry policy, research evidence, search and job-source observation normalization, and operator job reconciliation behind explicit ports.

  • personal-01a-career-leaf

    PersonalOS career goals, plan versions, search state and the per-product career.goal-plan@1 projection and server-only consumer.

    maintainer

    lib.personal-os-spec and lib.personal-os-runtime add ./career; bundle.personal-os adds the server-only ./consumers/career. Career products read career.goal-plan@1 only through a verified admission and an active per-product career_goal_plan_read grant; withdrawal denies the next read and invalidates issued projections locally before remote revocation. No existing schema, purpose enum or export changes.

  • personal-coach-command-owner

    Shared coach adaptation command construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical coach adaptation construction without duplicating policy, risk or proposal defaults.

  • personal-consent-command-draft

    Unbound consent drafts so PersonalOS mobile reuses the canonical consent constructor

    integrator

    Hosts with a platform digest port can bind the canonical consent draft without duplicating the envelope policy.

  • personal-foundation-command-owner

    Shared household, mission and goal foundation construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical foundation construction without duplicating household exclusions, declaration or metric defaults.

  • personal-outcome-command-owner

    Shared outcome observation command construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical self-declared outcome observation construction without duplicating provenance defaults.

  • personal-plan-command-draft

    Unbound Today/habit drafts so desktop and mobile reuse the canonical PersonalOS constructor

    integrator

    Hosts with a platform digest port can bind the canonical draft without duplicating Today/habit defaults.

  • personal-productivity-command-owner

    Shared deterministic Today and habit construction with a thin PersonalOS web adapter

    integrator

    Hosts can reuse canonical construction without duplicating domain defaults or granting authority.

  • personal-productivity-reflection-owner

    Shared check-in, recovery and weekly-review construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical observed-values-only reflection construction without duplicating productivity defaults.

  • personal-rights-command-owner

    Shared export and deletion rights request construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical rights request construction without duplicating scope, format or risk policy.

  • personal-support-command-owner

    Shared goal-scoped support grant, report, revoke and block construction for PersonalOS web, desktop and mobile hosts

    integrator

    Hosts can reuse canonical support construction without duplicating grant scope, expiry or exclusion policy.

  • personalos-command-envelope-ownership

    PersonalOS command envelope construction and digest binding move to personal-os-runtime

    integrator

    A new ./command-envelope subpath builds an unbound PersonalOS command envelope (surface evidence first, placeholder digest) and validates/binds a workspace command to its domain-separated payload digest.

  • platform-builder-data-ports

    Remove upward Builder type dependencies through neutral supplied-data projections.

    integrator

    Existing Builder helper imports retain behavior; neutral input models remove platform-to-domain dependencies.

  • platform-planning-handoff-owner

    Canonically own the unchanged reviewed planning handoff protocol below Builder.

    integrator

    Existing Builder and control-plane imports remain valid; strict plan-only handoff data has a neutral lower owner.

  • portable-delivery-chain-owner

    Preserve metadata-only delivery chain through canonical LSSM OS ownership

    integrator

    Historical delivery imports forward to the same canonical schemas and digest helpers; Builder references the canonical deployment receipt type.

  • provider-contract-type-cohesion

    Preserve provider contracts through cohesive private implementation units

    integrator

    Existing provider types and aggregation imports retain their contracts and behavior.

  • pure-spec-export-workflow

    Preserve pure-spec public exports through canonical prebuild.

    maintainer

    Preserve 12 Assurance and 26 Orchestration public roots while compiling every model file.

  • quality-canonical-assurance

    Preserve quality contracts under the pure assurance owner and remove the execution-lanes compatibility backedge.

    maintainer

    Quality models and supplied-evidence validation have one canonical pure owner; runtime execution remains separate.

  • support-platform-authority-owner

    SupportOS platform authority composition moves to its canonical runtime owner with identical compatibility exports

    integrator

    Import platform-authority, platform-authority-bindings and platform-authority-binding-registry from customer-support-runtime; existing contracts-spec imports remain supported.

  • tendframe-product-domain-alignment

    Align the existing founder product with the Tendframe name and canonical domains while preserving legacy identity and origin compatibility.

    customer

    The existing founder workspace and acquisition site use the Tendframe name and canonical domains; account entitlements and privacy boundaries remain the same.

    integrator

    Existing package names, environment keys, app_pactena entitlement scope, pactena-web client ID, HTTP headers, database identity, and explicit origin overrides remain compatible.

    maintainer

    New default origins require qualified DNS/TLS, matching app/API configuration and reconciliation of the existing identity client before cutover. No production admission gate is enabled by this change.

  • tkid-01-taketide-authos

    Register the production-disabled Taketide relying party and single-origin route, and add a presentation-only product session render partition with a fail-closed creator host session binding.

    integrator

    AUTH_OS_ECOSYSTEM_RELYING_PARTIES gains rp_taketide_web and resolveLssmProductScopes gains the app_taketide scope (11 entries). New exports authOsEcosystemSingleOriginRoute, assertAuthOsEcosystemSingleOriginRoute, ./product-session-scope and ./server/session-scope. The render partition only keys presentation caches and never grants authority; hosts inject the AuthOS product admission adapter and a fresh-session reader.

  • w3-client-server-ownership-boundaries

    Remove client-to-server reach and wrong ownership edges found by the W3 package boundary check.

    integrator

    Import sha256Hex from crypto-utils/sha256 and the Better Auth web client from authos-better-auth/client in browser code.

  • w4-edition-assurance-pure-suppliers

    Canonicalize portable Connect and Harness evidence declarations.

    maintainer

    Preserve declaration identity and runtime registry compatibility.

  • w4-immutable-artifact-ref-owner

    Canonicalize the immutable artifact reference declaration.

    maintainer

    Preserve exact artifact reference fields through existing root and Legacy imports.

  • w4-job-application-canonical-owner

    Canonical job application contracts with preserved compatibility forwarding

    integrator

    Existing imports retain their contracts through the domain owner.

  • web-01-int0-module-founder-intelligence

    @lssm-tech/module.founder-intelligence declares a module.forms dependency (WEB-01-INT0, D-103).

    maintainer

    '@lssm-tech/module.founder-intelligence' now depends on '@lssm-tech/module.forms'; no export or behavior changed.

  • x9-auth-support-ownership

    Auth and customer-support host behavior moves to authos-runtime, auth-os, customer-support-spec and customer-support

    integrator

    New owner subpaths expose the Passport OAuth gate and redirect allowlist, a public HTTP waitlist adapter, linked-accounts, passkey-management, invitation-acceptance and Passport privacy hooks with their ports, LSSM Passport copy, the live-chat binding-activity wire contract, a React Native safe case-queue hook and the customer session / live-chat lifecycle services with host security and transport ports.

Deprecations

  • The Patio* company offering projection types and values are deprecated aliases of the CompanyOffering* names and are removed in the next major release.

Migration guide

  • Apply migration 0196 before activating API Key or Agent Auth

    Required

    New plugin models use auth-owner tables and are denied to product and Supabase API roles.

    1. Apply 0196_authos_official_plugin_models.sql through the existing reviewed migration workflow.
    2. Verify both Drizzle metadata and physical database columns using the production auth database role.
    3. Configure host authority and complete capability-specific canaries before enabling privileged plugins.
  • Apply only the reviewed identity migration batch

    Required

    Preserve existing identity and product records while installing official plugin and central lifecycle models.

    1. Review the exact identity-migration-application-plan-2026-11-01 artifacts and source hashes.
    2. Complete the guarded command's real approval and verified encrypted-backup requirements.
    3. Apply only versions 0196–0204; do not invoke the unfiltered full product migration command.
    4. Recheck physical schema, runtime metadata, roles, ownership triggers and all nine ledger digests.
    5. Qualify isolated deployments, provider callbacks and consuming applications before claiming production completion.
  • Declare appPathPrefixes on every origin route you build

    Required

    Route objects without appPathPrefixes fail AuthOsEcosystemOriginRouteSchema and the TypeScript type.

    When: When code constructs or parses an AuthOsEcosystemOriginRoute.

    1. Add appPathPrefixes to each route; use [] for no workspace-path redirects.
  • Bind the content-analysis budget port and upsert receipts by id

    Required

    Hosts composing runContentAnalysisV1 must supply a budget port and an upsert repository.

    When: When a host constructs ContentAnalysisRuntimeDependenciesV1.

    1. Implement ContentAnalysisBudgetPortV1.reserve so a repeated call with the same receiptId returns the same reservationRef without a new reservation.
    2. Implement ContentAnalysisBudgetPortV1.settle so repeated calls for one reservationRef keep a single settlement (a later call may raise unknownCharge).
    3. Make ContentAnalysisRepositoryPortV1.save replace an existing receipt with the same id (running then terminal).
    4. Treat a failed receipt as final for its idempotency key; retry with a fresh idempotencyKey.
  • Bind the durable content-analysis repository, lease and outbox relay

    Required

    Replace the upsert repository with the claim/lease/fence port and schedule the relay and sweep.

    When: When a host constructs ContentAnalysisRuntimeDependenciesV1.

    1. Implement ContentAnalysisRepositoryPortV1 with create-if-absent claim, fence-conditional writes and terminal-plus-outbox transactions, or migrate and use SqlContentAnalysisStore on a scoped growth client.
    2. Set leaseMs to a positive integer at least as long as the model deadline.
    3. Run relayContentAnalysisOutboxV1 per scope; consumers must deduplicate by dedupeKey (delivery is at-least-once).
    4. Run sweepContentAnalysisReservationsV1 per scope with staleAfterMs >= leaseMs.
  • Return usage and billed cost from the Gemini structured client

    Required

    generateStructured returns { output, usage?, billedCostMicros? }; pass pricing only to record an estimate.

    When: When a host injects a GeminiStructuredGenerationPort.

    1. Wrap the structured output in { output } and report integer token usage when available.
    2. Report billedCostMicros only for a provider-reported actual charge; never pass a price-list estimate as billedCostMicros.
  • Apply migration 0032 before the runtime

    Required

    job-application-store migrations/0032_candidate_profile_questions.sql (generated verbatim from candidateProfileQuestionsMigrationSqlV1, D-181/D-182a) adds the profile context columns to candidate_questions and candidate_question_answer_revisions, drops NOT NULL on their application columns, adds one exactly-one-context check per table and a profile index. Grants and RLS are unchanged.

    1. Apply job-application-store migrations/0032_candidate_profile_questions.sql after 0031.
  • Use the company.offering.v1 projection id and the COMPANY_OFFERING_PROJECTION_* codes

    Required

    The projection id and error codes are renamed; persisted grants or catalog rows outside this repository that hold patio.company_offering.v1 no longer match.

    When: When a caller compares the projection id, matches PATIO_PROJECTION_* error codes or persists the projection id.

    1. Replace patio.company_offering.v1 with COMPANY_OFFERING_PROJECTION_ID (company.offering.v1) and the catalog entry with COMPANY_OFFERING_CATALOG_ENTRY_REF (company.offering@1).
    2. Match COMPANY_OFFERING_PROJECTION_* instead of PATIO_PROJECTION_* error codes.
    3. Rename PatioCompanyOffering* imports to the CompanyOffering* names before the aliases are removed.
  • Pass founder context and organization data from the host

    Required

    FOUNDER_CONTEXT_IDS and the closed slug union are gone; ids are branded and validated against a registry or manifest.

    When: When a caller imports FOUNDER_CONTEXT_IDS, relies on the FounderContextId or CanonicalOrganizationSlug literal unions, or indexes ORGANIZATION_BOOTSTRAP_PHASES as a tuple.

    1. Build a registry with defineFounderContextRegistry and a manifest with defineOrganizationBootstrapManifest (./managed-companyos/organization-bootstrap-manifest) and pass them to founderContextIdSchemaFor, planFounderBootstrap and the alias resolvers.
    2. Parse plain strings into FounderContextId / CanonicalOrganizationSlug through the registry or manifest instead of casting.
    3. Treat ORGANIZATION_BOOTSTRAP_PHASES as readonly OrganizationBootstrapPhase[].
  • Build the OSINT deployment profile registry in the host and pass it explicitly

    Required

    Hosts load osint.deployment-profiles@1 from @lssm-tech/lib.lssm-os-spec/catalog/osint-deployment-profiles, build the registry once with defineOsintDeploymentProfileRegistryV0 and pass it to the resolvers and to createManagedOsintOperationHandlerV0. The removed Hirly profile/program constants have no replacement in lib.osint-runtime.

    When: Before upgrading lib.osint-runtime or integration.osint-managed-runtime.

    1. Replace imports of HirlyFranceInternshipApprenticeshipProfileV0/ProgramV0 with the G catalog rows.
    2. Pass the registry to resolveOsintDeploymentProfileV0, resolveKnownOsintDeploymentProfileV0 and createManagedOsintOperationHandlerV0.
  • Update renamed seed-map, donor-pin and readiness identifiers

    Required

    Replace the seed-map path constants with seedMapCatalogPathV1(mapId); read DONOR_PINS_V1[].sourceRef instead of repository (resolveLssmDonorSourceV1 maps it to the repository); rename readiness owner 'hirly' to 'host_product' and capability hirly-export-cutover to legacy-host-export-cutover.

    When: Before upgrading lib.lssm-os-spec, integration.job-sources or bundle.creator-platform.

    1. Update consumers of the removed seed-map constants, DONOR_PINS_V1.repository and the readiness owner/capability ids.
  • Apply osint-store migration 0037 before mounting subject bindings

    Required

    Apply 0037_osint_governed_subject_bindings.sql with the migrator role; the runtime role must stay NOSUPERUSER NOBYPASSRLS. The table starts empty; organization issuance answers subject_binding_unavailable until an operator records bindings.

    When: Before enabling organization grant issuance with the subjects port.

    1. Run the OSINT store migrations through 0037 with the migrator role.
  • Apply osint-store migration 0038 before the hand-back and operator resolve

    Required

    Apply 0038_osint_source_rights_operator_subject_refs.sql after 0037 with the migrator role; the runtime role must stay NOSUPERUSER NOBYPASSRLS.

    When: Before enabling the subjectRef hand-back or the operator resolve route.

    1. Run the OSINT store migrations through 0038 with the migrator role.
  • Apply job-application-store migration 0022

    Required

    Adds candidate_material_keys, candidate_material_vault.key_version, candidate_erasure_receipts, candidate_profile_erasure_guard() (runtime, worker), erase_candidate_profile_records(text,text,text,text,text) (runtime only), re-creates profile_fact_invalidation_pending_candidates behind the erasure fence and grants jsonb_object_length to runtime/worker.

    When: Before deploying a runtime, worker or MCP/API host built from this release.

    1. Apply packages/integrations/job-application-store/migrations/0022_candidate_profile_erasure.sql after 0021 (fresh schema under D-088; no data migration).
    2. Run the store conformance; security.sql asserts the P-01k grants, definer functions and FORCE RLS of the new tables.
  • Apply migration 0031 before the runtime

    Required

    job-application-store migrations/0031_cv_ingestion.sql (generated verbatim from cvIngestionMigrationSqlV1, D-172) adds the five FORCE RLS append-only cv_* tables and the candidate-erasure trigger that removes CV ingestion rows.

    1. Apply job-application-store migrations/0031_cv_ingestion.sql after 0030.
  • Check the managed webhook environment before deploying

    Deployments that relied on a malformed environment value or a dependency module outside the job-application-webhook-dependencies-* allowlist now fail at startup.

    1. Confirm each managed webhook environment value is set and the dependencies module name matches the allowlist.
  • Apply job-application-store migration 0018

    Required

    Adds durable invalidation cursors, the worker pending-candidates function, the runtime deletion scrub function and the documents UPDATE grant for the deletion scrub.

    When: Before enabling JOB_APPLICATION_PROFILE_FACT_INVALIDATION_ENABLED or running application deletion on this release.

    1. Apply packages/integrations/job-application-store/migrations/0018_candidate_profile_fact_retention.sql after 0017.
    2. Run the store conformance; security.sql expects profile_fact_invalidation_cursors.
  • Apply the candidate profile fact invalidations migration

    Required

    Creates the append-only profile_fact_invalidations table with forced row-level security and scope policies; no existing table is rewritten.

    When: Deploying the job-application store after 0016

    1. Run packages/integrations/job-application-store/migrations/0017_candidate_profile_fact_invalidations.sql after 0016.
    2. Run the store Postgres conformance suite and confirm profile_fact_invalidations is listed with FORCE RLS.
  • Apply the candidate profile facts migration

    Required

    Creates the profile_facts table with forced row-level security and grants; no existing table is rewritten.

    When: Deploying the job-application store after 0015

    1. Run packages/integrations/job-application-store/migrations/0016_candidate_profile_facts.sql after 0015.
    2. Run the store Postgres conformance suite and confirm profile_facts is listed with FORCE RLS.
  • Send the session expectedRevision on every interview command

    Required

    Interview clients and hosts must send expectedRevision and the 2.0.0 contract fingerprint.

    When: Before calling a profile-interview command through a host built from this release.

    1. Send expectedRevision 0 with profile.interview.start.
    2. Send the revision returned by the previous interview command with each later command.
    3. On JOB_APPLICATION_PROFILE_INTERVIEW_REVISION_CONFLICT, reload the session state and retry with a new idempotency key.
  • Apply job-application-store migration 0021

    Required

    Adds resolve_profile_fact_invalidation_quarantine(text,text,text,text,text,text) and profile_fact_invalidation_quarantine_entries(text), SECURITY DEFINER with a pinned search_path, executable by job_application_runtime and job_application_worker only; table grants are unchanged.

    When: Before deploying an API or MCP host that composes the operator quarantine port.

    1. Apply packages/integrations/job-application-store/migrations/0021_profile_fact_invalidation_operator.sql after 0020.
    2. Run the store conformance; security.sql asserts the definer, search_path and execute grants of both functions.
  • Bind the connector field-sensitivity declaration in OSINT extraction

    Without a declaration, classification fails closed: only shared normalized job facts are public. Hosts that want a source's documented public raw keys to stay public pass the connector's declaration.

    1. Call osintJobObservationsV1 with fieldSensitivity set to the job-source connector's fieldSensitivity.
  • Apply migration 0034 and rebuild projections that may hold superseded public values

    Required

    Projection rows and embeddings written before this release may hold an older public value of a field whose newer assertion is restricted.

    When: Before the projection worker of this release runs

    1. Apply packages/integrations/osint-store/migrations/0034_osint_projection_supersession.sql as the migration owner.
    2. Rebuild osint_projection.entities and the derived lexical index and embeddings for affected tenants.
  • Apply the OSINT runtime lease delete scope migration

    Required

    Without 0033 a runtime transaction holding base_read or base_curate can delete the shared-base tenant's ingestion lease and allow a concurrent duplicate run.

    1. Apply packages/integrations/osint-store/migrations/0033_osint_runtime_lease_delete_scope.sql with the migrator role after 0032.
  • Re-key existing provider-search entities whose canonical key embeds a withheld URL

    The digest applies to new rows only. Existing osint_core.entities rows written by provider search whose canonical_key is <kind>:<url> with a withheld or personal URL keep that URL in clear, and a new ingestion of the same URL resolves to the digested key, so it does not match the old row or a suppression whose subject fingerprint is the old clear key.

    When: Provider-search results were ingested before this release

    1. Identify provider-search entities (evidence locator provider:<provider>:source:<n>) whose canonical_key suffix is a URL that the job-source classifier withholds or that belongs to a person result.
    2. Compute the new key as <kind>:osintWithheldCanonicalKeyHintV0(<suffix>) from @lssm-tech/lib.osint-runtime/identity and plan a reviewed data migration that updates canonical_key and adds suppressions with the digested subject fingerprint, before relying on suppression of those subjects.
    3. Rebuild osint_projection.entities for affected tenants so rows written before this release no longer hold personal values.
  • Rebuild projections that may hold assertions citing non-public evidence

    Rows of osint_projection.entities and embeddings written before this release may contain a public assertion that also cited personal evidence, or an older public value read in place of a newer non-public one.

    When: Projections were built before this release

    1. Rebuild osint_projection.entities and the derived lexical index and embeddings for affected tenants.
  • Qualify the new origins before switching runtime configuration

    Required

    Keep explicit legacy origins until the new domains and registered callback are operational.

    When: Deploying the founder product on the new Tendframe domains

    1. Attach tendframe.me and its www/.run marketing aliases to the founder web project, app.tendframe.me and app.tendframe.run to the same web project, and api.tendframe.me to the founder API project; verify DNS and TLS.
    2. Deploy the central identity composition with the updated AuthOS catalog, exact Tendframe waitlist CORS origin, and product email/status-link label. Reconcile the existing pactena-web registration with both exact callbacks and post-logout URLs; preserve the stable client, scopes, pairwise configuration, and security-review gates.
    3. Set BETTER_AUTH_BASE_URL=https://api.tendframe.me, APP_WEB_BASE_URL=https://app.tendframe.me and MARKETING_WEB_BASE_URL=https://tendframe.me on the API only when the cutover is ready.
    4. Build the web with NEXT_PUBLIC_PACTENA_API_URL=https://api.tendframe.me and NEXT_PUBLIC_PACTENA_API_ORIGIN=https://api.tendframe.me. Preserve the existing identity-authority configuration and matching reviewed RP mode.
    5. Qualify the protected authorization callback, local product session, invite-only denial, sign-out and waitlist flows on the new domains before promoting them. Legacy callbacks remain bound to the legacy API.
    6. Preserve the registered peer issuer defaults and the existing verified notification sender domain until their owners complete separate migrations.
  • Bind the lib.cli-runtime runtime ports in programmatic hosts

    Required

    Bind the ports before calling the port-backed lib.cli-runtime functions or the module.workspace DocBlock analysis forwards outside @lssm-tech/bundle.workspace. Hosts that import the bundle.workspace root entry or create a program through @lssm-tech/bundle.workspace/cli (createProgram, createCoreProgram or bindWorkspaceCliCommandPacks) are already bound.

    When: The host calls lib.cli-runtime DocBlock analysis, loadAuthoredModule under Node, the env-example templates, createConnectControlPlaneRuntime without a channel, or the module.workspace analyzePackageDocBlocks, buildPackageDocManifest or extractModuleDocData forwards, and never imports @lssm-tech/bundle.workspace.

    1. Bind the TypeScript tool before DocBlock analysis or Node module loading: bindCliRuntimePorts({ typescript }) with import * as typescript from '@lssm-tech/lib.typescript-runtime'.
    2. Bind environment resolution before the env-example templates: bindCliRuntimePorts({ environment: { resolveEnvironmentForTarget, buildEnvExample } }) from '@lssm-tech/integration.runtime/environment'.
    3. Pass channel (import * as channel from '@lssm-tech/integration.runtime/channel') to createConnectControlPlaneRuntime, or bind it as connectChannel.
  • Read productionEnabled per registration

    Non-breaking. Only code that assumed every catalog relying party is production-disabled is affected; no runtime in this repository does.

    When: When a consumer filters or asserts AUTH_OS_ECOSYSTEM_RELYING_PARTIES on productionEnabled or securityReviewRef.

    1. Read productionEnabled and securityReviewRef from each registration instead of assuming false and undefined.
    2. Keep treating inviteOnly as true for every registration; open admission needs its own security review.
  • Handle the new PersonalOS consent consumer

    PersonalConsentConsumerV1Schema gains companyos_meeting_context. Parsing is unchanged for existing values; code that switches exhaustively over the consumer type or keys a closed label map by it must add the member.

    When: Before upgrading a host that exhaustively matches PersonalConsentConsumerV1 or renders consumer labels from a closed map.

    1. Add a case or label for companyos_meeting_context wherever PersonalConsentConsumerV1 is matched exhaustively.
  • Bind the product channel hosts

    Additive. Unbound hosts keep every new surface fail-closed.

    When: When a deployment enables Pactena or HCircle notification preferences, Pactena calendar intake, or PersonalOS calendar and mail effects.

    1. Provide a revision-CAS preference store and a CommunicationOS host (routing, route directory, eligibility and Runtime Node delivery admission) to the product composition.
    2. For Pactena calendar intake, bind a calendar connection host and the SQL meeting-intake materializer.
    3. For PersonalOS, have the worker lease calendar_reconciliation and notification_delivery effects into the exported executors with a calendar provider host and domain activation, and release a deferred notification lease at its availableAt instead of acknowledging it.
    4. Key any preference store by productNotificationPreferenceKeyV1 (product, person and full scope).
  • Apply migrations 0155 and 0156

    Required

    0155 (authos_trusted_device_labels) backs the trusted-device list; until it is applied the list answers an error (sign-in and remember-device still work). 0156 adds nullable phone columns; the API selects them only when AUTHOS_PHONE_OTP_ENABLED=1, so it can be applied ahead of the flag.

    1. Run the tracked migration runner so 0155_authos_trusted_device_labels.sql and 0156_authos_user_phone_number.sql are applied before deploying the API.
  • Leave AUTHOS_CONNECT_LSSM_ENABLED and AUTHOS_PHONE_OTP_ENABLED unset in production

    Connect with LSSM stays closed in production until a human approves docs/evidence/authos/connect-lssm-security-review-2026-10-19.md and records AUTHOS_CONNECT_LSSM_REVIEW_APPROVAL_REF. Phone codes need AUTHOS_PHONE_OTP_ENABLED=1 plus AUTHOS_SMS_TWILIO_ACCOUNT_SID, AUTHOS_SMS_TWILIO_AUTH_TOKEN and AUTHOS_SMS_TWILIO_FROM_NUMBER.

    1. Do not set either flag in production until the review is approved and an SMS sender is provisioned.
  • Pass the SecuritySettings callbacks you support

    SecuritySettings renders the Change, Manage, and Update buttons only when onChangePassword, onManageEmail, onManageMfa, or onUpdatePhone are provided. Hosts that relied on always-visible (inert) buttons should pass the callbacks they actually support.

    1. Pass onChangePassword / onManageEmail / onManageMfa where your host has those flows.
    2. Implement AuthAccountAdapter and use useAccountProfile, useChangePassword, useEmailAddresses, and useDeleteAccount with the ./ui/organisms/account organisms.
  • Apply migration 0142 before enabling the Roles section

    Required

    The role routes need managed_companyos_custom_roles and the custom_role_id grant column.

    1. Run the tracked migration runner (companyos:db migrate) so 0142_authos_custom_roles.sql is applied; until then the role routes answer 503 and the Roles section shows its load error.
  • Apply migration 0150 before enabling the Single sign-on section

    Required

    SSO and SCIM need sso_provider and the authos_sso_* / authos_scim_* tables.

    1. Run the tracked migration runner (companyos:db migrate) so 0150_authos_enterprise_sso.sql is applied. Until then the Single sign-on section shows its load error, SSO sign-ins fail closed, and other sign-in methods keep working (the session gate tolerates the missing schema for non-SSO paths).
  • Move OrganizationSettings consumers to the new handlers

    Required

    Replace the removed props and pass the signed-in account id.

    1. Replace onManageOrg with onUpdateProfile({ name }) and resolve false when the server refuses the update.
    2. Remove onConfigureSettings; there is no organization settings row anymore.
    3. Replace onAcceptInvitation/onDeclineInvitation with onManageInvitations (the page lists pending invitations read-only).
    4. Pass value.currentUserId and the members' userId so guardrail-aware controls render; without it the page fails closed (no member controls).
    5. Read mutation failures from useOrganizationSettings state.actionError instead of state.error.
  • Apply migration 0124 before enabling the page

    Required

    The API key routes and authentication path need the authos_personal_api_keys table.

    1. Run the tracked migration runner (companyos:db migrate) so 0124_authos_personal_api_keys.sql is applied; until then the API key routes answer 503 and keys cannot authenticate.
  • Expect stale-claim takeover in the in-memory operator-auth store

    No API change. Tests or local-mode hosts that relied on the in-memory store refusing a second claim forever must now expect a takeover after 5 minutes.

    1. Advance the injected clock by less than 5 minutes when a test needs a second claim to be refused.
  • Write SupportOS authority origins exactly

    Required

    Configure each SupportOS origin as https://host[:port] (wss:// for the realtime origin), with no surrounding whitespace, path, query or fragment, and endpoint URLs without fragments.

    1. Remove trailing whitespace or newlines, empty ? or
  • Optionally seal durable outbox payloads with the shared primitives

    Additive only; existing imports are unchanged. A host persisting a durable outbox may implement CommunicationOsOutboxPayloadCipher with its platform AES-GCM, bind communicationOsOutboxAdditionalData as additional data, and quarantine rows that fail to open.

    1. Implement CommunicationOsOutboxPayloadCipher with the platform AES-256-GCM API and a host-held key.
    2. Seal on enqueue and open on listReady; quarantine any row whose envelope does not open instead of sending it.
  • Carry forward activations before enabling the gate

    Required

    Existing subjects lose health and life-admin access until activated. Run the idempotent backfill once; it only activates subjects with a current consent.

    1. Apply migratePostgresPersonalStore to create activation, ledger, attestation and heartbeat tables.
    2. Run runPostgresPersonalActivationCarryForward for every AuthOS subject with consent facts from the host key service.
    3. Start key-recovery attestation and outbox heartbeat writers, then deploy the API with domainActivation from createPostgresPersonalDomainActivationHost.
  • Opt in to the PersonalOS domain activation boundary

    Additive only. Existing compositions are unchanged; finance routes return 503 until a host injects domainActivation and finance.

    1. Provide activationForSubject, consentFactsForSubject, keyRecovery.isBound and outboxProcessor.ready as domainActivation.
    2. Provide scenarioIntegrity and consentsForSubject as finance.
  • Pass the typed executor to IntercomSupportAdapter

    Required

    IntercomSupportAdapter.dispatch no longer sends conversation actions through resolveIntercomCommand. Pass an IntercomConversationActionExecutor as the last constructor argument and include actorRef in the payload; without it, support.reply/note/assign/snooze/reopen/close fail closed.

    1. Construct IntercomSupportAdapter with an IntercomConversationActionExecutor.
    2. Add actorRef (Intercom admin id) and, for reply/close, approvalRef to dispatch payloads.
  • Apply SupportOS migration 0059

    Required

    Additive tables for conversation action custody and support resolutions; deploy schema before writers.

    1. Run the SupportOS migration runner to 0059_supportos_conversation_actions.
  • Enable AI-written OPA briefings

    Additive. Without the flag every briefing remains the labelled standard template.

    1. Apply app migration 0125 (opa_ai_briefing_workspace_models) through the tracked runner.
    2. Record the processing and Gateway transit approvals, then set OPA_AI_BRIEFINGS_PROCESSING_APPROVAL_REF and OPA_AI_BRIEFINGS_GATEWAY_TRANSIT_APPROVAL_REF.
    3. Ensure Gateway access (Vercel OIDC or AI_GATEWAY_API_KEY), optionally set OPA_AI_DEFAULT_MODEL, then set OPA_AI_BRIEFINGS_ENABLED=1 and redeploy the API.
  • Enable Gateway meeting transcription

    Additive and off by default; no EU-qualified model exists yet, so status stays no_eu_model.

    1. Ship a reviewed catalog entry once the Gateway endpoint listing shows an EU inference zone with zero data retention for a transcription model.
    2. Record processing and Gateway transit approvals, then set OPA_TRANSCRIPTION_PROCESSING_APPROVAL_REF and OPA_TRANSCRIPTION_GATEWAY_TRANSIT_APPROVAL_REF.
    3. Set OPA_TRANSCRIPTION_ENABLED=1 and OPA_CAPTURE_PROCESSING_ENABLED=1 on the API project and redeploy.
  • Enable owner-approved non-EU meeting transcription

    Off by default; no database migration.

    1. Record the non-EU processing and transfer decisions (text in the evidence file) and obtain their refs.
    2. Set OPA_TRANSCRIPTION_NON_EU_PROCESSING_APPROVAL_REF and OPA_TRANSCRIPTION_NON_EU_TRANSFER_APPROVAL_REF next to the existing transit ref, OPA_TRANSCRIPTION_ENABLED=1 and OPA_CAPTURE_PROCESSING_ENABLED=1, then redeploy the API.
    3. Confirm /api/companyos/health/degraded reports opaTranscription enabled and opaTranscriptionProcessingRegion non_eu.
  • Optionally report unexpected Forms failures

    Additive. Hosts that relied on their framework's uncaught-error logging for Forms failures should pass reportUnexpectedError, because the handler now converts those failures into responses.

    1. Pass reportUnexpectedError to createPostgresFormsHttpHandler and log the correlationId without the error message.
  • Opt in to reference mode to run commands locally

    Security fix: commands previously ran for any caller holding a non-empty key. Local and demo setups that run the deterministic command bindings must opt in explicitly; production keeps them denied until lib.auth-os verifies keys.

    1. Set MANAGED_COMPANYOS_MCP_REFERENCE_MODE=1 (and a NODE_ENV other than production) where reference commands must run.
    2. Do not rely on resolveActor() returning admin or the operations_manager role.
  • Staff an independent verifier for code-producing team runs

    Required

    Minor, behavioural tightening. Specs and persisted team state stay readable, but two flows that used to complete now fail closed: creating (or building from a plan pack) a code-producing run with verificationLane.required false is rejected, and a verifier approval decided by a task participant does not satisfy finalization. Worker add/remove on a run persisted before the upgrade re-validates its spec in amend mode, so an in-flight code-producing run without a verification lane can still change membership, and it still finalizes without a verifier. Task records persisted before the upgrade have no claimHistory, so their earlier, reclaimed claimants are recognized only through heartbeats that reported a task.

    When: When a team run declares writePaths, or when the same worker or principal both does task work and approves the run.

    1. Set verificationLane.required to true for any team run whose backlog declares writePaths, or drop writePaths for runs that do not change code.
    2. Record the verifier approval with a decidedBy actor that did no task work in the run (a separate verifier principal or a human), and pass actorId to the claim, evidence and completion calls so the run can tell the two apart.
    3. Remove surrounding whitespace from requiredEvidence entries; validation now rejects them.
    4. Optionally declare requiredEvidence on backlog tasks, and attach bundles saved to the lane store whose classes cover it before calling completeTask.
  • Apply managed economics migrations 0190–0194

    Required

    Apply after 0120–0123. Runtime connections must use the NOSUPERUSER NOBYPASSRLS managed_companyos_app role and set app.tenant_id per transaction from the authenticated session.

    1. Create managed_companyos_app (NOSUPERUSER NOBYPASSRLS) before applying 0194 wherever the runtime connects as that role; 0194 skips the grants when the role is absent.
    2. Read the durable stores from createManagedEconomicsStores(database, sessionScope).durable; the scope comes from the authenticated session, never from a request body.
  • Optionally call the new PersonalOS owner subpaths

    Additive; existing imports keep working. Hosts may compose the owner subpaths instead of application-local copies.

    1. Import the behavior from the owner subpath listed in the changeset instead of an app-local copy.
  • Expect fail-closed presentation access with a 5-minute window (D31)

    The PersonalOS web host's presentation freshness window tightens from 15 to 5 minutes. The desktop host now treats a missing or stale presentation as unavailable (never allowed) and blocks every governed action; it previously allowed area access without a presentation and never expired one. Mobile action and area lookups now require exact area-bound matches.

    1. Refresh the experience projection at least every 5 minutes on surfaces that submit governed actions.
  • Expect the canonical bounded offline replay on web and desktop (D31)

    Web and desktop replay now block a command after 5 attempts, re-check the offline registry, risk and undo before every dispatch, and defer transient failures with exponential backoff (persisted nextAttemptAt, capped at 15 minutes). Web blocks 401/403/409/other 4xx terminally and records the canonical reason (for example revision_conflict) instead of http_<status>; desktop continues past terminal blocks and blocks registry lookalikes as policy_changed.

    1. Treat blocked outbox entries as needing user recovery; they are kept, not deleted.
  • Web life-admin commands carry surface evidence

    The PersonalOS web host's life-admin commands now include the web surface evidence reference instead of an empty evidenceRefs list.

    1. No action required; servers receive one additional assurance evidence reference.
  • Optionally call the new AuthOS owner subpaths

    Additive only; existing imports and behavior are unchanged. Hosts may implement the owner ports (AuthEmailAddressStore, WaitlistAdminStore, OperatorAuthRepository) and call the owner rules instead of keeping app-local copies.

    1. Import the rules from the lib.authos-runtime subpath or the integration ./server entry instead of an app-local copy.
    2. Keep host SQL, environment wiring and transport in the app, implementing the owner port.
  • Optionally use the new CommunicationOS owner subpaths

    Additive only; existing imports are unchanged. Hosts that re-implement a session engine, outbox replay, delivery gate, Discord analysis rules or a live-room controller can call the owner subpaths instead.

    1. Import createCommunicationOsSessionEngine from '@lssm-tech/integration.communication-os-client/session-engine' and inject the host outbox and onUnauthorized handler.
    2. Import createCommunicationDeliveryDispatcher from '@lssm-tech/lib.communication-runtime/ecosystem-delivery-dispatcher' and pass provider target rules through verifyTarget.
  • Optionally build PersonalOS envelopes through the runtime subpath

    Additive only; existing imports are unchanged. Hosts may call the new subpath instead of keeping a host-local envelope literal or digest-binding helper.

    1. Replace a host-local envelope literal with buildUnboundPersonalCommandEnvelopeV1 and pass the host identifiers and surface evidence.
    2. Replace a host-local parse-digest-reparse helper with bindPersonalWorkspaceCommandV1.
  • Optionally adopt the new auth and customer-support owner subpaths

    Additive only; existing imports are unchanged. Hosts may bind the new ports instead of re-implementing the flows locally.

    1. Pass the identity origin explicitly to assertSafeOAuthRedirect from @lssm-tech/lib.authos-runtime/oauth-request.
    2. Bind createHttpWaitlistAdapter with your product scope and pair it with useWaitlistJoin / useWaitlistStatus.
    3. Implement LinkedAccountsAdapter, PasskeyManagementAdapter, InvitationAcceptanceAdapter or PassportPrivacyAdapter and use the matching module hook.
    4. Implement SupportCustomerSessionSecurity and SupportCustomerLiveChatTransport and compose createSupportCustomerSessionService.
  • Adopt portable command declarations when needed

    Existing public packs require no binding migration; portable declarations are an additive choice.

    1. Use createProgram from @lssm-tech/bundle.workspace/cli for the existing ContractSpec command composition.
    2. Keep the existing public optional pack commandPack/default entry for automatic canonical actions and AI core extensions.
    3. New portable hosts may use cli-runtime optional-command-declarations entries and bind exact action suppliers explicitly.
    4. Per-program cli-runtime registrations are process-shared, so the self-contained CLI host bundle and separately installed packs observe the same bindings; externalizing cli-runtime in pack producers remains supported.
    5. The published @lssm-tech/app.cli-contractspec stays a self-contained bundle with zero runtime dependencies.
    6. Build the workspace bundle to regenerate its offline MCP knowledge corpus; app hosts retain lazy optional snapshot bindings.
    7. Registry hosts retain their original optional snapshot lookup through the provider-free cli/snapshot-client binding entry.
  • Replace @lssm-tech/lib.contracts-spec/content-generation/<leaf> with...

    Replace @lssm-tech/lib.contracts-spec/content-generation/<leaf> with @lssm-tech/lib.content-analysis-spec/content-generation/<leaf> and the barrel @lssm-tech/lib.contracts-spec/content-generation with @lssm-tech/lib.content-analysis-spec/content-generation.

    1. Replace @lssm-tech/lib.contracts-spec/content-generation/<leaf> with @lssm-tech/lib.content-analysis-spec/content-generation/<leaf> and the barrel @lssm-tech/lib.contracts-spec/content-generation with @lssm-tech/lib.content-analysis-spec/content-generation.
  • Replace @lssm-tech/lib.contracts-spec/decisioning[/<leaf>] with...

    Replace @lssm-tech/lib.contracts-spec/decisioning[/<leaf>] with @lssm-tech/lib.decision-runtime/contracts[/<leaf>].

    1. Replace @lssm-tech/lib.contracts-spec/decisioning[/<leaf>] with @lssm-tech/lib.decision-runtime/contracts[/<leaf>].
  • Historical execution-lanes imports remain supported

    Historical execution-lanes imports remain supported; pure consumers may import the explicit orchestration-spec execution-lanes family.

    1. Historical execution-lanes imports remain supported; pure consumers may import the explicit orchestration-spec execution-lanes family.
  • Replace @lssm-tech/lib.lssm-os-spec/context/catalog-locator-node (and its .browser subpath)...

    Required

    Replace @lssm-tech/lib.lssm-os-spec/context/catalog-locator-node (and its .browser subpath) with @lssm-tech/lib.lssm-os-runtime/catalog-locator-node; the function name, arguments, results and browser fallback are identical.

    1. Replace @lssm-tech/lib.lssm-os-spec/context/catalog-locator-node (and its .browser subpath) with @lssm-tech/lib.lssm-os-runtime/catalog-locator-node; the function name, arguments, results and browser fallback are identical.
  • Pass the fourth argument of validateLssmCanonicalCatalogV2(ecosystem, bindings, capsule, now)...

    Required

    Pass the fourth argument of validateLssmCanonicalCatalogV2(ecosystem, bindings, capsule, now) from a trusted clock (for example new Date() in a host); omitting it now returns ['catalog.clock_required'] instead of reading the ambient clock.

    1. Pass the fourth argument of validateLssmCanonicalCatalogV2(ecosystem, bindings, capsule, now) from a trusted clock (for example new Date() in a host); omitting it now returns ['catalog.clock_required'] instead of reading the ambient clock.
  • Replace @lssm-tech/lib.contracts-spec/osint/<leaf> with...

    Replace @lssm-tech/lib.contracts-spec/osint/<leaf> with @lssm-tech/lib.osint-spec/contracts/<leaf> and the barrel @lssm-tech/lib.contracts-spec/osint with @lssm-tech/lib.osint-spec/contracts. The @lssm-tech/lib.osint-spec root barrel additionally carries the fresh-authority registry bindings and is not a drop-in replacement for the compatibility barrel.

    1. Replace @lssm-tech/lib.contracts-spec/osint/<leaf> with @lssm-tech/lib.osint-spec/contracts/<leaf> and the barrel @lssm-tech/lib.contracts-spec/osint with @lssm-tech/lib.osint-spec/contracts. The @lssm-tech/lib.osint-spec root barrel additionally carries the fresh-authority registry bindings and is not a drop-in replacement for the compatibility barrel.
  • Existing quality imports remain supported

    Existing quality imports remain supported; lower owners use the assurance quality entries directly.

    1. Existing quality imports remain supported; lower owners use the assurance quality entries directly.
  • Existing callers require no migration

    Existing callers require no migration. New composition consumers should use the customer-support-runtime platform-authority subpath.

    1. Existing callers require no migration. New composition consumers should use the customer-support-runtime platform-authority subpath.
  • Optionally call the new OSINT and job-source owner subpaths

    Additive only; existing imports are unchanged. Hosts may call the new owner subpaths instead of reimplementing worker-local policy.

    1. Import the policy from the osint-runtime or job-source-runtime subpath instead of a worker-local copy.

Upgrade steps

  • Configure the independent identity host before activation

    assisted

    Bind verified email, creation admission and each privileged capability to real host authority.

    Packages: @lssm-tech/lib.authos-spec, @lssm-tech/lib.authos-runtime, @lssm-tech/module.auth-os, @lssm-tech/integration.authos-better-auth, @lssm-tech/integration.runtime, @lssm-tech/integration.provider-project-management, @lssm-tech/integration.provider-reddit, @lssm-tech/integration.provider-email, @lssm-tech/integration.provider-calendar, @lssm-tech/integration.provider-payments, @lssm-tech/integration.provider-tiktok, @lssm-tech/integration.communication-os-persistence, @lssm-tech/lib.contracts-integrations, @lssm-tech/bundle.managed-companyos, @lssm-tech/app.communicationos-api

    1. Configure verified identity email, creation admission and explicit privileged-plugin authority.
    2. Keep existing product defaults unless the product explicitly adopts a new policy.
    3. Complete real provider and relying-party qualification before recording production activation.
  • Compose the profile registry in OSINT hosts

    manual

    osint-api, osint-mcp and osint-worker build the registry once from the G catalog at startup; a malformed catalog fails at startup with the issue list.

    Packages: @lssm-tech/lib.osint-runtime, @lssm-tech/integration.osint-managed-runtime, @lssm-tech/lib.companyos-spec, @lssm-tech/lib.lssm-os-spec, @lssm-tech/integration.job-sources, @lssm-tech/lib.creator-operations-spec, @lssm-tech/integration.job-application-browser

    1. Set OSINT_DEPLOYMENT_PROFILE_ID to a catalog profile id or keep OSINT_DEPLOYMENT_ID for resolveKnown resolution; an unknown profile id throws OSINT_DEPLOYMENT_PROFILE_UNKNOWN.
  • Configure the subject-binding read bearer on both hosts

    manual

    Set the same distinct 32+ character value as OSINT_GOVERNED_SUBJECT_BINDINGS_READ_TOKEN on the OSINT host and LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDINGS_READ_TOKEN on the identity host, plus the OSINT origin.

    Packages: @lssm-tech/lib.data-exchange-core, @lssm-tech/integration.governed-data-postgres, @lssm-tech/integration.osint-store, @lssm-tech/lib.osint-spec

    1. Keep the token distinct from OSINT_SOURCE_RIGHTS_INGRESS_TOKEN, SELF_IMPROVEMENT_WORKLOAD_TOKEN and every governed bearer.
  • Configure the hand-back and operator bearers

    manual

    Set the same distinct 32+ character value as OSINT_GOVERNED_SUBJECT_BINDING_REFS_WRITE_TOKEN on the OSINT host and LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDING_REFS_WRITE_TOKEN on the identity host, plus the OSINT origin; set OSINT_SOURCE_RIGHTS_EXPIRY_SWEEP_OWNER=worker on the api host when the worker owns the sweep.

    Packages: @lssm-tech/lib.osint-runtime, @lssm-tech/integration.osint-store, @lssm-tech/lib.osint-spec

    1. Keep every bearer distinct from the other OSINT and governed bearers.
  • Apply job-application-store migration 0023 before the runtime

    manual

    The candidate opportunity operations need the two tables created by 0023_candidate_opportunities.sql.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-managed-runtime

    1. Apply packages/integrations/job-application-store/migrations/0023_candidate_opportunities.sql.
    2. Deploy the runtime, API and MCP hosts with JOB_APPLICATION_MATERIAL_KEY_BASE64 set to enable the operations.
  • Apply the job-application-store candidate questions migration before the runtime

    manual

    The question operations need the three tables created by 0027_candidate_questions.sql.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-managed-runtime

    1. Apply packages/integrations/job-application-store/migrations/0027_candidate_questions.sql.
    2. Deploy the runtime and hosts with JOB_APPLICATION_MATERIAL_KEY_BASE64 set to enable the operations.
  • Wire a packet source before enabling the focused effects module

    assisted

    Focused submits are refused before dispatch as input_refused until the managed runtime service receives a JobApplicationSubmitPacketSourceV1.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-effects-focused

    1. Pass the resource service as the packet source to JobApplicationServiceV1 in the managed runtime behind an explicit deployment flag.
    2. Re-issue mandates with exact job-application-profile:<id>:<revision> refs as new revisions before enabling the flag.
  • Implement listProfileFactInvalidations on custom packet sources

    manual

    JobApplicationSubmitPacketSourceV1.listProfileFactInvalidations is now required so a missing invalidation read fails closed.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-store

    1. Add listProfileFactInvalidations to every custom JobApplicationSubmitPacketSourceV1 implementation; the Postgres resource service already implements it.
  • Re-issue mandates with exact profile refs before enabling packet binding

    assisted

    Opaque mandate profile refs keep working only on the legacy path; enabling the flag refuses them.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-managed-runtime, @lssm-tech/integration.job-application-effects-focused, @lssm-tech/integration.job-application-effects-dependencies-railway

    1. Re-issue each mandate as a new revision whose profileRevisionRef is formatJobApplicationRevisionRefV1('job-application-profile:', { id, revision }).
    2. Let applications already in flight under the old mandate revision finish on the legacy path or re-plan them, because re-issuing makes them refuse as APPLICATION_PROFILE_STALE.
    3. Set JOB_APPLICATION_PACKET_BINDING_ENABLED=true per deployment only after the host composition reads it.
  • Apply job-application-store migrations 0025 and 0026 before the runtime

    manual

    The subject binding, consent, disclosure tables and the erasure triggers are created by 0025_candidate_subject_bindings.sql and 0026_destination_disclosures.sql.

    Packages: @lssm-tech/lib.job-application-runtime, @lssm-tech/integration.job-application-store, @lssm-tech/integration.job-application-managed-runtime

    1. Apply packages/integrations/job-application-store/migrations/0025_candidate_subject_bindings.sql.
    2. Apply packages/integrations/job-application-store/migrations/0026_destination_disclosures.sql.
    3. Deploy the runtime and hosts; inject the AuthOS admission verifier where products bind subjects.
  • Apply osint-store migration 0035 before the runtime

    manual

    The taxonomy store needs the osint_reference schema, tables, grants and the osint_reference_reader role created by 0035_osint_reference_taxonomy.sql.

    Packages: @lssm-tech/lib.osint-spec, @lssm-tech/lib.osint-runtime, @lssm-tech/module.osint, @lssm-tech/integration.osint-store

    1. Apply packages/integrations/osint-store/migrations/0035_osint_reference_taxonomy.sql after 0001-0034.
  • Apply osint-store migration 0036 and configure the read bearer

    manual

    The source-rights heads and emissions tables are created by 0036_osint_source_rights_outbox.sql; the current read now needs its own bearer on the source product host.

    Packages: @lssm-tech/lib.osint-runtime, @lssm-tech/integration.osint-store

    1. Apply packages/integrations/osint-store/migrations/0036_osint_source_rights_outbox.sql.
    2. Set COMPANYOS_GOVERNED_SOURCE_RIGHTS_CURRENT_READ_TOKEN / LSSM_OS_GOVERNED_SOURCE_RIGHTS_CURRENT_READ_TOKEN on the source product host to the identity host's LSSM_GOVERNED_*_SOURCE_RIGHTS_CURRENT_TOKEN.
    3. Set the OSINT host dispatch env only after the outbox binding is deployed.
  • Find chrome-dropped CodeBlock callsites by the emitted marker

    manual

    Grep RICH_REF_CHROME_RESTORED instead of the retired TODO(rich-ref migration) anchor.

    Packages: @lssm-tech/tools.contractspec-codemods

    1. Grep for RICH_REF_CHROME_RESTORED (not TODO(rich-ref migration): re-add chrome) to find CodeBlock callsites that lost filename, description, comment or showDownloadButton.
    2. Review migrated DiffBlock callsites by hand; the DiffBlock codemod keeps only oldText, newText and language and emits no marker for the props it drops.
  • Verify the relying-party catalog and its consumers

    auto

    Run the AuthOS spec tests and typecheck, then the catalog consumer tests.

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

    1. Run bun test packages/domains/identity/spec/src and bun run --cwd packages/domains/identity/spec typecheck.
    2. Run bun test packages/domains/identity/runtime/src/oauth-request.test.ts packages/integrations/authos-better-auth/src/relying-party-reconciliation.test.ts.
  • Connect the PersonalOS meeting context consumer

    manual

    Operator step once a PersonalOS host serves the consumer routes; until then leave both variables unset.

    Packages: @lssm-tech/lib.personal-os-spec, @lssm-tech/lib.personal-os-runtime, @lssm-tech/integration.opa-meeting-context-bridge

    1. On a PersonalOS host, mount POST /v1/consumers/meeting-context/read and POST /v1/consumers/meeting-context/memory behind a service bearer, resolve companyos:user:<userId> through a verified account link, and answer with answerPersonalMeetingContextReadV1 / decidePersonalMeetingMemoryIntakeV1 on the host clock, storing memory entries and receipts atomically with entry-id dedupe.
    2. Set OPA_PERSONALOS_BRIDGE_URL (HTTPS origin) and OPA_PERSONALOS_BRIDGE_TOKEN (≥ 32 bytes, from the secret store) on the CompanyOS API, run a consented read canary on a staging owner, then add personalos_private_memory to OPA_MEETING_FOLLOWUP_TARGETS.
    3. Keep hcircle_space and pactena_workspace out of OPA_MEETING_FOLLOWUP_TARGETS until their hosts exist (B231, B240).
  • Verify the product channel composition

    auto

    Run the notification, Pactena and PersonalOS composition tests.

    Packages: @lssm-tech/lib.notification

    1. Run the product-channels tests in lib.notification.
    2. Run the Pactena communication journey, notification preference and calendar intake tests.
    3. Run the PersonalOS life-admin channel effect tests.
  • Update the ContractSpec CLI and regenerate agent outputs

    manual

    The new SessionStart hook needs a ContractSpec CLI that supports can-help catalog status --host; an older CLI rejects the option and Claude Code reports a non-blocking hook error. An older CLI also answers adoption hooks in a Connect-disabled workspace with a fail-closed prompt, so install the matching CLI before regenerating.

    Packages: @lssm-tech/agentpack.contractspec

    1. Install the ContractSpec CLI release that ships can-help catalog status --host alongside this pack.
    2. Re-run contractspec init (or regenerate with agentpacks) so .claude/settings.json and the scoped catalog memory rule are refreshed.
  • Optionally restrict editable organization profile fields

    manual

    Hosts whose slug anchors authority should allow only the name.

    Packages: @lssm-tech/lib.authos-spec, @lssm-tech/lib.authos-runtime, @lssm-tech/integration.authos-better-auth, @lssm-tech/module.auth-os

    1. Set organizationGuardrails.editableProfileFields to ['name'] in the Better Auth bridge config.
    2. Provide organizationGuardrails.onAudit to append organization audit events to the host ledger.
  • Verify COMMUNICATION_OS_OAUTH_HOST_ORIGINS keys

    manual

    Key the map by the host-exchange issuer, not by the access-token issuer.

    Packages: @lssm-tech/integration.communication-os-host-auth, @lssm-tech/app.communicationos-api

    1. Confirm each COMMUNICATION_OS_OAUTH_HOST_ORIGINS key equals a configured host issuer such as COMMUNICATION_OS_COMPANYOS_ISSUER, and remove any https://api.hcircle.app key.
  • Use OpportunityWave@1.1.0 for sales-assisted or creative-led discovery

    manual

    Choose selfserve-first or sales-assisted per wave; validate with validateOpportunityDiscoveryWave.

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

    1. Existing 1.0.0 waves need no change and replay with identical hashes.
    2. Set schemaVersion 1.1.0 and profileId sales-assisted to admit AI-prepared, human-voiced calls within two calls and 90 planned minutes per closed account; fail bounded_sales_effort for plays above the ceiling.
    3. Declare paid or AI UGC as a productionAsset paired with a reach method; never present a paid or synthetic person as a customer.
    4. Keep any primary method at or below 25% of a wave of eight or more drafts, across at least four method families.
    5. Load the distribution extension catalogs for the new method, production-asset and metric IDs; their numbers stay editorial priors.
    6. A shortlist is not authorization to call, send, publish, spend or build.
  • Refresh generated agent guidance

    assisted

    Regenerate the managed agent guidance so agents see the run-mode rules.

    Packages: @lssm-tech/agentpack.contractspec, @lssm-tech/lib.cli-runtime

    1. Run contractspec init (or contractspec onboard) to refresh the AGENTS.md and USAGE.md managed blocks and the curated agent pack.
  • Regenerate agent host hook configuration

    manual

    Consumers that generate hooks from the contracts-spec pack pick up the PowerShell matcher after regeneration.

    Packages: @lssm-tech/lib.cli-runtime, @lssm-tech/bundle.workspace

    1. Run bun run agentpacks:all and confirm bun run agentpacks:diff reports no changes.
  • Use the separate draft discovery entrypoints

    manual

    Evaluate captured hypotheses with the versioned selfserve-first profile before canonical mature scoring.

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

    1. Import the opportunity-spec/discovery schemas and opportunity-runtime/discovery projections.
    2. Supply catalog records and a fixed as-of date; keep priors, scenarios and observations distinct.
    3. Use opportunity-runtime/economics with explicit cost coverage, allocations, payer units and matching horizons.
    4. The mature portfolio API remains unchanged and can return a blocked primary on all-blocked input; use the new empty-safe draft shortlist for discovery.
    5. A shortlist or promotion is not authorization to build, contact, deploy, publish campaigns or spend money.

Unique release changes

  • Bind verified email, creation admission and each privileged capability to real host authority.

    15 packages · 15 occurrences

  • Independent central identity registration, management, reviewed applications and separately consented platform reads.

    15 packages · 15 occurrences

  • Preserve existing identity and product records while installing official plugin and central lifecycle models.

    15 packages · 15 occurrences

  • Additive. Without the flag every briefing remains the labelled standard template.

    9 packages · 9 occurrences

  • OPA morning recaps and meeting preparation can be written by an allowlisted, EU-routed model through the Vercel AI Gateway once the owner opts in. Every claim links to its source. Otherwise the labelled standard template is sent.

    9 packages · 9 occurrences

  • Content-generation contract definitions move from the contracts-spec compatibility facade to the content domain spec @lssm-tech/lib.content-analysis-spec with identity-preserving forwards

    8 packages · 8 occurrences

  • Existing public packs require no binding migration; portable declarations are an additive choice.

    8 packages · 8 occurrences

  • Existing subjects lose health and life-admin access until activated. Run the idempotent backfill once; it only activates subjects with a current consent.

    8 packages · 8 occurrences

  • Extract shared CLI composition and neutral host assembly without host-to-host dependencies.

    8 packages · 8 occurrences

  • OSINT contract definitions move from the contracts-spec compatibility facade to their existing owner @lssm-tech/lib.osint-spec with identity-preserving forwards

    8 packages · 8 occurrences

  • PersonalOS activation carry-forward migration, live host-binding probes, gated health/life-admin routes, encrypted health routine and FinanceOS company tax handoff

    8 packages · 8 occurrences

  • Remove client-to-server reach and wrong ownership edges found by the W3 package boundary check.

    8 packages · 8 occurrences

  • Replace @lssm-tech/lib.contracts-spec/content-generation/<leaf> with @lssm-tech/lib.content-analysis-spec/content-generation/<leaf> and the barrel @lssm-tech/lib.contracts-spec/content-generation with @lssm-tech/lib.content-analysis-spec/content-generation.

    8 packages · 8 occurrences

  • Replace @lssm-tech/lib.contracts-spec/osint/<leaf> with @lssm-tech/lib.osint-spec/contracts/<leaf> and the barrel @lssm-tech/lib.contracts-spec/osint with @lssm-tech/lib.osint-spec/contracts. The @lssm-tech/lib.osint-spec root barrel additionally carries the fresh-authority registry bindings and is not a drop-in replacement for the compatibility barrel.

    8 packages · 8 occurrences

  • Additive only. Existing compositions are unchanged; finance routes return 503 until a host injects domainActivation and finance.

    7 packages · 7 occurrences

  • Brand-specific OSINT deployment profiles, founder-context and organization-bootstrap seeds, seed-map paths and donor provenance move to governed lssm-os-spec G catalogs; domain and integration owners become brand-neutral.

    7 packages · 7 occurrences

  • Hosts load osint.deployment-profiles@1 from @lssm-tech/lib.lssm-os-spec/catalog/osint-deployment-profiles, build the registry once with defineOsintDeploymentProfileRegistryV0 and pass it to the resolvers and to createManagedOsintOperationHandlerV0. The removed Hirly profile/program constants have no replacement in lib.osint-runtime.

    7 packages · 7 occurrences

  • Off by default; no database migration.

    7 packages · 7 occurrences

  • OPA meeting transcription can be enabled through an explicitly owner-approved non-EU Gateway model (microsoft/mai-transcribe-2, zero data retention, no training) while no EU transcription zone exists; it stays no_eu_model until the approvals are recorded. The capture worker gains exponential backoff, HTTP status classification, fenced idempotent completion, structured logs and a usage metering hook.

    7 packages · 7 occurrences

  • osint-api, osint-mcp and osint-worker build the registry once from the G catalog at startup; a malformed catalog fails at startup with the issue list.

    7 packages · 7 occurrences

  • PersonalOS activation boundary, tax recovery dossiers, scoped finance review and subject-private health routines

    7 packages · 7 occurrences

  • Replace the seed-map path constants with seedMapCatalogPathV1(mapId); read DONOR_PINS_V1[].sourceRef instead of repository (resolveLssmDonorSourceV1 maps it to the repository); rename readiness owner 'hirly' to 'host_product' and capability hirly-export-cutover to legacy-host-export-cutover.

    7 packages · 7 occurrences

  • Additive and off by default; no EU-qualified model exists yet, so status stays no_eu_model.

    6 packages · 6 occurrences

  • Brand-neutral domain owners (D117-FIX-01) - company.offering@1 projection, consumer-isolated OSINT deployment row, catalog-driven founder contexts and organization slugs, neutral recruiting and creator copy.

    6 packages · 6 occurrences

  • Decisioning contracts and ports move from the contracts-spec compatibility facade to @lssm-tech/lib.decision-runtime/contracts with identity-preserving forwards

    6 packages · 6 occurrences

  • FOUNDER_CONTEXT_IDS and the closed slug union are gone; ids are branded and validated against a registry or manifest.

    6 packages · 6 occurrences

  • New plugin models use auth-owner tables and are denied to product and Supabase API roles.

    6 packages · 6 occurrences

  • OPA meeting recordings are transcribed only through the Vercel AI Gateway with EU inference, zero data retention and no training. The feature stays disabled until the Gateway lists an EU transcription endpoint.

    6 packages · 6 occurrences

  • Replace @lssm-tech/lib.contracts-spec/decisioning[/<leaf>] with @lssm-tech/lib.decision-runtime/contracts[/<leaf>].

    6 packages · 6 occurrences

  • Sixteen-provider AuthOS configuration, guarded official plugin wiring, and central passwordless MFA and email fixes.

    6 packages · 6 occurrences

  • The Patio* company offering projection types and values are deprecated aliases of the CompanyOffering* names and are removed in the next major release.

    6 packages · 6 occurrences

  • The projection id and error codes are renamed; persisted grants or catalog rows outside this repository that hold patio.company_offering.v1 no longer match.

    6 packages · 6 occurrences

  • Additive tables for conversation action custody and support resolutions; deploy schema before writers.

    5 packages · 5 occurrences

  • Additive; existing imports keep working. Hosts may compose the owner subpaths instead of application-local copies.

    5 packages · 5 occurrences

  • Canonically own the unchanged reviewed planning handoff protocol below Builder.

    5 packages · 5 occurrences

  • Existing callers require no migration. New composition consumers should use the customer-support-runtime platform-authority subpath.

    5 packages · 5 occurrences

  • IntercomSupportAdapter.dispatch no longer sends conversation actions through resolveIntercomCommand. Pass an IntercomConversationActionExecutor as the last constructor argument and include actorRef in the payload; without it, support.reply/note/assign/snooze/reopen/close fail closed.

    5 packages · 5 occurrences

  • job-application-store migrations/0031_cv_ingestion.sql (generated verbatim from cvIngestionMigrationSqlV1, D-172) adds the five FORCE RLS append-only cv_* tables and the candidate-erasure trigger that removes CV ingestion rows.

    5 packages · 5 occurrences

  • Own existing generic command input and error helpers in CLI runtime.

    5 packages · 5 occurrences

  • PersonalOS host offline replay, offline admission, presentation access, journey catalog, command context, command builders and governed projection transport move to owner packages

    5 packages · 5 occurrences

  • PROPOSED_NOT_ADMITTED additive canonical development lifecycle, native provider registration, durable journal and secret custody composition.

    5 packages · 5 occurrences

  • PROPOSED_NOT_ADMITTED private contract-first development resource JWT/workload registration and durable scoped OSINT authority receipt/revocation preparation. Registration rejects before effects without actual canonical reviewed-profile verification.

    5 packages · 5 occurrences

  • Single brand-neutral candidate-private CV ingestion owner (encrypted original custody with write-ahead intents, bounded PDF/DOCX/text extraction into immutable private text revisions, candidate review, proposed facts through the single profile-evidence writer, gated image transcription port).

    5 packages · 5 occurrences

  • Support action custody and resolutions persist in Postgres, resolution operations get HTTP routes bound to the canonical approval runtime, and personal device events ingest read-only into CommunicationOS

    5 packages · 5 occurrences

  • SupportOS platform authority composition moves to its canonical runtime owner with identical compatibility exports

    5 packages · 5 occurrences

  • The PersonalOS web host's life-admin commands now include the web surface evidence reference instead of an empty evidenceRefs list.

    5 packages · 5 occurrences

  • The PersonalOS web host's presentation freshness window tightens from 15 to 5 minutes. The desktop host now treats a missing or stale presentation as unavailable (never allowed) and blocks every governed action; it previously allowed area access without a presentation and never expired one. Mobile action and area lookups now require exact area-bound matches.

    5 packages · 5 occurrences

  • Web and desktop replay now block a command after 5 attempts, re-check the offline registry, risk and undo before every dispatch, and defer transient failures with exponential backoff (persisted nextAttemptAt, capped at 15 minutes). Web blocks 401/403/409/other 4xx terminally and records the canonical reason (for example revision_conflict) instead of http_<status>; desktop continues past terminal blocks and blocks registry lookalikes as policy_changed.

    5 packages · 5 occurrences

  • 0155 (authos_trusted_device_labels) backs the trusted-device list; until it is applied the list answers an error (sign-in and remember-device still work). 0156 adds nullable phone columns; the API selects them only when AUTHOS_PHONE_OTP_ENABLED=1, so it can be applied ahead of the flag.

    4 packages · 4 occurrences

  • Additive only; existing imports are unchanged. Hosts may bind the new ports instead of re-implementing the flows locally.

    4 packages · 4 occurrences

  • Additive only; existing imports are unchanged. Hosts that re-implement a session engine, outbox replay, delivery gate, Discord analysis rules or a live-room controller can call the owner subpaths instead.

    4 packages · 4 occurrences

  • Apply 0037_osint_governed_subject_bindings.sql with the migrator role; the runtime role must stay NOSUPERUSER NOBYPASSRLS. The table starts empty; organization issuance answers subject_binding_unavailable until an operator records bindings.

    4 packages · 4 occurrences

  • Auth and customer-support host behavior moves to authos-runtime, auth-os, customer-support-spec and customer-support

    4 packages · 4 occurrences

  • AuthOS account self-service — profile, password, verified email change, secondary emails, and account deletion

    4 packages · 4 occurrences

  • Brand-neutral public reference taxonomy across osint spec, runtime, module and store, with store migration 0035.

    4 packages · 4 occurrences

  • Candidate surfaces (REST/SDK/MCP/CLI) to list and answer the profile-scoped CV ingestion questions (D-181), wired in the operation handler and the managed composition, with a two-connection PostgreSQL proof of the profile question lock and currency.

    4 packages · 4 occurrences

  • Candidate-side list/get queries of the typed candidate questions and a pinned answer-ref resolver; no migration.

    4 packages · 4 occurrences

  • CommunicationOS client session, delivery, community and live-room behavior moves to its owners

    4 packages · 4 occurrences

  • Complete the AuthOS Organization page with profile editing, server-enforced membership guardrails, a leave flow, and honest settings.

    4 packages · 4 occurrences

  • Connect with LSSM stays closed in production until a human approves docs/evidence/authos/connect-lssm-security-review-2026-10-19.md and records AUTHOS_CONNECT_LSSM_REVIEW_APPROVAL_REF. Phone codes need AUTHOS_PHONE_OTP_ENABLED=1 plus AUTHOS_SMS_TWILIO_ACCOUNT_SID, AUTHOS_SMS_TWILIO_AUTH_TOKEN and AUTHOS_SMS_TWILIO_FROM_NUMBER.

    4 packages · 4 occurrences

  • Hosts whose slug anchors authority should allow only the name.

    4 packages · 4 occurrences

  • Managed packet source behind a deployment control, non-effect killed submits and shared destination and revision-ref helpers

    4 packages · 4 occurrences

  • Opaque mandate profile refs keep working only on the legacy path; enabling the flag refuses them.

    4 packages · 4 occurrences

  • OSINT public text is decoded before scanning, profile URLs are matched by host, withheld paths are structural, withheld search URLs are digested in canonical keys and projections hold no personal values

    4 packages · 4 occurrences

  • Per-organization enterprise SSO (OIDC + SAML 2.0) with verified domains, enforcement, JIT provisioning and SCIM 2.0.

    4 packages · 4 occurrences

  • Preserve shared library exports with explicit package entries

    4 packages · 4 occurrences

  • Production organization issuance composes real offers, subject-binding and source-rights ports; OSINT owns append-only trusted organization subject bindings; governed bearer env names derive from the AuthOS registry.

    4 packages · 4 occurrences

  • PROPOSED_NOT_ADMITTED additive local immutable OS custody review and private native composition, preserving V1 and mandatory runtime qualification.

    4 packages · 4 occurrences

  • Remove upward Builder type dependencies through neutral supplied-data projections.

    4 packages · 4 occurrences

  • Replace the removed props and pass the signed-in account id.

    4 packages · 4 occurrences

  • SecuritySettings renders the Change, Manage, and Update buttons only when onChangePassword, onManageEmail, onManageMfa, or onUpdatePhone are provided. Hosts that relied on always-visible (inert) buttons should pass the callbacks they actually support.

    4 packages · 4 occurrences

  • Set the same distinct 32+ character value as OSINT_GOVERNED_SUBJECT_BINDINGS_READ_TOKEN on the OSINT host and LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDINGS_READ_TOKEN on the identity host, plus the OSINT origin.

    4 packages · 4 occurrences

  • Single candidate-private profile-evidence writer (vault value under the candidate key plus fact revision in one erasure-guarded transaction), Railway vault wiring and a two-connection erasure lock conformance proof.

    4 packages · 4 occurrences

  • SSO and SCIM need sso_provider and the authos_sso_* / authos_scim_* tables.

    4 packages · 4 occurrences

  • The digest applies to new rows only. Existing osint_core.entities rows written by provider search whose canonical_key is <kind>:<url> with a withheld or personal URL keep that URL in clear, and a new ingestion of the same URL resolves to the digested key, so it does not match the old row or a suppression whose subject fingerprint is the old clear key.

    4 packages · 4 occurrences

  • The taxonomy store needs the osint_reference schema, tables, grants and the osint_reference_reader role created by 0035_osint_reference_taxonomy.sql.

    4 packages · 4 occurrences

  • Trusted devices, gated connect-with-LSSM, social provider readiness, gated phone/SMS second factor, and recent authentication for sensitive actions.

    4 packages · 4 occurrences

  • PersonalConsentConsumerV1Schema gains companyos_meeting_context. Parsing is unchanged for existing values; code that switches exhaustively over the consumer type or keys a closed label map by it must add the member.

    3 packages · 3 occurrences

  • Additive only; existing imports and behavior are unchanged. Hosts may implement the owner ports (AuthEmailAddressStore, WaitlistAdminStore, OperatorAuthRepository) and call the owner rules instead of keeping app-local copies.

    3 packages · 3 occurrences

  • Adds candidate_material_keys, candidate_material_vault.key_version, candidate_erasure_receipts, candidate_profile_erasure_guard() (runtime, worker), erase_candidate_profile_records(text,text,text,text,text) (runtime only), re-creates profile_fact_invalidation_pending_candidates behind the erasure fence and grants jsonb_object_length to runtime/worker.

    3 packages · 3 occurrences

  • Adds resolve_profile_fact_invalidation_quarantine(text,text,text,text,text,text) and profile_fact_invalidation_quarantine_entries(text), SECURITY DEFINER with a pinned search_path, executable by job_application_runtime and job_application_worker only; table grants are unchanged.

    3 packages · 3 occurrences

  • Apply 0038_osint_source_rights_operator_subject_refs.sql after 0037 with the migrator role; the runtime role must stay NOSUPERUSER NOBYPASSRLS.

    3 packages · 3 occurrences

  • AuthOS auth-audit, email-address, waitlist-admin, operator-auth and dev binding rules move to their AuthOS owners

    3 packages · 3 occurrences

  • Bind the ports before calling the port-backed lib.cli-runtime functions or the module.workspace DocBlock analysis forwards outside @lssm-tech/bundle.workspace. Hosts that import the bundle.workspace root entry or create a program through @lssm-tech/bundle.workspace/cli (createProgram, createCoreProgram or bindWorkspaceCliCommandPacks) are already bound.

    3 packages · 3 occurrences

  • Candidate profile-evidence erasure (erased tombstones, prior-revision redaction, per-candidate key crypto-erase, replay fence, value-free receipt) with store migration 0022, a fresh-MFA candidate operation and an AuthOS account-deletion path.

    3 packages · 3 occurrences

  • Candidate-private opportunity intake with sealed source provenance and append-only candidate availability observations, store migration 0023 and managed/API/MCP composition.

    3 packages · 3 occurrences

  • Canonical content-analysis declarations now live in their content domain owner with legacy forwarding compatibility.

    3 packages · 3 occurrences

  • Canonical CustomerSupport runtime contract ownership with compatible legacy forwards

    3 packages · 3 occurrences

  • Content analysis gains a durable claim/fence repository with a terminal-event outbox, an unsettled-reservation sweep, a SQL store and Gemini usage/billed-cost reporting.

    3 packages · 3 occurrences

  • Creates the append-only profile_fact_invalidations table with forced row-level security and scope policies; no existing table is rewritten.

    3 packages · 3 occurrences

  • Cross-product candidate subject binding with per-product consent (migration 0025) and destination-disclosure store and operations (migration 0026), with erasure removal and managed composition.

    3 packages · 3 occurrences

  • CV proposal plans and stages sealed as bounded, ordered vault parts with the evidence graph re-projected on read (D-182b); the largest synthetic CV at the 40 000-character limit proposes.

    3 packages · 3 occurrences

  • Existing quality imports remain supported; lower owners use the assurance quality entries directly.

    3 packages · 3 occurrences

  • generateStructured returns { output, usage?, billedCostMicros? }; pass pricing only to record an estimate.

    3 packages · 3 occurrences

  • Give execution and coordination declarations a canonical pure owner while retaining the execution runtime.

    3 packages · 3 occurrences

  • Historical execution-lanes imports remain supported; pure consumers may import the explicit orchestration-spec execution-lanes family.

    3 packages · 3 occurrences

  • job-application-store migrations/0032_candidate_profile_questions.sql (generated verbatim from candidateProfileQuestionsMigrationSqlV1, D-181/D-182a) adds the profile context columns to candidate_questions and candidate_question_answer_revisions, drops NOT NULL on their application columns, adds one exactly-one-context check per table and a profile index. Grants and RLS are unchanged.

    3 packages · 3 occurrences

  • lib.cli-runtime reaches the integration runtime and the TypeScript tool through runtime ports bound by bundle.workspace, deleting both lane-12b CLI bridges (10 edges)

    3 packages · 3 occurrences

  • Operator list/resolve of quarantined invalidation events with operator grants, fresh-MFA AuthOS assurance, store migration 0021 and grant-gated CLI/MCP surfaces.

    3 packages · 3 occurrences

  • Operator step once a PersonalOS host serves the consumer routes; until then leave both variables unset.

    3 packages · 3 occurrences

  • Organization custom roles as capability bundles over a declared catalog, with versioned grant rewrites and impact previews.

    3 packages · 3 occurrences

  • OSINT field classification fails closed; public job text is redacted, personal search results need personal_field, and runtime lease deletes stay in their own tenant

    3 packages · 3 occurrences

  • OSINT privacy keeps dates and references, withholds messaging URLs, gates personal embedding behind personal_field and ranks projection assertions over rows hidden by RLS

    3 packages · 3 occurrences

  • Own provider-neutral Durable Queue V2 definitions in orchestration-spec.

    3 packages · 3 occurrences

  • Personal, read-only, organization-bound AuthOS API keys with one-time reveal, expiry, rate limits, and live grant checks.

    3 packages · 3 occurrences

  • PersonalOS career goals, plan versions, search state and the per-product career.goal-plan@1 projection and server-only consumer.

    3 packages · 3 occurrences

  • PersonalOS companyos_meeting_context consent consumer, the consented CompanyOS meeting-context binding and adapters for every follow-up target

    3 packages · 3 occurrences

  • Preserve metadata-only delivery chain through canonical LSSM OS ownership

    3 packages · 3 occurrences

  • Preserve pure queue declarations through canonical orchestration ownership

    3 packages · 3 occurrences

  • Preserve quality contracts under the pure assurance owner and remove the execution-lanes compatibility backedge.

    3 packages · 3 occurrences

  • Profile-scoped candidate questions for CV ingestion (D-181), answer-driven re-run and re-seal of the CV stage plan, candidate-scoped confirmed-facts read for de-duplication and managed composition of the CV stages.

    3 packages · 3 occurrences

  • Projection rows and embeddings written before this release may hold an older public value of a field whose newer assertion is restricted.

    3 packages · 3 occurrences

  • Record no-longer-confirmed fact invalidations and refuse submit packets that bind an invalidated revision.

    3 packages · 3 occurrences

  • Replace the upsert repository with the claim/lease/fence port and schedule the relay and sweep.

    3 packages · 3 occurrences

  • Set the same distinct 32+ character value as OSINT_GOVERNED_SUBJECT_BINDING_REFS_WRITE_TOKEN on the OSINT host and LSSM_GOVERNED_ORGANIZATION_SUBJECT_BINDING_REFS_WRITE_TOKEN on the identity host, plus the OSINT origin; set OSINT_SOURCE_RIGHTS_EXPIRY_SWEEP_OWNER=worker on the api host when the worker owns the sweep.

    3 packages · 3 occurrences

  • Subject-scoped source-rights refs per organization binding, source-rights outbox operator resolve, worker expiry sweep and the D-160 subjectRef hand-back (osint-store 0038, EXCHANGE-01m).

    3 packages · 3 occurrences

  • The API key routes and authentication path need the authos_personal_api_keys table.

    3 packages · 3 occurrences

  • The candidate opportunity operations need the two tables created by 0023_candidate_opportunities.sql.

    3 packages · 3 occurrences

  • The question operations need the three tables created by 0027_candidate_questions.sql.

    3 packages · 3 occurrences

  • The role routes need managed_companyos_custom_roles and the custom_role_id grant column.

    3 packages · 3 occurrences

  • The subject binding, consent, disclosure tables and the erasure triggers are created by 0025_candidate_subject_bindings.sql and 0026_destination_disclosures.sql.

    3 packages · 3 occurrences

  • Typed asynchronous candidate questions with a required-unknown distinct from a refusal, sealed immutable answers, store migration 0027.

    3 packages · 3 occurrences

  • Without 0033 a runtime transaction holding base_read or base_curate can delete the shared-base tenant's ingestion lease and allow a concurrent duplicate run.

    3 packages · 3 occurrences

  • Accept month precision for undated-start CV profile answers.

    2 packages · 2 occurrences

  • Add scoped Career cockpit composition and fail-closed Taketide tracking and campaign guards.

    2 packages · 2 occurrences

  • Add the patio.company_offering.v1 governed company/offering projection contract and a pure public-only OSINT flattener.

    2 packages · 2 occurrences

  • Additive only; existing imports are unchanged. Hosts may call the new owner subpaths instead of reimplementing worker-local policy.

    2 packages · 2 occurrences

  • Adds durable invalidation cursors, the worker pending-candidates function, the runtime deletion scrub function and the documents UPDATE grant for the deletion scrub.

    2 packages · 2 occurrences

  • Agent guidance for Connect run modes in the consumer agent pack and generated AGENTS/USAGE guides.

    2 packages · 2 occurrences

  • Apply after 0120–0123. Runtime connections must use the NOSUPERUSER NOBYPASSRLS managed_companyos_app role and set app.tenant_id per transaction from the authenticated session.

    2 packages · 2 occurrences

  • Atomic profile fact correction and the value-free no-longer-confirmed notification.

    2 packages · 2 occurrences

  • AuthOS account-deletion governed-exchange consumer for candidate erasure and a destination-specific disclosure caller for submit (additive, not yet composed).

    2 packages · 2 occurrences

  • Canonical job application contracts with preserved compatibility forwarding

    2 packages · 2 occurrences

  • Canonicalize portable Connect and Harness evidence declarations.

    2 packages · 2 occurrences

  • Canonicalize the immutable artifact reference declaration.

    2 packages · 2 occurrences

  • Career brand, Fairelio and Hirly disposition rows in the LSSM OS and AuthOS governance catalogs; draft applications hidden on passport pages.

    2 packages · 2 occurrences

  • Choose selfserve-first or sales-assisted per wave; validate with validateOpportunityDiscoveryWave.

    2 packages · 2 occurrences

  • Configure each SupportOS origin as https://host[:port] (wss:// for the realtime origin), with no surrounding whitespace, path, query or fragment, and endpoint URLs without fragments.

    2 packages · 2 occurrences

  • Connect shell policy denies compound, normalized-git and wrapped forms of a denied command, and governs the Claude Code PowerShell tool.

    2 packages · 2 occurrences

  • Consumers that generate hooks from the contracts-spec pack pick up the PowerShell matcher after regeneration.

    2 packages · 2 occurrences

  • Content analysis re-authorizes replays, enforces duration and cost budgets, validates evidence against decomposed segments and resumes interrupted runs.

    2 packages · 2 occurrences

  • Creates the profile_facts table with forced row-level security and grants; no existing table is rewritten.

    2 packages · 2 occurrences

  • Deployments that relied on a malformed environment value or a dependency module outside the job-application-webhook-dependencies-* allowlist now fail at startup.

    2 packages · 2 occurrences

  • Durable Postgres agreement, mandate, collection, pilot-acceptance and termination stores with non-superuser RLS proof

    2 packages · 2 occurrences

  • Enforce profile fact lifecycle transitions and Sarla-normalized private employer exclusion.

    2 packages · 2 occurrences

  • Evaluate captured hypotheses with the versioned selfserve-first profile before canonical mature scoring.

    2 packages · 2 occurrences

  • Exact packet binding in the submit effect identity, typed non-effect submit result and live profile staleness

    2 packages · 2 occurrences

  • Expose the existing complete LSSM OS configuration declaration family through its canonical Spec owner.

    2 packages · 2 occurrences

  • Focused submits are refused before dispatch as input_refused until the managed runtime service receives a JobApplicationSubmitPacketSourceV1.

    2 packages · 2 occurrences

  • Host-exchanged CommunicationOS sessions carry the signed host issuer, so provider OAuth callbacks started from CompanyOS return to the CompanyOS origin configured in COMMUNICATION_OS_OAUTH_HOST_ORIGINS.

    2 packages · 2 occurrences

  • Hosts composing runContentAnalysisV1 must supply a budget port and an upsert repository.

    2 packages · 2 occurrences

  • Job-source observations classify personal fields (withheld) and fail closed to restricted; Greenhouse first_published maps to publishedAt

    2 packages · 2 occurrences

  • JobApplicationSubmitPacketSourceV1.listProfileFactInvalidations is now required so a missing invalidation read fails closed.

    2 packages · 2 occurrences

  • Key the map by the host-exchange issuer, not by the access-token issuer.

    2 packages · 2 occurrences

  • LSSM OS spec becomes a pure platform spec; the filesystem catalog locator moves to lssm-os-runtime and catalog validation takes an injected clock

    2 packages · 2 occurrences

  • Minor, behavioural tightening. Specs and persisted team state stay readable, but two flows that used to complete now fail closed: creating (or building from a plan pack) a code-producing run with verificationLane.required false is rejected, and a verifier approval decided by a task participant does not satisfy finalization. Worker add/remove on a run persisted before the upgrade re-validates its spec in amend mode, so an in-flight code-producing run without a verification lane can still change membership, and it still finalizes without a verifier. Task records persisted before the upgrade have no claimHistory, so their earlier, reclaimed claimants are recognized only through heartbeats that reported a task.

    2 packages · 2 occurrences

  • Move generic workspace parsing, rendering, diff, snapshot, impact, and DocBlock extraction into canonical CLI runtime leaves with compatible workspace forwards.

    2 packages · 2 occurrences

  • No API change. Tests or local-mode hosts that relied on the in-memory store refusing a second claim forever must now expect a takeover after 5 minutes.

    2 packages · 2 occurrences

  • Operator-auth store parity (stale-claim takeover) and one strict SupportOS origin validator

    2 packages · 2 occurrences

  • OSINT privacy scan normalizes to a fixpoint, detects phones on a separator-folded view, parses profile URLs with WHATWG URL and projections require that no cited evidence is non-public

    2 packages · 2 occurrences

  • OSINT rights lifecycle emission published through the governed source-rights publisher, the sourceRights.current read and the LSSM OS host source-rights mount.

    2 packages · 2 occurrences

  • OSINT source-rights outbox (osint-store migration 0036) with dispatch to the source product hosts, the production sourceRights issuance port and a separate read bearer for sourceRights.current.

    2 packages · 2 occurrences

  • OSINT worker domain behavior moves to osint-runtime and job-source-runtime

    2 packages · 2 occurrences

  • Own deterministic delivery policy contracts in LSSM OS Spec

    2 packages · 2 occurrences

  • Own neutral per-program inline AI bindings in cli-runtime.

    2 packages · 2 occurrences

  • Pass the fourth argument of validateLssmCanonicalCatalogV2(ecosystem, bindings, capsule, now) from a trusted clock (for example new Date() in a host); omitting it now returns ['catalog.clock_required'] instead of reading the ambient clock.

    2 packages · 2 occurrences

  • Preserve pure-spec public exports through canonical prebuild.

    2 packages · 2 occurrences

  • Regenerate the managed agent guidance so agents see the run-mode rules.

    2 packages · 2 occurrences

  • Register the production-disabled Taketide relying party and single-origin route, and add a presentation-only product session render partition with a fail-closed creator host session binding.

    2 packages · 2 occurrences

  • Reject unparseable expiration timestamps on job application authority decisions.

    2 packages · 2 occurrences

  • Replace @lssm-tech/lib.lssm-os-spec/context/catalog-locator-node (and its .browser subpath) with @lssm-tech/lib.lssm-os-runtime/catalog-locator-node; the function name, arguments, results and browser fallback are identical.

    2 packages · 2 occurrences

  • Resolve the canonical principal from a verified admitted pairwise product subject.

    2 packages · 2 occurrences

  • Rows of osint_projection.entities and embeddings written before this release may contain a public assertion that also cited personal evidence, or an older public value read in place of a newer non-public one.

    2 packages · 2 occurrences

  • Screen and export distribution-first opportunity drafts without fabricating mature evidence or customer economics.

    2 packages · 2 occurrences

  • Screen sales-assisted, creative-aware and channel-diverse opportunity drafts without weakening 1.0.0 waves or inventing customer economics.

    2 packages · 2 occurrences

  • Shared deterministic Today and habit construction with a thin PersonalOS web adapter

    2 packages · 2 occurrences

  • Shared subscription-store conformance subpath in billing runtime and Stripe test-mode subscription webhook and snapshot mapping in provider-payments (BILLING-01b).

    2 packages · 2 occurrences

  • Team tasks complete only with their declared evidence, and team runs finalize only with an independent verifier

    2 packages · 2 occurrences

  • Tellshift, Patio, GTM, Taketide and Sarla rows in the LSSM OS and AuthOS governance catalogs, with status-gated governed exchange bindings.

    2 packages · 2 occurrences

  • The source-rights heads and emissions tables are created by 0036_osint_source_rights_outbox.sql; the current read now needs its own bearer on the source product host.

    2 packages · 2 occurrences

  • Typed candidate profile facts with source-faithful lifecycle and value-state vocabulary

    2 packages · 2 occurrences

  • Verification links must be https and on the expected domain, and the managed webhook environment is validated before any client or module is created (E-01m)

    2 packages · 2 occurrences

  • Without a declaration, classification fails closed: only shared normalized job facts are public. Hosts that want a source's documented public raw keys to stay public pass the connector's declaration.

    2 packages · 2 occurrences

  • Worker invalidation consumer with durable cursors, stale disclosure snapshots, packet/application dependent enforcement and deletion coverage of profile facts.

    2 packages · 2 occurrences

  • @lssm-tech/module.founder-intelligence declares a module.forms dependency (WEB-01-INT0, D-103).

    1 package · 1 occurrence

  • Add candidate-private source context to revision-pinned CV profile question lists.

    1 package · 1 occurrence

  • Add organization-subject governed grant primitives with contract or legitimate-interest lawful bases and tenant-bound grants.

    1 package · 1 occurrence

  • Add the ecosystem data-ownership map catalog and validator to lssm-os-spec (D117-DATAMAP-01).

    1 package · 1 occurrence

  • Additive only; existing imports are unchanged. A host persisting a durable outbox may implement CommunicationOsOutboxPayloadCipher with its platform AES-GCM, bind communicationOsOutboxAdditionalData as additional data, and quarantine rows that fail to open.

    1 package · 1 occurrence

  • Additive only; existing imports are unchanged. Hosts may call the new subpath instead of keeping a host-local envelope literal or digest-binding helper.

    1 package · 1 occurrence

  • Additive. Hosts that relied on their framework's uncaught-error logging for Forms failures should pass reportUnexpectedError, because the handler now converts those failures into responses.

    1 package · 1 occurrence

  • Additive. Unbound hosts keep every new surface fail-closed.

    1 package · 1 occurrence

  • Align the existing founder product with the Tendframe name and canonical domains while preserving legacy identity and origin compatibility.

    1 package · 1 occurrence

  • AuthOS ecosystem origin routes declare required appPathPrefixes and expose pure app-path rule helpers.

    1 package · 1 occurrence

  • Board intake form untouched fields are unknown, never invalid (WEB-01-BOARD-HOST)

    1 package · 1 occurrence

  • Brand-neutral career FeatureModuleSpecs and operation classification map in the job-application runtime; no contract change.

    1 package · 1 occurrence

  • Brand-neutral job-application.opportunities FeatureModuleSpec; opportunity operations leave the internal list; no contract change.

    1 package · 1 occurrence

  • Connect hooks resolve the repository root from inside packages that carry their own turbo.json

    1 package · 1 occurrence

  • Consumer-pack Claude Code hooks use the Claude blocking protocol, cover PowerShell, emit one line of catalog context, and scope the catalog memory rule.

    1 package · 1 occurrence

  • Customer support runtime subpaths share module instances, restoring 4 facade re-exports

    1 package · 1 occurrence

  • CV ingestion stages (chronology with source spans and confidence, typed candidate question drafts through the existing question owner, de-duplication against confirmed facts, candidate-private evidence-graph read model, qualification-gated OCR and fact-extraction ports).

    1 package · 1 occurrence

  • Forms HTTP handler maps typed Forms errors (unknown public token returns 404 form_not_found, not 500)

    1 package · 1 occurrence

  • Grep RICH_REF_CHROME_RESTORED instead of the retired TODO(rich-ref migration) anchor.

    1 package · 1 occurrence

  • Headless adaptive candidate profile interview with four registered commands, refusal memory and explicit adoption into the candidate-private profile (additive; store and hosts not composed yet).

    1 package · 1 occurrence

  • Include built Agentpack artifacts required by existing published exports.

    1 package · 1 occurrence

  • Interview clients and hosts must send expectedRevision and the 2.0.0 contract fingerprint.

    1 package · 1 occurrence

  • Keep explicit legacy origins until the new domains and registered callback are operational.

    1 package · 1 occurrence

  • Non-breaking. Only code that assumed every catalog relying party is production-disabled is affected; no runtime in this repository does.

    1 package · 1 occurrence

  • Normalize workspace library-definition paths consistently across host platforms

    1 package · 1 occurrence

  • OSINT privacy decodes the complete HTML5 entity table, lists unsafe keys by index, matches profile hosts on any TLD and keeps URL reference numbers

    1 package · 1 occurrence

  • OSINT privacy keeps ordinary ATS labels with spaces and punctuation while key triggers still withhold the whole field

    1 package · 1 occurrence

  • OSINT privacy never emits an unsafe key in any output structure and matches profile host families on any host label

    1 package · 1 occurrence

  • PersonalOS command envelope construction and digest binding move to personal-os-runtime

    1 package · 1 occurrence

  • Preserve provider contracts through cohesive private implementation units

    1 package · 1 occurrence

  • Product notification preference centers and producers on CommunicationOS, plus Pactena and PersonalOS channel composition

    1 package · 1 occurrence

  • Protect candidate CV question responses from HTTP caching and preserve declared safe refusal codes.

    1 package · 1 occurrence

  • Resolve canonical capability references and preserve blocked export maps.

    1 package · 1 occurrence

  • Retain stable LSSM package binding IDs at current domain owner locators

    1 package · 1 occurrence

  • Revised-event invalidation contract and the submit packet disclosure snapshot guard seam; revised-event consumption awaits a store migration.

    1 package · 1 occurrence

  • Route objects without appPathPrefixes fail AuthOsEcosystemOriginRouteSchema and the TypeScript type.

    1 package · 1 occurrence

  • Run the AuthOS spec tests and typecheck, then the catalog consumer tests.

    1 package · 1 occurrence

  • Run the notification, Pactena and PersonalOS composition tests.

    1 package · 1 occurrence

  • Security fix: commands previously ran for any caller holding a non-empty key. Local and demo setups that run the deterministic command bindings must opt in explicitly; production keeps them denied until lib.auth-os verifies keys.

    1 package · 1 occurrence

  • SeedMapV1 contract, checker, SQL inventory parser and a reviewed-pending Tafio seed map in lssm-os-spec.

    1 package · 1 occurrence

  • Select installed adoption inventories by release and source priority.

    1 package · 1 occurrence

  • Serialize overlapping filesystem adapter glob traversals under Bun on Windows.

    1 package · 1 occurrence

  • Shared check-in, recovery and weekly-review construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared coach adaptation command construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared export and deletion rights request construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared goal-scoped support grant, report, revoke and block construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared household, mission and goal foundation construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared outcome observation command construction for PersonalOS web, desktop and mobile hosts

    1 package · 1 occurrence

  • Shared scope-bound outbox payload sealing primitives; CommunicationOS mobile seals its outbox

    1 package · 1 occurrence

  • Stable planning-handoff public maps and preserved browser output

    1 package · 1 occurrence

  • The adoption catalog loader reads the catalog package's own catalog.json from the workspace.

    1 package · 1 occurrence

  • The AuthOS ecosystem catalog marks the CompanyOS relying party production-enabled under its recorded security review, keeps it invite-only and refuses production entries without review evidence

    1 package · 1 occurrence

  • The CodeBlock codemod chrome marker points at the codemods package migration guide.

    1 package · 1 occurrence

  • The four profile-interview commands move to contract 2.0.0 and declare the integer expectedRevision that command authority requires, as a compare-and-set on the interview session revision.

    1 package · 1 occurrence

  • The Managed CompanyOS MCP server no longer grants admin to any API key and denies commands outside opt-in reference mode.

    1 package · 1 occurrence

  • The new SessionStart hook needs a ContractSpec CLI that supports can-help catalog status --host; an older CLI rejects the option and Claude Code reports a non-blocking hook error. An older CLI also answers adoption hooks in a Connect-disabled workspace with a fail-closed prompt, so install the matching CLI before regenerating.

    1 package · 1 occurrence

  • Unbound consent drafts so PersonalOS mobile reuses the canonical consent constructor

    1 package · 1 occurrence

  • Unbound Today/habit drafts so desktop and mobile reuse the canonical PersonalOS constructor

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/agentpack.contractspec

    Layer: tools · 1 change

  • @lssm-tech/app.cli-contractspec

    Layer: apps · 2 changes

  • @lssm-tech/app.communicationos-api

    Layer: apps · 2 changes

  • @lssm-tech/app.communicationos-mcp

    Layer: apps · 2 changes

  • @lssm-tech/app.managed-companyos-mcp

    Layer: apps · 2 changes

  • @lssm-tech/app.supportos-api

    Layer: apps · 2 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 2 changes

  • @lssm-tech/bundle.library

    Layer: bundles · 1 change

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 1 change

  • @lssm-tech/bundle.marketing

    Layer: bundles · 1 change

  • @lssm-tech/bundle.marketing-operations

    Layer: bundles · 2 changes

  • @lssm-tech/bundle.personal-os

    Layer: bundles · 1 change

  • @lssm-tech/bundle.workspace

    Layer: bundles · 1 change

  • @lssm-tech/integration.authos-better-auth

    Layer: integrations · 1 change

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

    Layer: integrations · 2 changes

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

    Layer: integrations · 2 changes

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

    Layer: integrations · 1 change

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

    Layer: integrations · 2 changes

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

    Layer: integrations · 2 changes

  • @lssm-tech/integration.communication-os-host-auth

    Layer: integrations · 2 changes

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

    Layer: integrations · 3 changes

  • @lssm-tech/integration.customer-support-postgres

    Layer: integrations · 2 changes

  • @lssm-tech/integration.governed-data-postgres

    Layer: integrations · 3 changes

  • @lssm-tech/integration.growth-persistence

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-browser

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-effects-dependencies-railway

    Layer: integrations · 1 change

  • @lssm-tech/integration.job-application-effects-focused

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-email

    Layer: integrations · 2 changes

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

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-store

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-application-transport

    Layer: integrations · 1 change

  • @lssm-tech/integration.job-application-webhook-resend-managed

    Layer: integrations · 2 changes

  • @lssm-tech/integration.job-sources

    Layer: integrations · 2 changes

  • @lssm-tech/integration.media-processing-local

    Layer: integrations · 2 changes

  • @lssm-tech/integration.opa-meeting-context-bridge

    Layer: integrations · 3 changes

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

    Layer: integrations · 1 change

  • @lssm-tech/integration.osint-store

    Layer: integrations · 1 change

  • @lssm-tech/integration.osint-transport

    Layer: integrations · 2 changes

  • @lssm-tech/integration.personal-os-state-postgres

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-calendar

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-customer-support

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-email

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-gemini

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-linkedin

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-llm

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-payments

    Layer: integrations · 1 change

  • @lssm-tech/integration.provider-project-management

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-reddit

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-tiktok

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-voice

    Layer: integrations · 2 changes

  • @lssm-tech/integration.provider-x

    Layer: integrations · 2 changes

  • @lssm-tech/integration.runtime

    Layer: integrations · 3 changes

  • @lssm-tech/integration.social-tracking-runtime

    Layer: integrations · 1 change

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

    Layer: libs · 1 change

  • @lssm-tech/lib.ai-providers

    Layer: libs · 2 changes

  • @lssm-tech/lib.assurance-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.authos-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.authos-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.billing-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.builder-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.builder-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.bus

    Layer: libs · 1 change

  • @lssm-tech/lib.cli-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.communication-runtime

    Layer: libs · 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.content-analysis-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.content-analysis-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.content-gen

    Layer: libs · 2 changes

  • @lssm-tech/lib.contracts-integrations

    Layer: libs · 3 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.contracts-spec-core

    Layer: libs · 1 change

  • @lssm-tech/lib.creator-operations-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.creator-operations-spec

    Layer: libs · 4 changes

  • @lssm-tech/lib.crypto-utils

    Layer: libs · 1 change

  • @lssm-tech/lib.customer-support-conformance

    Layer: libs · 2 changes

  • @lssm-tech/lib.customer-support-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.customer-support-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.data-exchange-core

    Layer: libs · 3 changes

  • @lssm-tech/lib.decision-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.execution-lanes

    Layer: libs · 2 changes

  • @lssm-tech/lib.finance-ops-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.finance-os-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.job-application-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.job-source-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.lifecycle

    Layer: libs · 1 change

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

    Layer: libs · 1 change

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

    Layer: libs · 1 change

  • @lssm-tech/lib.mobile-control

    Layer: libs · 1 change

  • @lssm-tech/lib.notification

    Layer: libs · 3 changes

  • @lssm-tech/lib.opportunity-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.opportunity-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.orchestration-spec

    Layer: libs · 1 change

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

    Layer: libs · 2 changes

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

    Layer: libs · 2 changes

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

    Layer: libs · 2 changes

  • @lssm-tech/lib.osint-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.osint-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.personal-finance-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.personal-finance-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.personal-health-runtime

    Layer: libs · 2 changes

  • @lssm-tech/lib.personal-health-spec

    Layer: libs · 2 changes

  • @lssm-tech/lib.personal-os-runtime

    Layer: libs · 1 change

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

    Layer: libs · 1 change

  • @lssm-tech/lib.provider-runtime

    Layer: libs · 1 change

  • @lssm-tech/lib.provider-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.talent-spec

    Layer: libs · 4 changes

  • @lssm-tech/lib.utils-typescript

    Layer: libs · 1 change

  • @lssm-tech/module.auth-os

    Layer: modules · 2 changes

  • @lssm-tech/module.communication-os

    Layer: modules · 2 changes

  • @lssm-tech/module.community-intelligence

    Layer: modules · 2 changes

  • @lssm-tech/module.content-generation

    Layer: modules · 2 changes

  • @lssm-tech/module.customer-support

    Layer: modules · 2 changes

  • @lssm-tech/module.examples

    Layer: modules · 1 change

  • @lssm-tech/module.forms

    Layer: modules · 1 change

  • @lssm-tech/module.founder-intelligence

    Layer: modules · 1 change

  • @lssm-tech/module.lssm-os-control-plane

    Layer: modules · 1 change

  • @lssm-tech/module.osint

    Layer: modules · 2 changes

  • @lssm-tech/module.personal-experience

    Layer: modules · 5 changes

  • @lssm-tech/module.personal-life-admin

    Layer: modules · 5 changes

  • @lssm-tech/module.workspace

    Layer: modules · 1 change

  • @lssm-tech/tools.contractspec-codemods

    Layer: tools · 2 changes

  • contractspec

    Layer: tools · 2 changes

  • spec-driven-development

    Layer: libs · 2 changes