Skip to content

Repo Overview

This repo is a multi-app platform workspace. This page is the shortest map of which app owns what, how the apps relate, and where shared contracts live.

  • apps/auth: Better Auth service, workforce SSO registration, web session issuance, and web sign-in policy.
  • apps/web: Nuxt app for the main user-facing workspace and sign-in UX.
  • apps/cms-customer: Payload customer operator surface, native CMS users, internal admin workflows, and read-only Better Auth web-user mirrors.
  • apps/cms-leverage: Payload Leverage-owned operator surface for internal product/ops workflows.
  • apps/api: Mastra runtime, chat APIs, connector orchestration, and retrieval logic.
  • apps/meltano: ELT and ingestion runtime for connector sync jobs.
  • apps/support-dev: this internal developer support site.
  • @repo/auth: shared Better Auth helpers for web auth.
  • @repo/contracts: shared public transport contracts across app boundaries.
  • @repo/cms-customer-contracts: internal CMS-facing transport contracts.
  • @repo/domain: shared domain types and connector runtime profiles.
  • @repo/env: shared environment access helpers.
  1. A web user signs in through web.
  2. auth issues and validates the Better Auth web session.
  3. cms-customer and cms-leverage operators sign in separately through native Payload auth.
  4. cms-customer receives read-only Better Auth web-user and access-request mirrors for operator lookup/review.
  5. api validates Better Auth for Mastra-backed web runtime operations.
  6. Connector sync and retrieval flows move through api, meltano, MongoDB, Qdrant, and provider APIs depending on the connector mode.
File What it helps you answer
README.md Root-level repo conventions and entrypoint commands
DESIGN.md Canonical authenticated web workspace design guidance
apps/auth/README.md Auth app-local run and support-site entrypoint
apps/web/README.md Web app-local run and support-site entrypoint
apps/cms-customer/README.md CMS app-local run and support-site entrypoint
apps/api/README.md API app-local run and support-site entrypoint
packages/domain/src/connectors/connectorRegistry.ts Shared connector definitions used across apps
apps/support-dev/src/content/docs/dependencies/overview.md Dependency map for frameworks, runtime services, stores, queues
apps/support-dev/src/content/docs/features/overview.mdx Short feature map for implemented, partial, and planned areas
apps/support-dev/src/content/docs/features/chat-orchestration.md Orientation to canonical chat orchestration requirements
apps/support-dev/src/content/docs/platform/chat-models-and-evals.md Short chat model role, policy, and eval lane map
docs/features/chat/spec.md Canonical chat eval coverage, thresholds, and release policy
docs/features/connectors/spec.md Canonical connector lifecycle, mode, recovery, and rollout rules
docs/features/ingestion/spec.md Canonical indexed-sync, embedding, and pipeline runtime rules
docs/features/governance/spec.md Canonical connector policy, registry, and secret-boundary rules
docs/features/realtime/spec.md Canonical authenticated realtime transport and event rules
apps/support-dev/src/content/docs/platform/chat-evals-and-regression-testing.mdx Operator workflow for chat eval triage and release-gate review
  • Use the support-dev site for current setup and architecture orientation, then follow the linked canonical feature docs for durable requirements and release policy.