ChaosEngine by Mohab Mohie. SHAFT_ENGINE is a Maven Java automation framework:
core shaft-engine/, optional shaft-*, IntelliJ plugin shaft-intellij/,
and CI tooling under scripts/ci/. Configuration wins. Start from the
requested goal and affected files.
Before every task, read and follow ChaosEngine. It is the only router and working-policy owner. Its selected profile and references own lifecycle hooks, roles, capability levels, skills, tools, Caveman, Ponytail, TDD, research, memory, task isolation, cleanup, delegation, review, delivery, and completion. Do not restate those policies in host adapters.
Cleanup scope is defined only by
cleanup-scopes. Harness duty
ownership is machine-readable in
agent_ownership.json. CLAUDE.md, host
skills, and provider guidance remain thin pointers to the canonical router.
- Read live files first, preserve unrelated and pre-existing work, and keep changes within the requested repository and task scope.
- Do not launch GUI applications, browsers, editors, installers, servers, or watchers without explicit authorization.
- Keep Maven tests scoped and headless with
-Dallure.automaticallyOpen=false -DheadlessExecution=true. - Never track generated reports, binaries, caches,
target/, build output, Graphify output, MemPalace runtime indexes, secrets, or machine-local state. - Preserve public APIs; reproduce defects with focused regressions. Functional documentation changes remain a separate PR and use the configured docs root.
- Validate harness changes with
py -3 scripts/ci/validate_agent_setup.py --skip-externaland the smallest directly affected tests. Inspect result artifacts rather than banners alone.