jade-core-batch-processor

To process one migration rule at a time, you build a single-rule batch from the flag index and track file-level completion state. This ensures the orchestrator processes, verifies, and commits exactly one rule_id before starting the next.

Per-file status tracking during a migration pipeline involves grouping flagged entries by file, assigning statuses, and persisting progress. This approach writes atomic JSON artifacts so interrupted sequential batching runs can resume safely.

Sequential batching handles interruptions by enforcing per-file status tracking and atomic JSON artifact writes. It persists completion state for each flagged file, allowing the migration pipeline to resume cleanly from the last committed rule batch.

Yes, single-rule batching requires 04-flag-index.json and 05-rule-queue.json as inputs. These JSON artifacts provide the flagged file entries and rule queue sequence needed to build the current batch and apply strict validation.

Migration rules should be processed sequentially to prevent loosely coordinated per-file edits. Sequential batching with strict validation and atomic writes keeps downstream verification and commit steps aligned with the current rule.

Yes, batch processing tracks completion state across dozens of flagged files by grouping entries, assigning statuses, and writing aggregate status files. This keeps downstream verification aligned until the entire rule batch is complete.