dokugent init¶
Initializes a new Dokugent project by creating the required folder structure, setting up agent scaffolding, and optionally bypassing the wizard with default values.
What It Does¶
- Scaffolds
.dokugent/directory structure - Generates
README.md, agent spec files, and tool list
Behavior Overview¶
This command runs in non-interactive mode and creates a standard .dokugent/ folder structure with default subdirectories for agent data, operational output, and audit scaffolding. There are no configuration prompts or flags — it is a deterministic scaffold step.
Directories Created¶
.dokugent/
├── audit/
│ ├── ignatures/
│ └── trace/
├── data/
│ ├── agents/
│ ├── compliance/
│ ├── conventions/
│ ├── criteria/
│ ├── io/
│ ├── plan/
│ └── tool-list/
├── ops/
│ ├── certified/
│ ├── compiled/
│ ├── logs/
│ ├── preview/
│ └── reports/
├── overrides/
Additional Files¶
.dokugent/README.md→ static intro
Console Output Example¶
Running dokugent init...
Created base .dokugent structure.
.dokugent/
├── audit → Signature logs and trace evidence
├── data → Editable input: agent, plans, tools, rules
├── ops → Output folders: preview, compiled, certified agents
└── overrides → Local dev overrides like whitelists
📄 Files created:
- .dokugent/README.md
➡️ You can now run: dokugent agent
Best Practices¶
- Run
dokugent initonly once per project or environment. - Keep
.dokugent/dataunder version control for agent transparency. - Use timestamped folders to manage versions without overwriting history.
- Avoid modifying scaffolded files directly unless using overrides.