Configuration Reference
Decapod project policy is defined in .decapod/config.toml. This file should be committed to source control and is the primary mechanism for humans to communicate global rules to agents.
The [init] Section
Governs the behavior of the decapod init command.
| Key | Type | Default | Description |
|---|---|---|---|
specs | bool | true | If true, scaffolds living documentation under .decapod/managed/specs/. |
diagram_style | enum | "ascii" | Preferred style for generated architecture diagrams ("ascii" or "mermaid"). |
entrypoints | list | [...] | The agent entrypoint files to maintain (e.g., AGENTS.md, CLAUDE.md). |
The [repo] Section
Defines the operational policy and metadata for the repository.
| Key | Type | Default | Description |
|---|---|---|---|
product_name | string | None | The canonical name of the software product. |
product_summary | string | None | A high-level description of the product's purpose. |
architecture_direction | string | None | The intended architectural style (e.g., "monolithic", "event-driven"). |
product_type | string | None | Categorization (e.g., "cli", "library", "service"). |
done_criteria | string | None | The global definition of "done" that all work must satisfy. |
primary_languages | list | [] | The primary programming languages used in the repository. |
detected_surfaces | list | [] | Entrypoints and interfaces detected in the repo (e.g., "cargo", "npm"). |
external_tracker | bool | false | Whether Decapod should expect and validate external issue references. |
container_workspaces | bool | true | If true, Decapod will strongly encourage/enforce Docker isolation for worktrees. |
backend | enum | "local" | Storage backend for the project todo path ("local" or "cloud"). Cloud uses the binary-owned Propodus endpoint and GitHub origin identity. |
Cloud service details are intentionally not project configuration. Decapod
owns the Propodus deployment defaults in the binary, derives repo_id from
the GitHub origin, and keeps credentials machine-local.
Schema Versioning
Decapod uses a schema_version key at the root to ensure forward and backward compatibility as the governance kernel evolves.
schema_version = "1.0.0"
[init]
specs = true
diagram_style = "mermaid"
[repo]
product_name = "decapod"
container_workspaces = true
done_criteria = "Validate passes and all unit tests are green."