preflight gating
This commit is contained in:
parent
4f8d8a1f52
commit
18299b03aa
7 changed files with 157 additions and 5 deletions
|
|
@ -310,6 +310,9 @@ Resolves an assessment profile into an executable run plan:
|
|||
- isolation and timeout policy,
|
||||
- artifact retention policy.
|
||||
|
||||
At execution time, a failing preflight blocks downstream check groups for the
|
||||
same extension so expensive or misleading harness steps are not invoked.
|
||||
|
||||
### Runner Bridge
|
||||
|
||||
Executes or coordinates extension checks.
|
||||
|
|
|
|||
|
|
@ -182,6 +182,11 @@ package `artifact_manifest`.
|
|||
If a Python runner raises an exception, the core converts that failure into
|
||||
`infrastructure_error` evidence so the assessment package remains complete.
|
||||
|
||||
Preflight runners are gates. If an extension preflight returns `fail`, `blocked`,
|
||||
or `infrastructure_error`, downstream check groups for that extension are not
|
||||
executed; they receive `blocked` evidence with `blocked_reason:
|
||||
preflight_failed`.
|
||||
|
||||
## Result Statuses
|
||||
|
||||
Initial statuses:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue