Air traffic control for AI coding

Nool Troubleshooting

Troubleshoot Nool setup and workflow issues by checking status, doctor output, artifact verification, and task operation ordering.

Use status to inspect DAG heads and pending proposals.
Use doctor for release-readiness and filesystem hygiene.
Create task updates sequentially to avoid sibling task heads.

Multiple DAG heads

Run status and doctor. If the issue came from concurrent task operations, create future task updates sequentially.

nool status --compact

Release outdated

Doctor reports this when the DAG head is newer than the last release. That is expected after task or implementation work until a new release is cut.

nool doctor

Installer verification

Download the matching checksum file for the artifact and compare SHA256 before installation in controlled environments.

Nool: AI Engineering Governance & Agent Reliability

The governance layer for AI-native engineering teams

Nool governs each repository and coordinates the workspace above it. Engineering leaders can turn cross-project goals into real child-ledger tasks, roll release health and operating metrics upward, and trace delivery back to signed implementation evidence.

Built for engineering managers, CTOs, and principal engineers who need one recursive control model from organizational intent to project execution without creating a shadow management ledger.

Key capabilities: workspace topology reconciliation, goal-to-task decomposition, conservative release-health rollups, child-ledger insights, dependency-ordered coordination, semantic blast radius analysis, provenance, and policy-gated changes.