# Fracta

> Swarm intelligence engine: parallel agents explore, a graph captures, deterministic strategies execute.

## Docs

- [Adding a New Runtime to Fracta](https://fracta.quasarops.com/docs/contributing/adding-runtime.md): How to onboard a new LLM CLI as a fracta host runtime
- [Contributing](https://fracta.quasarops.com/docs/contributing/overview.md): How to work on fracta itself
- [Building from source](https://fracta.quasarops.com/docs/development/building.md): Local builds, Makefile targets, and version stamping for the Go binary and Python sidecar.
- [CI and tests](https://fracta.quasarops.com/docs/development/ci-and-tests.md): GitHub Actions CI pipeline for fracta — what runs, why it runs, and how to reproduce failures locally.
- [Development](https://fracta.quasarops.com/docs/development/overview.md): Building, testing, and releasing fracta from source.
- [Releasing](https://fracta.quasarops.com/docs/development/releasing.md): Cutting tagged releases — multi-arch binaries, Docker images, GitHub Release notes.
- [Getting Started with Fracta](https://fracta.quasarops.com/docs/getting-started/core-concepts.md): Core concepts, how credentials flow, and which deployment mode to pick.
- [Your First Agent](https://fracta.quasarops.com/docs/getting-started/first-agent.md): Spawn, peek, and clean up a fracta agent in about 5 minutes.
- [Installation](https://fracta.quasarops.com/docs/getting-started/installation.md): Prerequisites and how to install fracta
- [Credential Pipeline](https://fracta.quasarops.com/docs/guides/authentication/credential-pipeline.md): Canonical reference for fracta auth — how credentials are resolved and bound for agents and tools.
- [MCP Server Authentication](https://fracta.quasarops.com/docs/guides/authentication/mcp-server-auth.md): Authenticated remote MCP servers via the mcp_servers.*.remote.auth block in fracta.yaml.
- [Runtime Configuration Guide](https://fracta.quasarops.com/docs/guides/authentication/runtime-configuration.md): Configuring claude, codex, and opencode runtimes — auth wiring for local and K8s deployments.
- [Quickstart, Docker Compose Mode](https://fracta.quasarops.com/docs/guides/deployment/docker-compose.md): Run the full fracta stack in containers — control plane, gateway, strategy runner, Postgres, FalkorDB.
- [Quickstart, Kubernetes Mode](https://fracta.quasarops.com/docs/guides/deployment/kubernetes.md): Deploy fracta to a Kubernetes cluster — control plane and gateway as Deployments, agents as Jobs.
- [Local K8s Mode](https://fracta.quasarops.com/docs/guides/deployment/kubernetes-runbook.md): Operations reference — run fracta against kind (recommended), Docker Desktop, minikube, or k3d for development and testing.
- [Quickstart, Local Process Mode](https://fracta.quasarops.com/docs/guides/deployment/local-process.md): Everything runs on your machine — control plane daemon, gateway, agents as local processes, SQLite for state.
- [Deployment Modes](https://fracta.quasarops.com/docs/guides/deployment/overview.md): Three deployment modes — local-process, docker-compose, kubernetes — sharing the same thin-client architecture.
- [Gateway Tool Policy](https://fracta.quasarops.com/docs/guides/gateway-tool-policy.md): Restrict which MCP tools agents can see and call. Per-server allow_only / deny lists, configuration in fracta.yaml, and how to verify enforcement with fracta debug.
- [MCP Catalog Workflow](https://fracta.quasarops.com/docs/guides/mcp-catalog.md): Operator narrative for the MCP server catalog — when to use which verb, what gets committed, and org-private catalogs.
- [MCP Server Examples](https://fracta.quasarops.com/docs/guides/mcp-server-examples.md): Worked configs for OAuth-protected, env-token, and SSE-transport MCP backends — the patterns the scaffolded gateway used to ship inline.
- [Architecture](https://fracta.quasarops.com/docs/introduction/architecture.md): Four cooperating processes, plus one git worktree per active agent.
- [Glossary](https://fracta.quasarops.com/docs/introduction/glossary.md): Terms you'll encounter in the fracta docs
- [Licensing](https://fracta.quasarops.com/docs/introduction/licensing.md): Source-available under FSL-1.1-ALv2 — free for internal use, modification, and most real-world scenarios. Converts to Apache-2.0 two years after each release.
- [What is Fracta?](https://fracta.quasarops.com/docs/introduction/what-is-fracta.md): Swarm intelligence orchestration for AI agents — turning open-ended exploration into reproducible, high-performance automation.
- [Troubleshooting](https://fracta.quasarops.com/docs/operations/troubleshooting.md): Common issues across all deployment modes
- [[Pattern Name]](https://fracta.quasarops.com/docs/patterns/_template.md): [One sentence: what this pattern is + who it's for, written as a noun phrase ending in a benefit. Example: 'Notion + Readwise + a knowledge-garden ontology that turns annotated reading into a queryable atomic-note graph.']
- [Fracta Patterns](https://fracta.quasarops.com/docs/patterns/overview.md): Opinionated end-to-end stacks — MCP servers, ontology slice, strategies — for the most common ways people use fracta.
- [Extending](https://fracta.quasarops.com/docs/patterns/reading-garden/extending.md): The seams — adding sources (Raindrop, Zotero, PDFs), publishing to public gardens (Mintlify, Quartz), and growing the ontology — without forking the pattern.
- [First Run](https://fracta.quasarops.com/docs/patterns/reading-garden/first-run.md): End-to-end scripted run — register the MCP stack, spawn a Claude worker with one pipeline prompt, and publish your first Concept page to Notion.
- [Ontology](https://fracta.quasarops.com/docs/patterns/reading-garden/ontology.md): The eight node types — Topic, Highlight, Document, Concept, Entity, Claim, Question, Publication — and the edges that wire your reading into a queryable graph.
- [Reading Garden](https://fracta.quasarops.com/docs/patterns/reading-garden/overview.md): Six months of Kindle highlights, automatically connected and published to Notion — using Readwise + a knowledge-garden ontology + three strategies.
- [Setup](https://fracta.quasarops.com/docs/patterns/reading-garden/setup.md): Wire Notion and Readwise to the fracta gateway via native OAuth, stand up the concept extractors, provision the three Notion databases, and verify the stack — about 20 minutes.
- [Strategies](https://fracta.quasarops.com/docs/patterns/reading-garden/strategies.md): The bundled strategies — highlight_distill, cross_source_concepts, notion_publish — that turn captured highlights into idempotent Notion concept pages.
- [fracta auth](https://fracta.quasarops.com/docs/reference/cli/auth.md): Auth credential pipeline commands
- [fracta config mcp](https://fracta.quasarops.com/docs/reference/cli/config-mcp.md): Entry point for MCP catalog management and per-mode server wiring.
- [fracta controlplane](https://fracta.quasarops.com/docs/reference/cli/controlplane.md): Start, stop, or check status of the local fracta control plane daemon.
- [fracta debug](https://fracta.quasarops.com/docs/reference/cli/debug.md): Diagnostic commands for inspecting a running fracta deployment — gateway policy snapshots and the runtime registry.
- [fracta graph](https://fracta.quasarops.com/docs/reference/cli/graph.md): Knowledge graph management commands
- [fracta host-mcp](https://fracta.quasarops.com/docs/reference/cli/host-mcp.md): Start an MCP server on stdio that exposes lifecycle tools through the ControlPlaneClient abstraction.
- [fracta init](https://fracta.quasarops.com/docs/reference/cli/init.md): Materialize a deployment scaffold (local, docker-compose, or k8s) into the current directory.
- [fracta kill](https://fracta.quasarops.com/docs/reference/cli/kill.md): Kill an agent, removing its worktree and state
- [fracta list](https://fracta.quasarops.com/docs/reference/cli/list.md): List all agents
- [`fracta mcp` (deprecated alias)](https://fracta.quasarops.com/docs/reference/cli/mcp.md): One-release deprecation alias for the relocated MCP commands.
- [fracta merge](https://fracta.quasarops.com/docs/reference/cli/merge.md): Merge an agent's feature branch into the current branch (non-destructive)
- [CLI Overview](https://fracta.quasarops.com/docs/reference/cli/overview.md): Every fracta command at a glance
- [fracta peek](https://fracta.quasarops.com/docs/reference/cli/peek.md): Peek at an agent's log output
- [fracta registry](https://fracta.quasarops.com/docs/reference/cli/registry.md): Manage the MCP server registry
- [fracta say](https://fracta.quasarops.com/docs/reference/cli/say.md): Send a follow-up message to an agent, resuming its session
- [fracta serve](https://fracta.quasarops.com/docs/reference/cli/serve.md): Start fracta as an MCP server
- [fracta spawn](https://fracta.quasarops.com/docs/reference/cli/spawn.md): Spawn a new agent with a dedicated worktree
- [fracta watch](https://fracta.quasarops.com/docs/reference/cli/watch.md): Connect to the control plane and stream live events for the given agent.
- [fracta worker](https://fracta.quasarops.com/docs/reference/cli/worker.md): Runs one or more worker loops that pull missions from the configured queue and execute them using the host registry.
- [fracta.yaml](https://fracta.quasarops.com/docs/reference/configuration/fracta-yaml.md): Schema for the project-root fracta.yaml — connections, auth, agents, runtimes, MCP servers.
- [Logging](https://fracta.quasarops.com/docs/reference/configuration/logging.md): Structured logging configuration and component registry
- [MCP Servers Catalog](https://fracta.quasarops.com/docs/reference/configuration/mcp-servers-catalog.md): The bundled catalog of pre-configured MCP server definitions in mcp-servers/ and the schema of each server.yaml.
- [Ontology Schema Configuration](https://fracta.quasarops.com/docs/reference/configuration/ontology.md): Configure which graph schema families the gateway loads at startup via the ontology.schemas URI block.
- [Event Bus](https://fracta.quasarops.com/docs/reference/events.md): Internal event buses, sinks, and lifecycle events
- [Strategy Bindings](https://fracta.quasarops.com/docs/strategies/bindings.md): The binding.yaml schema and fetch modes
- [cross-source-concepts](https://fracta.quasarops.com/docs/strategies/catalogue/knowledge-garden/correlation/cross_source_concepts.md): Score Concepts by recency × frequency × source diversity × mean per-mention extraction_score
- [highlight-distill](https://fracta.quasarops.com/docs/strategies/catalogue/knowledge-garden/enrichment/highlight_distill.md): Distill Readwise highlights into Highlight, Document, Concept, and Entity nodes
- [Strategy Contracts](https://fracta.quasarops.com/docs/strategies/contracts.md): The contract.yaml schema and parameters
- [Strategy Lifecycle](https://fracta.quasarops.com/docs/strategies/lifecycle.md): How strategies get found, deployed, updated, and graduated from exploratory work to validated production assets.
- [Strategy Developer Guide](https://fracta.quasarops.com/docs/strategies/overview.md): Reusable Python DAG pipelines run inside a sidecar process — DuckDB is the engine.
- [Portability](https://fracta.quasarops.com/docs/strategies/portability.md): Strategies are two things glued together at runtime — a publishable artifact and an environment-specific binding.
- [Quick Start](https://fracta.quasarops.com/docs/strategies/quickstart.md): Build a minimal strategy end-to-end — contract.yaml, strategy.py, and binding.yaml.
- [Response Adapters](https://fracta.quasarops.com/docs/strategies/response-adapters.md): Parsing non-standard tool responses
- [Control Plane](https://fracta.quasarops.com/docs/swarm/control-plane.md): The orchestrator behind the swarm — spawns, supervises, and reaps agents over HTTP and MCP.
- [Coordination](https://fracta.quasarops.com/docs/swarm/coordination.md): Three lightweight mechanisms — mailbox, declared intent, non-disruptive peeks — that keep isolated agents aligned.
- [Swarm Overview](https://fracta.quasarops.com/docs/swarm/overview.md): The exploration stage of fracta's three-stage arc — parallel AI agents in isolated workspaces with a shared mailbox.
- [Spawning Agents](https://fracta.quasarops.com/docs/swarm/spawning-agents.md): How agents are launched, what shapes their behavior, and the lifecycle states they pass through.
- [Workspaces](https://fracta.quasarops.com/docs/swarm/workspaces.md): Per-agent workspaces — git worktrees, directory workspaces, and what each deployment mode supports.

## OpenAPI Specs

- [openapi](https://fracta.quasarops.com/docs/api-reference/openapi.json)