Verify record inheritance through pipeline resolution

This commit is contained in:
2026-11-18 00:32:13 +00:00
parent 1febd2edfa
commit 1c93aa0947
3 changed files with 62 additions and 2 deletions

View File

@@ -186,6 +186,14 @@ step requirement. Validator chains are not automatically identified. Authors
may declare identities for other lists when needed. CLI list assignment replaces
the complete decoded list.
Record inheritance does not create template-only steps: every record in the
final step list executes and must have artifact lanes. A child that inherits
its parent's named lanes also conflicts with the requirement that lane IDs be
unique across steps; adding differently named lanes does not remove inherited
ones. Use pipeline-level inheritance with step upsert for pipeline variants.
Native identified-record inheritance is also available in compatible collections,
such as an author-identified validator list, subject to ordinary domain validation.
For example, an overlay can opt into replacing a pipeline's steps:
~~~yaml