what a paragraph would tell them is already in the code.
Write a comment only when a reviewer would otherwise have to ask **why** the code exists:
- a non-obvious
flagged.
## Key Sections
- **Issue Tracking** - How to use bd for work management
- **Development Guidelines** - Code standards and testing
- **Project Scope** - Read [engdocs/PROJECT_CHARTER.md](engdocs/PROJECT_CHARTER.md) before adding new feature surface area
- **Visual
derived files retain GPL-3.0-only provenance and the exact source revision. Helium-derived code is not available under Manaflow's commercial license.
- Other bundled dependencies retain their own terms
reach for `let`.
### Naming Enforcement (Read This)
THIS RULE IS MANDATORY FOR AGENT WRITTEN CODE.
- Use single word names by default for new locals, params, and helper functions.
- Multi-word
CONTRIBUTING.md](CONTRIBUTING.md#release-notes) for details.
In addition, there are rules inferred from previous codereviews. Follow them like a
reviewer's note: they encode reasons, not ceremony, so when
open a pull request or link a branch when code is available.
## Pull requests
Before opening a pull request:
1. Review `CONTRIBUTING.md` and follow the repository PR template.
2. Keep
path the old text served.
- Ordinary code under `src/`, `tests/`, and `scripts/` gets ordinary codereview; these rules are about instruction prose.
### Acting on review feedback
This governs any agent
narrate the code or restate names, types, or assertions.
- Type hints required for all code
- Public APIs must have docstrings. When a public API raises exceptions a
caller would reasonably
wiki/architecture/tools.md`.
## When making architecture-sensitive changes
Read the relevant page in `wiki/architecture/` **before** writing code. The page list lives in `wiki/architecture/README.md`. As a minimum:
- Adding a node type → `node-schemas.md`, `renderers.md
install` once, then `npm test` or `npm run build`; repeat for `research/` and `index/`.
## Coding Style & Naming Conventions
- Python: 4-space indentation, Black line length 88, Ruff
archon/workflow-language-constitution.md`](.archon/workflow-language-constitution.md), aspirational engineering craft and review values in [`.archon/engineering.md`](.archon/engineering.md), user documentation in the docs site, and machine-checkable rules in code, types, tests, lint, or CI.
## Read before
every code change and `npm run build` after MCP server changes.
- After rebuilding server code, ask the user to reload the MCP server before testing the changed MCP behavior.
- Name
rerun affected checks without asking at each step. Continue into PR
publication and review follow-up when requested. A first patch or lifecycle handoff is not completion.
Keep local verification
review documentation.
This file owns agent-specific documentation routing and workflow.
- Write clear, accurate, task-oriented documentation for developers who run NemoClaw with OpenClaw, Hermes, LangChain Deep Agents Code
they matter.
- Prefer a direct, focused tool over overlapping projections or orchestration layers. Ordinary codereview, representative harness exercises, and repository hooks are the validation boundary. Do not add repository
messaging egress opt-in unless accepted product policy states otherwise. Load `nemoclaw-maintainer-security-code-review` when the change affects credentials, public ingress, sender authorization, network policy, or another trust