Finalize artifact workflow documentation
This commit is contained in:
@@ -54,12 +54,14 @@ kind and prepared filename vocabulary.
|
||||
Configured definitions are always registered. Without an explicit selection,
|
||||
the effective analyze set contains enabled definitions. With `--artifacts`, the
|
||||
exact named configured definitions become the effective set for that invocation,
|
||||
regardless of their `enabled` value; dependencies are not added implicitly.
|
||||
Availability is separate from executability. Configured outputs, including
|
||||
non-executable prerequisites, become available only when the versioned analyze
|
||||
state identifies a current result whose source, contract, canonical configured
|
||||
path, size, and checksum match a confined no-follow regular file. An incidental
|
||||
canonical file and a legacy aggregate analyze output are unavailable.
|
||||
regardless of their `enabled` value. The effective-set resolver itself does not
|
||||
expand dependencies; the analyze work planner closes those targets over their
|
||||
configured prerequisite graph. Availability is separate from executability.
|
||||
Configured outputs, including non-executable prerequisites, become available
|
||||
only when the versioned analyze state identifies a current result whose source,
|
||||
contract, canonical configured path, size, and checksum match a confined
|
||||
no-follow regular file. An incidental canonical file and a legacy aggregate
|
||||
analyze output are unavailable.
|
||||
Extraction entries are registered from configuration and become available only
|
||||
after compatible extraction evidence is hydrated.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user