Start from the top-level operating model: ProcessForge is installed once as a
tool, a workplace is the machine-level home for reusable resources, and each
repository keeps only a project-local .pf/ layer.
The required initialization order is workplace first, workplace resources second, and project onboarding third. Use guided workplace setup by default for human-led machine setup. Use the fully automatic path only when the operator provides explicit paths and choices.
- Top-level README
- Quickstart prompts
- Installation
- Guided workplace setup
- Initialization order
- Workplace vs project
- Resource authoring
- Project onboarding
- Built-in process stages
- Agent command runbook and prompts
- Guided workplace setup agent prompt
- Automatic workplace initialization agent prompt
- Project onboarding agent prompt
- Release checklist
- Validation
- First run
- Installation
- Initialization order
- Workplace initialization
- Guided workplace setup
- Project onboarding
- Agent command runbook and prompts
- Create your first process
- Task batch workflow
- Built-in process stages
- Multi-agent orchestration
- Runtime driver and supervisor quickstart
- Quick getting started path
- Russian documentation
- Reusable templates
- Knowledge packages
- Platform contracts
- Knowledge resource navigation
- Process authoring
- Authoring parity
- Backfill existing processes
- Resource authoring
- Task batch execution
- Workplace vs project
- Path constants
- Context resolution
- Cascade merge
- Package roots
- Package roots overview
- Project snapshot
- Project snapshot overview
- Hooks and events
- Hooks and events overview
- Runtime model
- Agent session model
- Project coordination modes
- Runtime drivers
- Process supervisor
- Director, ledger, inspector, and worker boundary
- Platform inheritance
- Process definition, run, task, iteration
- Semantic parity
- Runs, tasks, and iterations
- Multi-agent orchestration
- Known limitations
- Workplace device: computer, laptop, server, or runner host.
- ProcessForge tool root: CLI, schemas, processes, docs, templates, checks.
- Global workplace resources: knowledge packages, reusable templates, tools, MCP providers, platform contracts, roots, registries, runtime data.
- Project
.pf/layer: selected resources, project context, assignments, runs, tasks, iterations, artifacts, reviews, handoffs, hooks.
Platform contracts are composition manifests. They can model a single platform or a parent/child stack and connect the resources needed by a concrete project. Process definitions remain platform-agnostic process mechanics.