Cat-Factory
Home
  • Introduction
  • Core Concepts
  • Quick Start
  • Designing Your Board
  • Shared Services
  • Requirements
  • Running Pipelines
  • Recurring Pipelines
  • Pull Requests & Merging
  • Repositories
  • Issue & Document Sources
  • Budgets & Spend
  • Prompt Fragments
  • Deploy to Cloudflare
  • Deploy to Node.js
  • Configuration
  • Self-Hosted Runner Pools
  • Ephemeral Environments
  • Architecture
  • Integration Manifests
  • Packages & Repository Layout
GitHub
Home
  • Introduction
  • Core Concepts
  • Quick Start
  • Designing Your Board
  • Shared Services
  • Requirements
  • Running Pipelines
  • Recurring Pipelines
  • Pull Requests & Merging
  • Repositories
  • Issue & Document Sources
  • Budgets & Spend
  • Prompt Fragments
  • Deploy to Cloudflare
  • Deploy to Node.js
  • Configuration
  • Self-Hosted Runner Pools
  • Ephemeral Environments
  • Architecture
  • Integration Manifests
  • Packages & Repository Layout
GitHub
  • Reference

    • Architecture
    • Integration Manifests
    • Packages & Repository Layout

Packages & Repository Layout

Cat-Factory is a TypeScript monorepo. This page maps the published packages and the source tree, so you know where to look when extending or debugging the platform.

Published libraries

PackageResponsibility
@cat-factory/appNuxt SPA layer - board UI and Pinia stores.
@cat-factory/kernelDomain types, constants, repository ports, the pipeline registry (registerPipeline).
@cat-factory/orchestrationService composition root and workflow engines.
@cat-factory/agentsAgent catalog, prompt composition, model-provider facade, the agent-kind registry (registerAgentKind) and web-research/cache policy.
@cat-factory/serverRuntime-neutral HTTP controllers, the shared agent-execution machinery (composite/container executors, runner-job client, GitHub App auth), and the web-search proxy.
@cat-factory/integrationsGitHub, document/task sources, ticket trackers, environments, runner pools.
@cat-factory/contractsWire formats, validated with Valibot.

Extending a deployment

The model-provider, agent-kind, and pipeline registries are opt-in extension seams. A deployment (e.g. a proprietary org package) can mix in providers, agent kinds, and predefined pipelines without forking. See Architecture → Extending a deployment.

Where to get help in the source repo

TopicLocation
Backend / monorepo overviewbackend/README.md
Frontend SPAfrontend/app/README.md
End-to-end runtime flowCLAUDE.md
Authenticationbackend/docs/auth.md
GitHub operationsbackend/docs/github-operations.md
Runner poolsbackend/docs/runner-pool-integration.md

The platform is MIT licensed. Source, issues, and contribution guidelines live at kibertoad/cat-factory.

Edit this page on GitHub
Last Updated: 6/20/26, 7:25 PM
Prev
Integration Manifests