Skip to content

Paseka documentation

Docs are grouped by immersion depth. Feature specs under specs/ are not published on the site; see Specs index.

New here?

Follow the shortest path from the model to a running colony:

  1. Principles — understand choreography and Flight Trail identity.
  2. Colony layout — initialize project and machine-local config.
  3. Bee config and prompt templates — configure roles.
  4. CLI first-time setup — start NATS, run diagnostics, and dispatch work.

Idea & principles

Document Description
Principles Choreography model, contracts, honey, HITL, colony vs machine
Glossary Bee-language vocabulary and domain terms
Brief (RU) Historic product brief (concept, EDA, stack, HITL)
Self-improving colonies Idea note: what a colony could learn from its own trails, and the line between platform capabilities and the methodology that uses them

Using Paseka

Document Description
Start here — Colony layout .paseka/ vs machine-local config, slug, local NATS, paseka init
Bee config Bee role YAML schema, adapters, routing fields
Prompt templates .paseka/prompts/, text/template, partials
CLI Queen Shell (paseka) command reference and troubleshooting
Interactive sessions HITL bee chat, SessionAdapter, Ghostty
Queen Console Local web UI operator tour, reviews, sessions, system and Git
Forage Cues Named ingress shortcuts (.paseka/cues/); optional Standing Trail identity; CLI, Console, Telegram; timers/webhooks call cue run
Telegram gateway Setup and run paseka gate telegram
Nuc packs Export/import portable bee + prompt packs
Homelab deployment Server/apiary container, Queen Console, reuse NATS
Pull-request delivery Isolated trails as origin PRs (defaults.delivery, forge script, reconcile)

Reference

Document Description
Bee routing subscribes / publishes, Reactor, task vs direct dispatch
Event contracts SIGNAL, INSIGHT, MUTATION, VERIFICATION kinds and authoring rules
Insight kinds INSIGHT taxonomy and {{.Insights}} projection
Task ledger traceId → taskId → agentId, task lifecycle
Adapter launch resolution Bee → OS process: config layers, params, command, env

Architecture

Document Description
Overview Adapters, run IPC, worktrees, package layout
Queen Console design system UI contract for the Svelte console: themes, component inventory, status colors, hard rules
Hive Runtime map Interactive Archify diagram (generated in docs CI)

Plans

Document Description
Changelog Shipped features with links to specs and canonical docs
Specs index Short map of docs/specs/ (bodies stay in the repo only)
Backlog Deferred work and implementation assumptions
UI migration backlog Deferred Console redesign decisions: dead links, unbuilt transitions, placeheld sections

Russian index: README-RU.md.

Agent index: llms.txt (full corpus: llms-full.txt, generated by scripts/gen-llms-full.sh).

Contributors and coding agents: AGENTS.md.