eric/notarius
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Include validator policy in pipeline identity

Browse Source
This commit is contained in:
Eric Rakestraw
2026-07-17 13:33:16 +00:00
parent 3e4fa923eb
commit 35e45f0914
4 changed files with 193 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/internal/pipeline.md
View File

@@ -31,13 +31,19 @@ calls `pipeline.ResolvePipeline`.
7. validates each selected module and validator option set through its registry
entry; and
8. calculates a digest over the resolved structure, including typed artifact
kind and schema identity.
kind and schema identity and the effective validator policy in its resolved
execution order.
Resolution returns a `ResolvedPipeline` containing ordered lanes, concrete
bindings, validator chains, reference targets, and the digest. It does not read
reference bytes or construct runtime modules. CLI lane and reference selector
syntax is defined in the [CLI reference](../cli.md#run).
The digest includes each resolved validator chain's stage, lane, owning module,
ordered validator bindings, execution classes, targets, and artifact kinds.
Changing a default chain or an explicit override therefore changes pipeline
identity whenever it changes the effective validator policy.
## Reference Materialization
The CLI calls `MaterializeReferences` after resolution and before constructing