Software and test execution packs
Release signed software/test definitions for an exact manufacturing plan and compile immutable build-result packs for independent Quality acceptance.
Screen orientation
Manufacturing read and exact definition/signature/result/review permissions apply with site and classification. Technical, Quality and Production signatures remain separated.
Definition panels freeze software/test manifests and evidence; signature history releases the version. Build result panels compile exact execution evidence and show Quality decisions.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Released manufacturing-plan version | Select | Required. | Choose the exact current released plan. | Pins the definition source fingerprint. |
| Pack title · Controlled scope and authority boundary | Text | Required. | Name the pack and state what it governs. | Freezes the package purpose. |
| Test-result adapter | Select | Required for test evidence. | Choose the bounded adapter supported by the contract. | Defines how exact results are validated. |
| Software manifest · Test manifest | Structured editors | Required according to plan operations. | Record complete exact versions, hashes, procedures, parameters and acceptance limits. | Creates immutable software/test definitions. |
| Signed artifact, procedure and transition evidence | Controlled evidence | Required for release signatures. | Select CLEAN evidence supporting the exact manifest. | Pins definition evidence. |
| Immutable external record prefix | Text | Required when external record identities are compiled. | Use the controlled unique prefix. | Contributes to immutable result identity. |
| Signed result compilation evidence | Controlled evidence | Required for result compilation. | Attach CLEAN evidence for the exact build observations. | Pins the result version. |
| Decision · Attributable signature note · Signature evidence | Signature/review controls | Required at each decision. | Each exact authority records their own authenticated decision and evidence. | Appends an immutable signature/review fact. |
Actions and effects
When to use: For one exact released plan.
What it does: Creates an immutable definition version.
When to use: In the server-required order by distinct actors.
What it does: Releases the exact definition; these are authenticated decisions over hashes, not PKI signatures.
When to use: By the exact executing Production Operator after complete evidence.
What it does: Creates an immutable build-specific result version.
When to use: By a different Quality Inspector.
What it does: Accepts the exact unchanged result; it does not complete product delivery or move stock.
Lists and states
- Definition and build result register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
Execution packs do not command machines, mutate Engineering/Quality sources, move stock/custody, create procurement or post accounting.