Path Roles and Outcome Classes
Understanding How Exploit Paths Are Composed
Separate what a capability is from what it is doing in the route and what state the route reaches.
On this page Open module guide
- Distinguish primitive families from path roles and outcome classes.
- Explain why role and outcome need to stay separate in a reusable model.
- Read a grounded case across all three layers.
This module structure is live. Full lesson copy is still moving through review.
The public skeleton exists so the course can launch as a real learning surface now. As modules are approved, the full lesson body, exercises, and supporting links will replace the current placeholder blocks.
Narrative Overview
This lesson will make composition legible by separating recurring capability type, role in the route, and resulting state.
The final published version of this section will expand from the approved module draft and connect back to the rest of the site where relevant.
Core Reading
The published lesson will connect terminology discipline directly to stronger exploit-path analysis.
The final published version of this section will expand from the approved module draft and connect back to the rest of the site where relevant.
Key Concepts and Explainers
The final lesson will focus on clean distinctions and show why collapsing these categories causes confusion later.
The final published version of this section will expand from the approved module draft and connect back to the rest of the site where relevant.
Practical Exercise
The exercise layer will ask learners to classify one route by family, role, and outcome without conflating them.
The final published version of this section will expand from the approved module draft and connect back to the rest of the site where relevant.