# BWOC Framework & Handbook > BWOC (Buddhist Way of Coding) is a backend-neutral framework for incarnating and orchestrating AI coding agents, driven by a single CLI (`bwoc`). It defines a three-phase lifecycle arc (uppāda/birth · ṭhiti/live · vaya/retire), a strict one-folder-one-agent layout cloned from a canonical template, a plain-Markdown agent identity file (`AGENTS.md`) with `{{camelCase}}` placeholders that work across any LLM backend (Claude, Codex, Kimi, Ollama, or any OpenAI-compatible endpoint via `bwoc-harness`), persistent memory capped at 200 lines, and multi-agent coordination through named Saṅgha teams with shared task lists. The framework is implemented in Rust (`bwoc-cli`, `bwoc-agent`, `bwoc-core`, `bwoc-harness` crates) and documented bilingually in English (canonical) and Thai (parity). Software version 2.24.0, latest release v2026.6.6-0; always re-read VERSION.md for current values. The handbook summarises; the canonical source of truth for all facts is the public repo https://github.com/bemindlabs/BWOC-Framework — on any conflict the repo wins. ## Handbook (by role) [BWOC Handbook — English entry point](README.md): Role-indexed entry point for all readers. Contains a five-sentence description of BWOC, the three-phase lifecycle table, cross-handbook conventions (handbook vs repo, bilingualism, versioning), and fast-path shell commands. Links every role handbook and the glossary. [BWOC Handbook — Thai entry point](README.th.md): Thai-language parity of README.md. Identical structure; Thai is the secondary language, English is canonical on conflicts. Useful for Thai-speaking users and for verifying bilingual parity. [End-User Handbook — English](end-user/HANDBOOK.en.md): Practical guide for people who run agents without touching framework code. Covers install (Rust 1.85+), workspace init, four ways to drive an agent (chat/run/spawn/send), inbox/log/memory/health commands, team and task list management, agent lifecycle commands (new/stop/start/retire), fleet overview (dashboard/sessions/fleet/peer), document scaffolding (notes/retro/research), updating, and a troubleshooting table. [End-User Handbook — Thai](end-user/HANDBOOK.th.md): Thai-language parity of the end-user handbook. Same structure and command examples in Thai prose. [Why BWOC / Philosophy — English](philosophy/HANDBOOK.en.md): The design-rationale chapter. Why BWOC exists, its four pillars (one-repo-one-agent, backend-neutral AGENTS.md, ≤200-line memory, multi-agent trust), where DDD/SOLID/Clean Architecture are thin (state impermanence, failure tracing, lifecycle, trust, default safety, scope discipline), the full 22-Buddhist-framework→engineering mapping table, the five governing principles, the uppāda·ṭhiti·vaya arc, who should/should not adopt it, and tradeoffs. States clearly: Pali = engineering labels, not religious instruction. [Why BWOC / Philosophy — Thai](philosophy/HANDBOOK.th.md): Thai-language parity of the philosophy chapter. [Self-Improvement — English](self-improvement/HANDBOOK.en.md): How a BWOC agent learns, reflects, and improves. Capability declaration + skill maturity L1–L7; the Three Roots of Wisdom learning loop (study/reflection/practice) with the memory artifact each writes; the Wisdom Loop; the curation pipeline (personal Tier-1 → pattern → cross-agent Tier-2 → fleet convention); memory tiers and every `bwoc memory` command; the work engine & effort discipline; the growth lifecycle (grow→mature→mentor→release); metrics, anti-patterns, and learning triggers. [Self-Improvement — Thai](self-improvement/HANDBOOK.th.md): Thai-language parity of the self-improvement chapter. [Developer Handbook — English](developer/HANDBOOK.en.md): For people building on or contributing to the Rust framework. Covers the two scopes (framework root vs agent template), the nine-crate map, build/test/install, dependency-quarantine, the hard rules (two-tier docs, backend neutrality, bilingual parity, auto-version hook, implementation logs, conventional commits, protected-main PR gates, over-engineering protection), skill/plugin development, the contribution flow, releasing, and how to publish this handbook as a GitHub Pages site. [Developer Handbook — Thai](developer/HANDBOOK.th.md): Thai-language parity of the developer handbook. [Plugin Authoring — English](plugin-craft/HANDBOOK.en.md): Building BWOC plugins — skill-vs-plugin, the nine plugin kinds, manifest.toml, the bwoc plugin lifecycle, normative output schemas, and the operator-confirm gate on write verbs. [Plugin Authoring — Thai](plugin-craft/HANDBOOK.th.md): Thai-language parity of the plugin-authoring chapter. [Agent Author & Operator Handbook — English](agents/HANDBOOK.en.md): For people who incarnate, configure, tune, and operate agents. Covers the one-folder-one-agent layout, the AGENTS.md backend-neutral rule vs Obsidian slot files, the full config.manifest.json field schema, slots (persona/mindsets/skills/interconnect/memories) and maturity levels, `bwoc new` with its full flag table, every `bwoc check` failure mode, trust & ed25519 signing, lifecycle (stop/start/retire), teams, and common authoring mistakes. [Agent Author & Operator Handbook — Thai](agents/HANDBOOK.th.md): Thai-language parity of the agents handbook. [Persona/Mindsets/Skills Handbook — English](slots/HANDBOOK.en.md): How to write an agent's slot content — persona (WHO: identity, role, core principles), mindsets (HOW: named decision frames, frontmatter `principle/` tag, When/How-to-Apply), and skills (WHAT: bounded verifiable capabilities, `domain/` tag + `maturity: L1..L7`). Explains the Obsidian slot format (frontmatter + wikilinks + callouts) vs the plain AGENTS.md rule, the Thai-body/English-tags/emoji convention, seeding with `bwoc new --mindsets/--skills`, and `bwoc check`. [Persona/Mindsets/Skills Handbook — Thai](slots/HANDBOOK.th.md): Thai-language parity of the persona/mindsets/skills handbook. [Backends Handbook — English](backends/HANDBOOK.en.md): How to drive and configure an agent through each backend CLI after `bwoc init` and incarnation. Covers the AGENTS.md + symlink mechanism (CLAUDE/AGY/CODEX/KIMI/COPILOT/OLLAMA/OPENAI → AGENTS.md), vendor agentic CLIs (Claude Code, Antigravity `agy`, Codex, Kimi, GitHub Copilot) vs harness backends (Ollama, OpenAI-compatible needing `baseUrl`), launch via `bwoc spawn/chat/run` with `--backend`, configuring by natural-language prompt, persisting config in config.manifest.json + `bwoc check`, and adding a backend with one symlink. [Backends Handbook — Thai](backends/HANDBOOK.th.md): Thai-language parity of the backends handbook. [Crawler / Indexer Handbook — English](crawler/HANDBOOK.en.md): For web crawlers and documentation indexers. Defines the index-vs-skip scope, bilingual canonical/parity (hreflang) handling, freshness signals (VERSION.md fields + auto-version hook), and polite-crawl guidance. Pairs with robots.txt and sitemap.md. [Crawler / Indexer Handbook — Thai](crawler/HANDBOOK.th.md): Thai-language parity of the crawler handbook. [Ecosystem / Projects Handbook — English](ecosystem/HANDBOOK.en.md): Maps every BWOC and related `bwoc-*` project — the core framework, bwoc-chat (egui desktop chat), bwoc-devices (device monorepo + ESP32 firmware), bwoc-devices-app / BWOC Monitor (Tauri macOS dashboard), bwoc-llm-pm / LLM Provider Monitor (macOS menu-bar), bwoc-mcc (SwiftUI menu-bar control center), and this handbook — with each project's stack and how it connects to the `bwoc` CLI and shared protocols. [Ecosystem / Projects Handbook — Thai](ecosystem/HANDBOOK.th.md): Thai-language parity of the ecosystem handbook. [AI-Search Handbook — English](ai-search/HANDBOOK.en.md): Guidance for AI retrieval agents ingesting this corpus. Defines the two-layer corpus architecture (handbook=summary, repo=canonical), provides a full canonical-source map table (topic to GitHub URL), citation rules (five rules including version pinning and no local paths), freshness signals, a safe-to-assert facts list, an exhaustive hallucination-traps list, and instructions for using llms.txt and the glossary. [AI-Search Handbook — Thai](ai-search/HANDBOOK.th.md): Thai-language parity of the AI-search handbook. Same structure; English is canonical on conflicts. [Handbook Glossary — English](glossary.en.md): Quick-reference one-line definitions of every term a handbook reader may encounter, including all Pali engineering labels. For full engineering treatment and framework membership, follow links to the repo GLOSSARY and PHILOSOPHY docs. [Handbook Glossary — Thai](glossary.th.md): Thai-language parity of the handbook glossary. [Quickstart — English](quickstart/HANDBOOK.en.md): A guided ~10-minute end-to-end tutorial: install, `bwoc init`, `bwoc new` + `bwoc check`, talk to the agent (`chat`/`run`), make a team + task, observe, and retire. The hands-on companion to the reference end-user page. [Quickstart — Thai](quickstart/HANDBOOK.th.md): Thai-language parity of the quickstart. [Single-Agent Workspace — English](single-agent/HANDBOOK.en.md): When and how to run a one-agent workspace (`bwoc init --single-agent`) instead of the multi-agent fleet — profile differences, driving the single agent, and growing into a fleet later. Note: there is no machine-wide "global agent"; cross-machine sharing is the cross-workspace (peer/A2A) story. [Single-Agent Workspace — Thai](single-agent/HANDBOOK.th.md): Thai parity of the single-agent chapter. [Security & tianting — English](security/HANDBOOK.en.md): Security with BWOC — the threat model (Three Cravings: manipulation/persistence/destruction), the Five Precepts safety floor, audit logging (Three Doors), inter-agent trust + ed25519 signing, fleet-health signals, and the 8-agent tianting (天庭) security team (yudi/erlang/zhongkui/yanluo/laojun/xuanwu/nezha/taibai) with the monitor→hunt→patch→report incident loop. Red-team is authorized-use only. [Security & tianting — Thai](security/HANDBOOK.th.md): Thai-language parity of the security chapter. [Cross-workspace — English](cross-workspace/HANDBOOK.en.md): Connecting workspaces & agents across machines — `bwoc peer` (list/status/learn/feedback) + routes.toml, the Agent2Agent (A2A) protocol via bwoc-a2a (Agent Card, JSON-RPC, HTTP), and MQTT transport via bwoc-mqtt, all over ed25519-signed envelopes. [Cross-workspace — Thai](cross-workspace/HANDBOOK.th.md): Thai-language parity of the cross-workspace chapter. [Self-hosting (Harness) — English](harness/HANDBOOK.en.md): Running agents on Ollama / any OpenAI-compatible model via bwoc-harness (OpenAI-compatible provider, agentic loop, core tools, tool-auth, task queue, telemetry, Sīla-5/Taṇhā-3 guardrails, Tier-2 memory, chat_proto, `bwoc chat --tui`). Covers manifest `baseUrl` and dependency quarantine. [Self-hosting (Harness) — Thai](harness/HANDBOOK.th.md): Thai-language parity of the harness chapter. [Fleet Operations — English](fleet-ops/HANDBOOK.en.md): Running many agents reliably — `bwoc fleet health` (seven Non-Decline signals), `bwoc supervise` (restart-on-crash + backstop), `bwoc sessions`/`list` filters/`ping`/`dashboard`/`log`/`inbox`, `bwoc doctor --auto`, `bwoc workspace validate/prune`, and bulk `stop/start --all`. [Fleet Operations — Thai](fleet-ops/HANDBOOK.th.md): Thai-language parity of the fleet-ops chapter. [Council — English](council/HANDBOOK.en.md): Structured fleet decisions via the council plugin kind — the propose → discuss → vote → resolve protocol, voting models (simple-majority / consensus / weighted / sangha), quorum, and the append-only Council Decision record with dissent preserved. [Council — Thai](council/HANDBOOK.th.md): Thai-language parity of the council chapter. [FAQ & Troubleshooting — English](faq/HANDBOOK.en.md): Consolidated common questions (no Pali needed, backend choice, agent lifecycle, workspace resolution, memory cap, neutrality, daemon issues, versioning) plus a symptom→cause→fix table. The canonical FAQ is the GitHub FAQ.en.md. [FAQ & Troubleshooting — Thai](faq/HANDBOOK.th.md): Thai-language parity of the FAQ chapter. [Chat Connectors (Telegram & Discord) — English](connect/HANDBOOK.en.md): Bring a BWOC agent into Telegram & Discord via the bwoc-connect crate (long-poll/gateway, DM+group, keyring secrets, daemon-supervised). [Chat Connectors (Telegram & Discord) — Thai](connect/HANDBOOK.th.md): Thai parity. [Google Workspace — English](google-workspace/HANDBOOK.en.md): Connect BWOC to Google Workspace via the gws plugin family (auth/drive/gmail/calendar; install/enable, scoped read-mostly ops). [Google Workspace — Thai](google-workspace/HANDBOOK.th.md): Thai parity. [Jira & SCRUM — English](jira-scrum/HANDBOOK.en.md): Jira & SCRUM: the jira-cloud-rest plugin (kind jira, project-scoped JQL + gated transitions) + the scrum-via-jira skill (sprint verbs); kind-dependency model. [Jira & SCRUM — Thai](jira-scrum/HANDBOOK.th.md): Thai parity. [ISO Standards Audit — English](iso-audit/HANDBOOK.en.md): Machine-assisted ISO audits via audit-kind plugins (ISO 9001/27001/20000-1/29110): attestations + SoA + samples, read-only findings. [ISO Standards Audit — Thai](iso-audit/HANDBOOK.th.md): Thai parity. [OKR Plugin — English](okr/HANDBOOK.en.md): Manage OKRs in BWOC via the okr plugin (objectives/key-results in local TOML; track / check-progress / report verbs; ties to fleet governance). [OKR Plugin — Thai](okr/HANDBOOK.th.md): Thai parity. ## Canonical framework docs [ARCHITECTURE](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/ARCHITECTURE.en.md): Implementation stack — how framework repo, agent template, incarnated agents, the bwoc CLI, and backend execution fit together. Includes an ASCII layer diagram, crate map (bwoc-cli / bwoc-agent / bwoc-core / bwoc-harness), and information-flow description. Canonical for questions about component relationships and process topology. Thai: [ARCHITECTURE.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/ARCHITECTURE.th.md) [DESIGN](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/DESIGN.en.md): Design-system tokens for BWOC UIs (bwoc dashboard ratatui TUI, bwoc chat --tui, bwoc-chat egui desktop). Defines ColorToken {ansi, rgb}, glyph tokens, and spacing/layout tokens. Canonical for any question about UI consistency, colour meaning, or frontend integration. Thai: [DESIGN.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/DESIGN.th.md) [FAQ](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/FAQ.en.md): Authoritative answers to frequently asked questions about BWOC — installation, workspace setup, backend selection, agent creation, memory limits, teams, versioning, and troubleshooting. Prefer this over handbook troubleshooting sections for canonical answers. Thai: [FAQ.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/FAQ.th.md) [FLEET-GOVERNANCE](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/FLEET-GOVERNANCE.en.md): Defines the seven Aparihāniya-dhamma fleet-health signals checked by `bwoc fleet health`. Explains what each signal measures, how it maps to the Pali engineering label, and how to interpret results. Canonical for multi-agent fleet health and governance questions. Thai: [FLEET-GOVERNANCE.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/FLEET-GOVERNANCE.th.md) [GLOSSARY](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/GLOSSARY.en.md): Alphabetical table of every Pali term used in BWOC with a one-line engineering meaning. Includes a note that Pali terms are engineering labels, not religious content. For full framework membership and composition rules, links to PHILOSOPHY.en.md. Canonical for precise Pali-term definitions. Thai: [GLOSSARY.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/GLOSSARY.th.md) [HARNESS](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/HARNESS.en.md): Documents the `bwoc-harness` crate — the self-hosted OpenAI-compatible agentic loop runtime used for Ollama and other provider-neutral backends. Covers dep-quarantine design, safety guardrail layer (Sīla 5 + Taṇhā 3), Tier 2 memory integration (wake-up/search/mine), chat_proto event stream, and the TUI chat client. Canonical for self-hosted deployment questions. Thai: [HARNESS.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/HARNESS.th.md) [INCARNATION](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/INCARNATION.en.md): Single source of truth for creating a new agent from the template. Explains what incarnation means (uppāda phase), prerequisites, the canonical `bwoc new` CLI path and the legacy `incarnate.sh` shell-script path, manifest field resolution, placeholder substitution, backend symlink creation, and the post-incarnation `bwoc check` step. Thai: [INCARNATION.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/INCARNATION.th.md) [NAMING](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/NAMING.en.md): Naming conventions for everything in BWOC: agent IDs (kebab-case `agent-`), workspace files, slot directory names, skill/plugin names, note slugs (`YYYY-MM-DD_.md`), and the `{{camelCase}}` placeholder convention. Canonical for any naming question. Thai: [NAMING.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/NAMING.th.md) [PLUGINS](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/PLUGINS.en.md): Documents the framework plugin system — plugin manifest format, `modules/plugins/<name>/` layout, install from local path / git URL / tarball with SHA-256 trust gate, enable/disable/remove CLI (`bwoc plugin`), workspace.toml registration, and the distinction between plugins (workspace-level) and skills (agent-level). Thai: [PLUGINS.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/PLUGINS.th.md) [RELEASING](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/RELEASING.en.md): Documents the dual-version release process: CalVer Git tag (`vYYYY.M.D-<patch>`) triggers `release.yml` CI to build cross-platform binaries (Linux x86_64, macOS aarch64 + x86_64, Windows x86_64) with SHA-256 checksums. Explains the Cargo SemVer vs CalVer distinction, same-day reissue convention, and the auto-version hook that bumps patch on every edit. Thai: [RELEASING.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/RELEASING.th.md) [SIGNING](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/SIGNING.en.md): Documents ed25519 signing keypair generation (`bwoc trust --keygen`), where keys are stored (`<agent>/.bwoc/agent.key` at 0600, public key in manifest `signingPublicKey`), the Kalyāṇamitta-7 trust scoring model for inter-agent trust, and cross-workspace signed feedback envelopes (`bwoc peer feedback`). Canonical for inter-agent trust and signing questions. Thai: [SIGNING.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/SIGNING.th.md) [SKILLS](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/SKILLS.en.md): Documents the framework skills system — skill manifest format, maturity levels L1 (beginner) through L7 (mastery), `modules/skills/<name>/` layout, the `bwoc skill` CLI (list/show/verify/init/install/enable/disable/remove), the SHA-256 trust gate on install, and the `[gates].verify` static-check mechanism. Canonical for skill authoring and management. Thai: [SKILLS.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/SKILLS.th.md) [WORKSPACE](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/en/WORKSPACE.en.md): Documents the `.bwoc/` workspace directory layout: `workspace.toml`, `agents.toml` registry, `teams/`, `memory/`, `inbox.jsonl`, `routes.toml` (peer workspaces), `doc-kinds.toml` (custom document types). Explains `bwoc init` scaffolding, `--no-runtime` and `--single-agent` modes, `bwoc workspace` validation and prune, and workspace resolution (--workspace > BWOC_WORKSPACE env > ancestor walk). Thai: [WORKSPACE.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/docs/th/WORKSPACE.th.md) ## Spec & philosophy [Agent identity spec (AGENTS.md)](https://github.com/bemindlabs/BWOC-Framework/blob/main/modules/agent-template/AGENTS.md): The specification every incarnated agent's `AGENTS.md` must conform to. Plain Markdown only — no YAML frontmatter, no wikilinks, no callout blocks, no hardcoded vendor or model names. All configurable values use `{{camelCase}}` placeholders resolved at `bwoc new` time. Backend entry files (CLAUDE.md, AGY.md, CODEX.md, KIMI.md, OLLAMA.md, OPENAI.md) are symlinks to this file. Spec version 2.0. [Philosophy — 22 Buddhist-framework mappings (EN)](https://github.com/bemindlabs/BWOC-Framework/blob/main/modules/agent-template/docs/en/PHILOSOPHY.en.md): Full mapping of every Pali term to its engineering framework, design rationale, what it determines in code and process, and how it composes with related terms. Twenty-two frameworks organized by concern (architecture, lifecycle, memory, error handling, inter-agent trust, fleet governance, threat modeling, code of conduct, self-improvement). Canonical for understanding why any Pali term exists. Thai: [PHILOSOPHY.th.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/modules/agent-template/docs/th/PHILOSOPHY.th.md) [VERSION.md](https://github.com/bemindlabs/BWOC-Framework/blob/main/VERSION.md): Auto-maintained version file. Contains Software-Version (Cargo SemVer, canonical in Cargo.toml, auto-bumped on .rs/.toml edits), Document-Version (bumped on .md edits), Phase (current implementation milestone), Latest release (CalVer tag), and Last-Updated (UTC ISO 8601 timestamp of last edit). Must be read at query time for any version-sensitive claim; never use a cached value. ## Machine files [llms.txt](llms.txt): This file. Machine index of the BWOC handbook corpus following the llms.txt convention. Lists every handbook page and every canonical framework document with a one-paragraph description of each. Use as the entry point for corpus enumeration before fetching individual pages. [robots.txt](robots.txt): Crawler access policy for this handbook corpus. Specifies which paths are open to indexing and which to skip (ephemeral or private content). [sitemap.md](sitemap.md): Human- and machine-readable sitemap of the handbook. Lists every page with its path, role audience, language, and a one-line description. Complements llms.txt for crawlers that prefer Markdown over the llms.txt format.