A.15.1:6.7.1 - Filled result route: build, verify, transfer, accept
BuildRunnerAssignment is a directly declared species whose signature uses the local BuildRunnerSystemRole domain. The fixture declares BuildRunnerSystemRole as a local agential kind, gives its build-action membership criterion, classifies BuildRunner_A : U.System under it, and cites evidence that the System satisfies that local criterion for the scope and window; no Grade or autonomy-profile claim is used. BuildRunnerAssignment_2026-07-21 is its obtaining occurrence, with that System as holder and an extent covering 09:00–09:12. The exact action history, Method, extent, and BuildWorkOccursWithinServiceBoundary fact first admit ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work. F.6 then separately states that BuildRunner_A performed that Work under the same assignment. Those facts establish distinct Work and attribution results. The rows below add only the result and consequence claims that are current in this case. Every additional verification, evaluation, or acceptance Work named in a row needs its own A.15.1 admission basis; any precise assignment-bound attribution for it needs its own later F.6 check. It does not inherit BuildRunner_A or the build assignment.
| Current case claim | Exact object or relation | Kept separate from |
|---|---|---|
| build application returned the binary | A.6.1 application BuildApplication_12 of declared operation storeWrite@BuildOps-v12, with argument binding storeTarget -> ArtifactStorePartition_12 and result binding builtBinary -> ReleaseBinary_12 | entity inception, production completion, delivery, acceptance |
| subject practice also needs a direct result relation | case-local occurrence BuildRunReturnedBinary_12 under already declared predicate BuildRunReturnedBinary@BuildOps-v12, relating the build Work to ReleaseBinary_12; if that declaration were absent, this row would be omitted and the A.6.1 binding retained | a universal WorkResultRelation |
| the artifact-store partition changed | A.3.4 identifies ArtifactStorePopulationTransformation_12. BuildOps relation specification BuildOpsWorkChangeRelations-v12 declares the direct predicate BuildWorkPopulatedStore@BuildOps-v12(work, transformation) with participant order <work, transformation>. Its test requires the named Work to be the performed process that, through exact storeWrite@BuildOps-v12 application BuildApplication_12 and its storeTarget -> ArtifactStorePartition_12 binding, brings about the independently identified population transformation of that same partition. The stipulated Work, application, target binding, and transformation facts make the predicate obtain for ReleaseBinary12_BuildWork_2026-07-21T0900_0912 and ArtifactStorePopulationTransformation_12; C.2.1 assertion BuildWorkPopulatedStore-12 states that positive claim | the application remains an independently identified occurrence used by the predicate test; shared time, artifact label, or returned binary cannot establish the direct W-to-T claim |
| this was production, the binary first existed, and production completed | three separate A.15.PROD local claims: whole-production-work participation for the build Work; inception of ReleaseBinary_12 at 09:11 under ReleaseBinaryIdentitySpec_v12; completion at 09:12 under BuildCompletionCriterion_v12 | one omnibus production/result record |
verification returned pass | separate ReleaseBinary12_VerificationWork_2026-07-21T0913_0918 : U.Work, A.6.1 application VerifyApplication_12, result binding verdict -> pass, and C.2.1 episteme BinaryVerificationResult_12 when the durable verdict claim is needed | acceptance and the build Work’s result binding |
| checksums and test logs support that verdict claim | A.10 account citing evidence-provenance relation BinaryVerificationEvidenceUse_12, bounded to the verification claim and staging decision | truth by carrier presence or acceptance |
| the binary moved to staging | relation occurrence ArtifactTransferToStaging_12 under declared predicate ArtifactTransferredToStaging@BuildOps-v12, with participants ReleaseBinary_12 and StagingSystem_A, establishes this transfer | production, verification, acceptance |
| staging accepted the binary | StagingAcceptanceWork_12, StagingAcceptanceCriterion_v12, and its returned verdict remain available, but this fixture declares no acceptance predicate relating that verdict to ReleaseBinary_12; return missing-governor[STAGING-ACCEPTANCE] and do not assert acceptance | transfer, evidence, or a bare pass value cannot fill the missing relation |
The readable report is therefore: the build Work occurred; a different entity was returned and produced; BuildWorkPopulatedStore-12 states the positive local W-to-T claim; separate verification Work returned a verdict supported by evidence; and the entity was transferred to staging (ArtifactTransferToStaging_12). Acceptance remains at missing-governor[STAGING-ACCEPTANCE]. Removing any non-current row does not alter the identity of the build Work.