x-evaluate-parallelism

Classifying parallel work collisions helps avoid conflicts and rework by categorizing risks into hard, regen, or soft groups. This classification uses a parallelism-heuristics knowledge pack to evaluate file footprints and suggests serialization groups for safe concurrent execution.

Yes, you can validate an implementation map before parallel dispatch by comparing the file footprints of involved artefacts. This evaluates epic, story, or task scopes to identify and quantify parallel-work collision risks, ensuring safe concurrent execution before work begins.

Generate a collision report by providing the target scope and involved artefacts to the analysis process. It outputs a deterministic Markdown or JSON report detailing hard, regen, and soft collisions, which can be used for governance and pre-dispatch checks.

Avoid running work units in parallel when the collision risk assessment identifies hard collisions in the file footprints. These hard collisions require serialization to prevent conflicts, whereas regen and soft collisions might be managed with suggested serialization groups.