Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Documentation Index

Canonical documentation for project-agent-manager (pam) — a multi-host platform (central orchestrator + per-host workers, PostgreSQL-backed; ADR-012) for hierarchical project/task management and AI task orchestration via tmux-hosted LLM CLIs.

All architecture and contract documents are written in English and carry frontmatter with an implementation: status. Never treat a proposed (or placeholder) document as shipped behavior — see 004-implementation-reference.md for the truthful snapshot of what exists in code.

Numbering Scheme

Documents are numbered 0xx and grouped by domain bands. Reading order within the table is numeric.

Reading Order

Reviews: reviews/ — dated design-review records (e.g., 2026-08-29); historical, never canon.

Canon Selection

Which document answers which question — each decision lives in exactly one canonical document:

Documentation Rules

  • Every architecture/contract/UI/roadmap document carries frontmatter: type, authority (canonical|derived), implementation (proposed|partial|placeholder|not-applicable), verification, source, last_verified, owners.
  • implementation: placeholder marks a domain skeleton with no designed content yet — it only reserves the number and points at scattered material; never cite it as a decision source.
  • authority: canonical documents own their decisions; other documents link instead of restating.
  • Overturning a working default recorded in 071-risks-and-open-questions.md must update the affected canonical doc(s) and code in the same commit.
  • Architecture/contract docs are in English; top-level README may be bilingual (Korean/English).
  • Diagrams: Small inline state/dependency diagrams are allowed in prose; CANONICAL diagrams must be .mermaid files under assets/diagrams/ and registered in the diagram registry (no orphans).
  • Verification convention: One executable one-line directive per document (e.g., “Execute all endpoints and validate against curl”).
  • Numbering: a new document takes the next free number in its domain band; a new domain claims the next free decade (e.g., 080–089). Numbers are never reused after a document is deleted.