Embed in a route
<FigureFromSource sourcePath="content/publications/figures/services/apc-backed-review.dsl.md" figureId="PATHS-02" />
PATHS-02
Path Validation Workflow
Candidate paths are challenged for evidence, ordering, consequence, and alternatives before they become reportable.
governed lifecycle
Review workflow
- 1Ingest representative findingsAccept the agreed finding, trace, graph, or partner object with source references.
- 2Construct candidate pathsGroup related findings and relationships without assuming the chain is valid.
- 3Challenge evidenceConfirm each step, source, precondition, and relevant observation.
- 4Challenge orderingReview prerequisites, transition feasibility, and alternate sequences.
- 5Bound consequenceLimit impact to what the evidence and reachable actions support.
- 6Correct or rejectSplit, downgrade, revise, or reject unsupported paths.
Retest loop returns to Construct candidate paths
What result is reportable?
- Grounded path
- Explicit inferred extension
- Rejected path
- Analyst-reviewed result
About this figure
This review workflow governs how candidate paths become reportable findings. It starts by ingesting representative findings and constructing candidate paths, then subjects each path to explicit challenge: what evidence supports it, whether the ordering is correct, what consequence actually follows, and whether credible alternatives explain the same observations. Paths that cannot survive these checks are corrected or rejected, and both outcomes remain traceable so later reviewers can see how the conclusion evolved. Review controls ensure that only humans set the analyst-reviewed state, preserving accountability while keeping partner ownership and source context intact throughout the lifecycle.
Citation
Path Validation Workflow (PATHS-02). SecEng Figure Library. https://aisecurity.llc/publication-dsl/figures/PATHS-02