Answer A-290: a step answer over the steps state's bound is kept as an object the key names
mesh/delivery merged: source.main moved to novox/hq@43612bf1be0a
mesh/check checking 048545b266bb on 43612bf1be0a
mesh/delivery merged: source.main moved to novox/hq@43612bf1be0a
mesh/check checking 048545b266bb on 43612bf1be0a
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -422,3 +422,7 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
watched branch, §505's manifest without MAJOR.MINOR, a candidate) counts as done, and the builder's unpublished
|
||||
count holds no package at all: a reserving build's package is published or its build fails, and a done key is never
|
||||
built again under a reservation, so no seat republishes a package (principle 7). The count holds images only.
|
||||
- **A-290** (A-254, §467; principles 3 and 7) A step's key in its build module's steps state keeps the step's answer
|
||||
only within the state's bound per value; an answer over it, a check's or a run's alike, is kept as the object
|
||||
`output.<ask>` in the module's outputs store and the key names it, and every reader (the checker, the asker) reads
|
||||
the answer from the key or the object it names. No step ends passed in one place and failed in another.
|
||||
|
||||
Reference in New Issue
Block a user