Release summaries
authos-better-auth-schema-check-identity
The canonical-email adapter wrapper keeps the adapter's identity so Better Auth's schema self-check can find it.
integrator
withCanonicalEmailDatabaseLookup returns the adapter object the database factory built, with findOne replaced as an own property, instead of a Proxy. Better Auth's schema self-check, keyed by adapter identity, is therefore registered for compositions that only add canonical-email lookups. Once it is registered, Better Auth awaits it before handling auth requests and logs a mismatch at startup.
maintainer
withSsoSecretEncryption still wraps the adapter in a Proxy, so compositions with the sso plugin (such as the CompanyOS API) keep the schema check disabled until that wrapper also preserves the adapter's identity.
authos-better-auth-server-entry
authos-better-auth adds an explicit server-only ./server entry; the root barrel stays compatible
integrator
Server hosts may import
@lssm-tech/integration.authos-better-auth/server; browser and native code imports./clientor./native-session-client. Existing root imports keep working.authos-idp-oauth-provider-1-7-schema
Better Auth 1.7.5 OAuth-provider schema (migration 0176) and back-channel origin handling for the central LSSM IdP
maintainer
Apply tracked migration 0176 before promoting an lssm-identity-api build on Better Auth 1.7.5. Without it, /api/auth/jwks and /api/auth/oauth2/authorize answer 500 on the production database.
authos-oauth-second-factor
AuthOS: OAuth/social sign-ins of TOTP-enrolled identities are challenged for the second factor unless the device is trusted, and the CompanyOS client registration ceremony on the central IdP uses central-only env names.
integrator
Hosts that enable the
two-factorbridge plugin now challenge OAuth sign-ins too. Set the new optionaltwoFactorChallengePagebridge config to the page that renders the pending MFA challenge; it receives the original destination as?callback=. Without it, the callback URL is reused withtwoFactorRedirect=trueand no session.maintainer
To register
companyos-webon id.lssm.co, setLSSM_IDP_COMPANYOS_RP_ENABLED,LSSM_IDP_COMPANYOS_RP_SECURITY_REVIEW_REF,LSSM_IDP_COMPANYOS_RP_CLIENT_SECRETandLSSM_IDP_RP_RECONCILE_TOKENon the identity API (neverLSSM_RP_*), redeploy, reconcile, then remove them.customer
If you turned on an authenticator app, signing in with LSSM, Google, Microsoft, LinkedIn or GitHub now asks for your code too, unless you trusted this browser.
authos-product-admission-adapters
Brand-neutral verified-identity and reviewed-membership product admission adapters with monolith wiring.
integrator
New server-only subpaths under ./product-admission/*; no existing export or behavior changes. Hosts supply binding rows {productApplicationId, relyingPartyId, mode, accessTier} and inject session, operator and revocation ports.
authos-shared-oidc-subject-binding-20261102
Bind strict relying-party profile and account subjects to the verified ID token.
maintainer
Strict OIDC fallback cannot replace the verified subject or share claim state across callbacks.
authos-sso-adapter-schema-check
The SSO client-secret adapter wrapper forwards Better Auth's schema self-check, so compositions with the sso plugin detect schema drift.
integrator
withSsoSecretEncryption registers each wrapper with the schema check of the adapter it wraps, so $context.checkSchema is defined when the sso plugin is enabled (it was undefined before). Encryption of SSO OIDC client secrets at rest is unchanged, and the wrapped adapter is not modified. Behaviour tightening: Better Auth awaits the check before every auth request, and a schema mismatch fails the request with SchemaMismatchError.
maintainer
The package declares @better-auth/core 1.7.5 (already a peer of its Better Auth plugin dependencies) as a direct dependency for registerSchemaCheck and schemaCheckFor. Keep it pinned to the better-auth version.
builder-existing-control-plane-build
Build existing Builder control-plane leaves and preserve export manifests
integrator
Existing advertised control-plane leaves produce their canonical build outputs without rewriting the explicit manifest.
canonical-control-plane-operations
Preserve ControlPlane operation identity through canonical Builder declarations
integrator
Historical execution approval, rejection and trace imports forward to the same canonical Builder declarations.
cmp-auth-and-product-schema-rehearsals
Better Auth schema check helpers and local schema rehearsal scripts for CompanyOS, hCircle and Pactena
integrator
runBetterAuthSchemaCheck(await auth.$context)reports whether the composed instance still has its schema check (unregisteredmeans an adapter wrapper dropped it) and returns mismatch findings as data.findBetterAuthStoreSchemaProblems(options, tables)compares the tables the plugins write with introspected tables given in the adapter's logical names. Both are read-only.maintainer
Three operator scripts rehearse schema work on loopback test databases: the CompanyOS Better Auth check per production profile, the hCircle meeting host provisioning and migrations, and the Pactena 0007-0010 apply at boot. Evidence and the provisioning steps are in docs/evidence/authos/better-auth-schema-rehearsal-2026-10-27.md and docs/evidence/opa/rehearsals/.
cmp-fix-lssm-runtime-portable-declarations
Preserve portable claimed queue envelope and fixture declarations
integrator
Queue envelope declarations retain their canonical inferred types and runtime behavior.
cmp-meeting-intake-sync-and-titles
Meeting intake gets calendar push channels and delta sync, retires meetings whose event moved or was cancelled, names materialized meetings, and exposes its readiness to operators
customer
Once the operator turns them on, meetings OPA creates from your calendar show the event title in your private recent meetings (filterable by title or note), a meeting whose event moved or was cancelled no longer lingers there unless you wrote in it, and calendar changes reach OPA within minutes instead of at the next poll.
integrator
@lssm-tech/integration.provider-calendaradds push channels and delta sync:./impls/calendar-sync(calendarPushChannelToken, constant-timeverifyCalendarPushChannelToken,CalendarSyncSession,CalendarDeltaResult), Googleevents.watchchannels, header parsing andsyncTokensync (./impls/google-calendar-push,./impls/google-calendar-delta,createGoogleCalendarSyncSessionWithTokens), and Microsoft Graph subscriptions, validation handshake, notification parsing andcalendarView/delta(./impls/microsoft-graph-push,./impls/microsoft-graph-delta,createMicrosoftCalendarSyncSession). The Graph transport now admits/subscriptionsandcalendarView/deltapaths.OpaPrivateMeetingRecentItemSchema(opa.meeting_workspace.recent) gains an optional plain-texttitle(1-200 characters); the schema stays strict, so a client built before this change rejects a response that carries a title.maintainer
The CompanyOS API owns migrations 0185-0189 (B242): 0185 calendar push channels and encrypted delta cursors, 0186 encrypted intake titles and retirements, 0187 the append-only bot repair audit (B164), 0188 the live-capture retention index, discovery function and capture-runtime deletes (B175), and 0189 the OPA service price table (seeded unpriced) and usage records (B170). The API host mounts the guarded readiness route GET /api/opa/meeting-intake/readiness (key names only), POST /api/webhooks/calendar-push/google and /microsoft, and the cron GET /api/cron/meeting-intake-push-channels, which vercel.json and the deploy/lssm-ecosystem CompanyOS API profile schedule every 30 minutes.
control-plane-skills-owner
Canonical owners for messaging policy and signed control-plane skill contracts
integrator
Import skill schemas from lssm-os-spec, signing and verification from lssm-os-runtime/control-plane/skills, and messaging policy from builder-spec.
current-growth-model-form-owner
Own complete marketing model and FormSpec families in Growth.
maintainer
Preserve full marketing types, canonical FormSpec identity and compatibility paths.
current-growth-operation-owner
Canonicalize complete marketing operations and remove the Growth Legacy return.
maintainer
Preserve operation objects, schemas, policies and compatibility exports.
cving-01a-host
The job-application API and MCP hosts inject CV original custody over the existing candidate S3 configuration with a distinct CV prefix, failing closed when it is absent.
maintainer
The API and MCP from-environment compositions build cvOriginalCustody with createRailwayCvOriginalCustodyV1 over JOB_APPLICATION_S3_* and the new JOB_APPLICATION_CV_S3_PREFIX (default candidate-cv-originals/, must not overlap the document, inbox or export prefixes) and pass cvImageTranscriptionEnabled false, only together with profileEvidenceKey. A missing bucket or incomplete endpoint, region or credential set composes no custody and the CV ingestion operations stay JOB_APPLICATION_OPERATION_UNSUPPORTED; invalid present values fail at startup with a code and no value. The worker host composes no profileEvidenceKey and does not run CV operations, so it is unchanged.
integrator
Both apps depend on @lssm-tech/integration.job-application-effects-dependencies-railway, which exposes the ./cv-original-custody subpath. Set JOB_APPLICATION_CV_S3_PREFIX per deployment if the default prefix is not wanted.
fo2-s04-knowledge-live-stack
Live evidence ingestion and grounded answers run on Supabase Storage, pgvector in the evidence database and the Vercel AI Gateway; no S3 vendor account, Qdrant or embedding/OCR vendor key is needed
integrator
New adapters: supabaseStorageS3ClientConfig with S3ObjectWriter conditionalWrite head-verify for Supabase Storage, GatewayEmbeddingProvider for Vercel AI Gateway embeddings, SupabaseVectorProvider extensionSchema, and createCompanyIntelligenceEvidenceVectorStore for tenant-isolated pgvector evidence. Knowledge evidence vector requests carry an additional tenantId field; vector stores without tenancy ignore it, tenant-isolated stores require it.
maintainer
The CompanyOS API document evidence composition now defaults to pgvector (migration 0180, managed_companyos_ci_evidence_vectors, vector(1536) in the extensions schema, RLS on app.tenant_id) unless COMPANY_INTELLIGENCE_QDRANT_URL is set; Gateway embedding and OCR routes use AI_GATEWAY_API_KEY or VERCEL_OIDC_TOKEN; COMPANY_INTELLIGENCE_EMBEDDING_API_KEY is required only for direct openai/mistral routes. Health capabilities gain an ocr entry. Composition never throws while the API module loads: invalid Gateway inferenceProviders, a malformed Supabase region or https URL, an OCR model outside the EU Gateway catalog and a provider constructor refusal are all reported by name as configuration_required. health.get reports the vector dependency unavailable when pgvector is selected and the 0180 table is absent. docs/operations/founder-ops-v2/knowledge-stack.md lists the bucket, route and variable names an operator must set.
fo2-s06-meeting-evidence-briefings
Account-scoped Granola/calendar meeting evidence, private meeting preparation, durable briefing occurrences and approval-gated follow-through
integrator
Granola reads are exact-identity, bounded and fail with redacted typed codes; hosts persist evidence through
MeetingEvidenceStorePortand read explicit freshness.@lssm-tech/bundle.managed-companyos/meeting-intelligence-founder-opsexposes DailyBriefModel, MeetingPreparationPack, MEETING_PREPARATION_RECIPE and services whose ports bind to the existing occurrence claim store, grounded knowledge, Work and CommunicationOS delivery owners.fo2-s06-meetings-live-readiness
Notetaker bot live-readiness (readiness names and a disabled state, cron gating, reauthorization alerts, dead-letter recovery through migration 0195); production stays off.
maintainer
AttendeeCaptureError gains the
unauthorizedcode for HTTP 401 (other 4xx stayrejected); exhaustive switches over the code union must handle it. resolveCompanyBotReadiness keeps its signature and output fields; its verdict union gainsdisabled(OPA_BOTS_ENABLED is not 1), the BOTS_DISABLED blocker code is retired, and the new codes are ENV_INVALID (with the key name) and CAPTURE_STORAGE_REGION_NOT_EU. OPA_CAPTURE_STORAGE_REGION is now a required readiness key.integrator
Nothing changes while OPA_BOTS_ENABLED is unset. To go live follow section 4 of docs/operations/founder-ops-v2/meetings-enable.md: Attendee DPA and EU evidence, migrations 0165 and 0195, the dispatcher login and the OPA_BOTS_* values. No route exposes the readiness verdict, so check the key names against the deployment's environment listing first; after the switch is set, any gap makes both bot crons answer 503 and log opa-bots.configuration_required with blocker codes and key names. Rollback is unsetting OPA_BOTS_ENABLED.
fo2-s08-founder-coding-improvement
Agent fleet adds durable coding-agent supervision, proactive proposals, governed workflow improvement and use-case proposals for founder operations
integrator
@lssm-tech/module.agent-fleet/coreexports SupervisedCodingSessionService, ProactiveProposalService, WorkflowImprovementService with createWorkflowImprovementAdapter, reviewUseCaseProposals and the shared FounderProposalV1 contract. Hosts bind durable stores, provider control (Agent Host, Runtime Node, Claude Code or Codex adapters), notification, authority, quiet-hours and Work-creation ports. Workflow improvement uses GovernedAiImprovementRuntimeV2, so failed evaluations are rejected and production promotion needs a human approval.growth-marketing-tail-ownership
Move marketing validation, forms and sample handlers to canonical Growth owners
integrator
Legacy marketing paths preserve fixture objects, form schemas and deterministic handler behavior through Growth packages.
hook-authority-runtime-owner
Canonical Hook Authority runtime ownership with preserved private packaging and compatibility
integrator
Use lssm-os-runtime/control-plane/hook-authority and the digest, validation and reference-adapter leaves.
job-application-fact-revised-consumer-2
Store migration 0019, key-dispatched invalidation recording with the sibling rule, and revised-event consumption in the managed-runtime consumer and worker.
integrator
JobApplicationProfileFactInvalidationEventV1 gains an optional key (no-longer-confirmed when omitted, or job-application.profile.fact.revised; any other key is refused with JOB_APPLICATION_PROFILE_FACT_INVALIDATION_EVENT_INVALID) and JobApplicationProfileFactInvalidationResultV1 gains siblings. The invalidation consumer now records streamed revised events instead of ignoring them, so exact packet submits refuse on dependents invalidated by any material fact revision, not only a withdrawal.
customer
Apply job-application-store migration 0019 after 0018 before running a worker of this release with JOB_APPLICATION_PROFILE_FACT_INVALIDATION_ENABLED; without it recording a revised invalidation fails the reason check and that candidate's drain stops at the event. Then run the store conformance.
maintainer
A withdrawn confirmed fact appends revised then no-longer-confirmed with one receipt and the same dependents; the first event stored in sequence order keeps its reason (normally revised), the other is a sibling and writes nothing. Real-Postgres conformance of 0019 has not been run.
job-application-inbox-subject-sealed
Inbox message subjects are sealed under the per-candidate data key behind an opaque subject_ref (store migration 0029 drops the plaintext column); the managed Resend webhook requires the deployment material key.
integrator
PostgresJobApplicationInboxStoreV1(client, scope, objects, keys, now) takes a candidate data-key strategy (inboxSubjectKeysV1; the legacy key form is refused with APPLICATION_INBOX_SUBJECT_KEY_STRATEGY_INVALID); readApplicationInboxV1 message rows carry subject_ref (sealed reference, null for legacy rows, or deleted) and no subject; openInboxSubjectV1 opens a reference of its own scope; store() can now refuse with JOB_APPLICATION_CANDIDATE_ERASED and refuses a different subject for the same provider message as APPLICATION_INBOX_MESSAGE_COLLISION; the candidate-key PostgresCandidateMaterialVaultV1 handles inbox-subject references; createManagedApplicationResendWebhookCompositionV1 requires materialKey.
customer
Apply store migration 0029 before deploying a runtime or webhook built from this release, and give the webhook service JOB_APPLICATION_MATERIAL_KEY_BASE64 (the same deployment material key the effects dependencies use); without it the webhook refuses to start (JOB_APPLICATION_MATERIAL_KEY_REQUIRED or JOB_APPLICATION_MATERIAL_KEY_INVALID). Existing plaintext subjects are dropped by 0029 (fresh schema under D-088/D-112b); those rows keep a null subject_ref.
maintainer
The webhook role now holds the deployment material key and route-scoped SELECT/INSERT on candidate_material_keys and inbox-subject vault rows (key_version > 0), never UPDATE/DELETE; the vault policy does not verify that a reference's scope fingerprint matches its row scope (the store computes it). No unkeyed subject digest is stored.
job-application-invalidation-quarantine
Store migration 0020, bounded retry and quarantine of permanently invalid invalidation events, typed worker signals and a fail-closed submit gate until operator resolution.
integrator
ManagedJobApplicationProfileFactInvalidationOutcomeV1 gains a quarantined variant (sourceEventId, eventKey, typed reason, attempts, replayed); the consumer and ProfileFactInvalidationRunnerV1 accept maxPermanentAttempts (1..100, default 3); ProfileFactInvalidationRunResultV1 gains optional quarantined signals and the host loop an onQuarantine callback. listProfileFactInvalidations (and so every exact packet binding and disclosure read) now throws APPLICATION_PACKET_INVALIDATION_QUARANTINED while the candidate has an unresolved quarantine entry; submit refuses before any reservation and the pre-dispatch recheck reports capacity_requeued. consume() of a streamed event is unchanged.
customer
Apply job-application-store migration 0020 after 0019 before running this release; without it every exact packet submit fails closed because the unresolved-quarantine read is missing. Watch for JOB_APPLICATION_PROFILE_FACT_INVALIDATION_QUARANTINED signals and resolve each entry with PostgresJobApplicationProfileFactInvalidationQuarantineStoreV1.resolve (dependents_reviewed or not_applicable, opaque operator and evidence refs) to reopen that candidate's submits.
maintainer
Only typed recording refusals are permanent; database, connection, lock, timeout and unknown errors are transient and never quarantine. Attempt rows are counted per candidate scope, consumer and event and survive restarts; a replay of a quarantined event counts nothing. Quarantine rows are value-free and retained through candidate deletion like cursors. Real-Postgres conformance of 0020 has not been run.
job-application-profile-interview-store
Candidate-private profile interview store (migration 0024), atomic fact correction with value and brand-configured managed composition.
maintainer
PostgresJobApplicationProfileInterviewStoreV1 implements the runtime interview store port; the managed operation handler passes interview deps as the ninth handler argument only when profileEvidenceKey and profileInterview (consentRevision, model, optional emit) are both set, otherwise the job-application.profile.interview.* operations stay JOB_APPLICATION_OPERATION_UNSUPPORTED. The API and MCP environment factories accept an optional brand argument with profileInterview; no consent text, prompt or model default ships in the shared owners (D-117). Deploy store migration 0024 before the runtime.
job-application-verification-effect-ledger
Fenced verification effect ledger (migration 0028) with in-doubt reconciliation and lease-gated challenge claims (E-01n)
integrator
Apply migration 0028 before deploying; pass claimDigest from reserve() to complete, handoff and release; verification replay now completes instead of handing off, an effect that may have been dispatched is handed off as ambiguous, and missing or blank work claims are refused with APPLICATION_EFFECT_CLAIM_REQUIRED.
job-application-verification-effect-reconcile
Lease-checked verification transitions and audited operator reconcile of in-doubt verification effects (migration 0030, E-01p)
integrator
Apply migration 0030 after 0029; pass the full work claim (workItemId, leaseOwner, fencingToken) with claimDigest to complete, handoff and release; compose the operator reconcile port as the runtime role and bind the operator_verification_read/reconcile grants in AuthOS.
meeting-recorder-provider-normalization
Normalized transcript segments, per-provider webhook verification and bounded retries for meeting recorder providers
integrator
Read transcript timing from startMs/endMs (or startTimeMs/endTimeMs) and speakers from the speaker object, not from startTime. Verify webhooks with verifyMeetingRecorderWebhook and reject providers whose meetingRecorderCapabilities entry says webhook 'unsupported' (Granola, tl;dv). A verified event names one record to re-fetch; payload content is never trusted.
maintainer
withRecorderRetry wraps the transport for all four HTTP providers. Fathom and Fireflies verifyWebhook fail closed without a secret. Fathom SDK list pages are read from result.items.
microsoft-calendar-reauthorization
Personal Microsoft calendar requests least-privilege Graph scopes and surfaces, alerts and restores lapsed grants like Google
customer
When Microsoft stops accepting CompanyOS access to your Outlook calendar (password change, expired sign-in, revoked consent), you get one email and a "Reconnect Microsoft" banner on every OPA page; one click reconnects. CompanyOS now only asks Microsoft for read access to your calendars.
integrator
MicrosoftCalendarOAuthClient requires Calendars.Read (Calendars.ReadWrite is no longer allowed in the config) and throws MicrosoftOAuthError with sanitized codes, AADSTS numbers and Retry-After. Personal Microsoft reads declare CALENDAR_REAUTHORIZATION_REQUIRED (409); a new health query reports the stored connection state without contacting Microsoft.
maintainer
The shared transition/outbox/relay used for Google now carries providerKind; Microsoft transitions run in a fresh transaction after the failed read rolls back. invalid_client is logged as microsoft_calendar_connection.client_rejected and never flips owners.
ts-01-comments
Audience comment grants, observations, cursor and redaction lineage under FORCE RLS (TS-01-COMMENTS).
integrator
Run SqlMarketingAudienceCommentStore.migrate() on the owner client before applyGrowthRowLevelSecurity, then mount the store on createScopedGrowthSqlClient. Compose MarketingAudienceCommentService with a real authority, a targets port that resolves the actor's current connection and owned object and returns SOCIAL_COMMENT_SCOPES for requiredScopes, a credentials port, a lineage port answered by the content, publication and results owners, and a provider reader (the integrations comment readers are structurally compatible). Call redact after a publication, content or result deletion. Mapping a comment to an account or contact, reply holds and results recording are not part of this release.
maintainer
Donor lineage: tellshift-monorepo@eefc58b packages/libs/contracts/comments.ts, packages/modules/workspace/comments{,-collect,-ports}.ts and migrations 0094-0096 (reference only). Actor privacy is enforced by the store and service; FORCE RLS binds tenant, workspace and brand. Evidence is PGlite-only under a NOSUPERUSER owner with fixture readers (D-094).
ts-01-deps
Tellshift Studio subpath exports, browser-layer dependencies and verbatim typecheck split; provider-x static twitter-text import (TS-01-DEPS).
maintainer
Import the studio through ./engine, ./react, ./hosts-public or ./hosts-public/runtime; the embed entry stays free of the engine. A host rendering ./react must import src/react/index.css and provide Tailwind 4. The verbatim folders and the two public-host files that import them are typechecked by tsconfig.verbatim.json until parity.
ts-01-edcore
Editorial core v2 with native content kinds, field-addressed claims, policy-fingerprinted review and consented scheduling.
integrator
Editorial records, content and operation IO are v2 (operations 2.0.0). Hosts must supply an EditorialPolicyEvaluator (or accept the refusal-by-default double that refuses submit, review approval, scheduling and publication), and the due runner needs EditorialStore.listDueScopes.
maintainer
growth-persistence replaces EDITORIAL_DDL with EDITORIAL_V2_DDL (editorial_record and editorial_record_history). This is a reset: v1 editorial rows are neither read nor migrated.
ts-01-edcore-fu
Editorial record v2 documentation and repository script follow-up; no package behavior change.
maintainer
Package READMEs describe editorial record v2 (editorial_record tables, operations 2.0.0, required policy evaluator, admission bridge). The preview, packed-consumer, Hirly compiler and GitHub qualification scripts build schemaVersion 2 records; the packed lifecycle also checks a policy-change review refusal.
ts-01-edgov
Editorial governance with exact-revision assigned review, authorized export with receipts, clipboard confirmation and self-reported feedback.
integrator
Compose EditorialAssignmentService, EditorialExportService and EditorialFeedbackService with real stores, an EditorialReviewerPolicy and EditorialReviewRules, then call registerEditorialGovernanceOperations next to registerEditorialOperations. Pass assignments.gate(authority) as the editorial authority so approval honors an open assignment. Use createProductionEditorialPolicyEvaluator over the knowledge stores and authority instead of a fixture policy; there is no permissive default.
maintainer
growth-persistence adds three fully scoped marketing_execution tables through SqlEditorialAssignmentStore, SqlEditorialExportStore and SqlEditorialFeedbackStore. They are registered as editorial-assignments, editorial-export-receipts and editorial-feedback after evidence-sources, with package exports and the marketing barrel.
integrator
Breaking (D-088, donor parity): evaluateEditorialPolicy now returns EDITORIAL_POLICY_CHANGED instead of EDITORIAL_NEEDS_EVIDENCE when the evaluator refuses after a fingerprint was bound, so a profile, source or brief change after submit refuses review, schedule and the due runner with POLICY_CHANGED (409) and the invalidation code is EDITORIAL_POLICY_CHANGED; a refusal at submit stays NEEDS_EVIDENCE. The review error catalog declares ASSIGNED_REVIEW_REQUIRED, ASSIGNED_REVIEW_STALE, ASSIGNED_REVIEW_BLOCKED, ASSIGNED_REVIEWER_UNAVAILABLE and SELF_REVIEW_FORBIDDEN (403). Clients that branched on NEEDS_EVIDENCE for post-submit changes must handle POLICY_CHANGED.
customer
EditorialReviewActions now shows the assigned review panel while in review and the export action once approved. Ready is labelled as a reviewer signal, copying as not publication, and feedback as self-reported.
ts-01-gen
Durable fenced marketing copy runs over a strict task generator, with Tellshift generation configuration and wiring.
integrator
Hosts compose MarketingCopyRunService with a MarketingCopyGeneratorPort, a usage-reservation port, a draft port and the copy run store, then mount registerMarketingCopyRuns. Start, retry and resume are cost-bearing and need an operation approval receipt over an exact quote; a run never confirms, approves or publishes. The existing growth.marketing.copy.generate operation is unchanged.
maintainer
growth-persistence adds SqlMarketingCopyRunStore with two fully scoped marketing_execution tables (copy_runs, copy_run_attempts) under FORCE RLS; its store-registry step and package exports are added by the integration owner. bundle.tellshift-studio server/generation needs the content-gen and provider-llm dependencies and a ./server subpath.
ts-01-int0-shared
Marketing content kinds, the growth store migration registry and pre-declared Tellshift dependencies.
maintainer
lib.growth-spec exports ./marketing/content-kind (8 content kinds, 11 brief formats; legacy linkedin/x values refused). integration.growth-persistence exports ./store-registry with 20 ordered idempotent migration steps run by migrateAllGrowthStores. provider-x and app.marketing-operations pre-declare dependencies used by later Tellshift slices.
ts-01-know
Marketing knowledge convergence with revisioned evidence, scoped search, intake candidates, confirmed brand revisions and campaign briefs.
integrator
MarketingBrandRevision and MarketingBrief are schemaVersion 2. Brand revisions carry draft|confirmed status and company-brief fields; briefs are revisioned campaign context that pin a confirmed brand revision. Copy generation refuses unconfirmed brands and the retired linkedin/x formats. Hosts must supply a real MarketingKnowledgeAuthority; there is no permissive default.
maintainer
growth-persistence adds six fully scoped marketing_execution tables through SqlMarketingEvidenceSourceStore, SqlMarketingEvidenceCandidateStore, SqlMarketingBrandStore and SqlMarketingBriefStore. Their store-registry steps are added by the integration owner.
ts-01-results
Results with provenance and publication binding, reviewed CSV import, learning decisions with autoApply false and draft next-cycle revisions.
integrator
Hosts compose MarketingResultService and MarketingLearningService with a real MarketingResultsAuthority, the CSV adapter (parseResultsCsv) and a learning context (briefLearningContext over the brief store plus the campaign revision reader), then call registerMarketingResults. There is no permissive default. Decisions are never applied: operators submit the draft through the owning brief or campaign revise command.
maintainer
growth-persistence adds SqlMarketingResultStore and SqlMarketingLearningStore with four fully scoped marketing_execution tables under FORCE RLS. Their store-registry steps are added by the integration owner. normalizeAdvertisingObservation takes a seventh connectionRef argument.
ts-01-soc
Owner-only member-approved LinkedIn, X and Instagram scheduling and publish-now on module.social-media (TS-01-SOC).
integrator
Compose scheduling with createMarketingSocialScheduling and supply an account binding port (AuthOS connection projection with CAS), per-kind qualification, a content reader, policy and the SqlSocialPublisherStore. Owners submit acknowledgements, an exact kind and the reviewed bindingHash per target; the runtime mints one member approval per target. Adapters receive publicationKind, actorId, connectionId and connectionVersion and should be given currentConnectionVersion. Run workers through createMarketingSocialScopedWorker with discoverGrowthDueScopes and scope-bound runtimes.
maintainer
Ported from tellshift-monorepo@eefc58b (public-scheduling contract, workspace public-scheduling and public-scheduling-run, linkedin/x/x-thread/instagram publishing blockers, scheduled LinkedIn provider, public worker and the public-scheduling, linkedin-publishing, x-publishing, x-thread and instagram-publishing test cases). Breaking: the grant union, schedule record schema 2, the extended SocialScheduleStore port (count, peers, forAccount) and operation versions 2.0.0. Fixture-only evidence.