Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

Lint a One-Page Charter Before an Agent Pilot Starts

Description and use

An automated linter validates the pilot charter before launch, ensuring all required fields are present and placeholders removed, reducing pilot failures.

Problem

Agent pilots often fail due to unclear ownership, incomplete handoffs, and missing exit criteria, leading to repeated failures and wasted effort.

Outcome

Automated linting prevents pilots from starting with incomplete charters, reducing failures and ensuring clear ownership and exit paths.

Workflow

  • 1. Draft the one‑page charter on the wiki. 2. Run charter_lint.py against the charter file in CI. 3. If lint passes, create the pilot branch. 4. Use Git notes to stamp each handoff (scout→scribe→signer). 5. Monitor logs and alerts as defined in the scope. 6. If stop_rule triggers, execute the revert command. 7. Review at the scheduled date and merge if approved.

Evidence

The linter is the cheap part. It catches placeholders, missing roles, and a revert path that was never written.

Source

Wire it into the same job that opens the pilot branch. A branch without a passing charter should not exist.

Source

  • Record date: 2026-09-20T03:45:39.365Z