A.15.PROD:5.9 - ReleaseBinary 12: complete build-to-inception replay
BuildOps asks one question: when did exact ReleaseBinary_12 first exist? Verification, transfer, release, deployment, publication, and availability are not part of this answer. The fixture uses one affected referent and one transformation; it does not hide an unnamed effect chain.
Ordinary answer. The runner performed the named Work under the applicable build Method. The named Work-to-change predicate connects that Work to the store-population transformation, and the named change-to-identity predicate says that the transformation made the applicable binary-identity rule become true first at 09:11. Therefore ReleaseBinary_12 first exists at 09:11 through this build Work; decide completion and later uses separately. The table below supplies the exact assurance basis for that answer.
| Needed fact | Exact case fact |
|---|---|
| Work, performer, and method | Applying the common route in section 4.2, A.15.1:6.7.1 first reuses BuildRunner_A : U.System’s A.13 core for this action, including the exact direct assignment species and obtaining occurrence BuildRunnerAssignment_2026-07-21; A.15.1 then independently admits ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work from its performance history, enacted Method ReproducibleBuild@BuildOps-v12, interval 09:00–09:12, and the obtaining BuildWorkOccursWithinServiceBoundary relation to BuildService_A. Because this case claim consumes attribution under that assignment, F.6 then establishes the exact relation. The enacted Method states the intended effect of producing an immutable binary. Method-applicability claim ReproducibleBuildApplies-12 applies that Method to exact build input and configuration BuildInputSet_12. |
| Application and candidate basis | After the produced entity exists, A.6.1 application BuildApplication_12 has result binding builtBinary -> ReleaseBinary_12; that binding designates the returned entity but establishes neither its inception nor its boundary. The same identified application is an application of declared operation storeWrite@BuildOps-v12 and has argument binding storeTarget -> ArtifactStorePartition_12; A.15.1:6.7.1 uses this application and binding in the obtaining test for the named Work-to-transformation predicate below. Before inception, BuildOutputBasis_12 designates the candidate bytes, manifest, digest, and their positions in that partition, not a surrogate future binary. |
| Actual transformation | A.3.4 independently identifies the one transformation consumed here: ArtifactStorePopulationTransformation_12 : U.Transformation, the change of ArtifactStorePartition_12 from no complete candidate tuple at 09:00 to the written bytes, manifest, and digest at 09:11, after which that tuple remains fixed through build completion at 09:12. |
| Work to change | A.15.1:6.7.1’s BuildOps relation specification declares BuildWorkPopulatedStore@BuildOps-v12(work, transformation) with participant order <work, transformation>. Its stated test and the stipulated Work, application, target-binding, and transformation facts make BuildWorkPopulatedStore@BuildOps-v12(ReleaseBinary12_BuildWork_2026-07-21T0900_0912, ArtifactStorePopulationTransformation_12) obtain. Shared timing or the result binding alone would not establish this predicate. |
| Identity criterion and applicability | Predicate-definition episteme ReleaseBinaryIdentitySpec_v12 says that this BuildOps binary exists when one immutable byte sequence, manifest, and digest are fixed together and addressable by that digest in ArtifactStorePartition_12. Applicability claim ReleaseBinaryIdentitySpecApplies-12 applies that episteme to BuildOutputBasis_12, the BuildOps-v12 context, and the ordered candidate boundaries from 09:00 through 09:12. This is the criterion episteme for the selected inception question; BuildCompletionCriterion_v12 belongs to the separate completion question at 09:12. |
| Change to identity | BuildOps predicate-definition episteme ReleaseBinaryIdentityPredicates-v12 declares case-local predicate StorePopulationClosedBinaryIdentity@BuildOps-v12(transformation, identitySpecification, candidateBasis, boundary, producedEntity) with that participant order. Its test requires the governed store change to make the applicable identity rule false at every earlier candidate boundary and true at the named boundary. The stipulated case facts make it obtain for <ArtifactStorePopulationTransformation_12, ReleaseBinaryIdentitySpec_v12, BuildOutputBasis_12, 09:11, ReleaseBinary_12>. |
| Local result | C.2.1 episteme ReleaseBinary12InceptionClaim has exact EntityOfConcern = ReleaseBinary_12 and states only that this entity first exists at 09:11 through the governed effects of ReleaseBinary12_BuildWork_2026-07-21T0900_0912 under ReleaseBinaryIdentitySpec_v12 and ReleaseBinaryIdentitySpecApplies-12. It asserts neither build completion nor verification, transfer, acceptance, release, deployment, publication, or availability. |
Nearest failing variant.
Keep every fact above, including the result binding, store transformation, work-to-change predicate, identity specification, applicability, ordered boundaries, and the state that satisfies the identity rule at 09:11. Remove only the declaration and obtaining fact for StorePopulationClosedBinaryIdentity@BuildOps-v12.
The exact result is missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY] for <ArtifactStorePopulationTransformation_12, ReleaseBinaryIdentitySpec_v12, BuildOutputBasis_12, 09:11, ReleaseBinary_12>. A timestamp, completed write, or builtBinary binding cannot replace that missing change-to-identity predicate.
Author-side replay of the same result. Case substrate ReleaseBinaryInceptionClaims-v1 defines a time-indexed conjunction over the named Work, performer basis, method applicability, the performed storeWrite application fact (not the later result binding), affected referent, transformation, work-to-change predicate, identity specification, applicability claim, and change-to-identity predicate.
Its declared ordered boundary domain is 09:00-09:12, and its earliest-satisfying rule returns 09:11. The positive replay therefore yields ReleaseBinary12InceptionClaim.
In the failing variant, the same constructor lacks exactly the change-to-identity conjunct and returns missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY], exactly as the ordinary replay does. These case-local predicates and this substrate introduce no universal production, work-to-change, or change-to-identity relation kind.