jade-core-orchestrator

Automate JADE migration by running a deterministic, disk-backed state machine that advances sequential phases from workspace checks to final verification. This orchestrates tooling scouting, build fixes, and rule batching without passing bulky data through prompt context.

To protect cross-package contracts during Java version upgrades, process one rule across all flagged files sequentially before verification and commit. This rule-by-rule migration approach isolates breaking changes and enforces strict artifact-backed gating.

Disk-based artifact management reads and writes run state, progress logs, rule status, and failure summaries to disk. This makes every state transition auditable and resume-safe by applying hash-based integrity checks and required artifact schemas.

Yes, you can resume a Java migration run after failures because the orchestrator supports retry and escalation paths. It enforces operational guardrails that stop on gate failures and validates workspace readiness before resuming subprocess execution.

You need phase gates and hash validation when executing sequential Java-version migration pipelines that require strict rule-by-rule batching. This ensures deterministic execution and verifies artifact integrity before advancing tooling, build, scan, and verification phases.