Workflow

Flow 32 — Signed software/test definition to accepted execution results

Bind exact baseline software identities, signed artifact hashes, test procedures, adapters and parameters to a released routing; require three independent definition signatures; then compile exact passing executions for separate Quality acceptance before as-built capture.

Overview

Inventory meaning

Flow 32 creates immutable definition, signature and result evidence only. It never issues a machine command, changes a safety interlock, edits Engineering or Quality sources, posts accounting, or reserves, consumes, moves or reclassifies stock/custody.

Responsible roles

Manufacturing Engineer author → different Product Engineer technical signer → different Quality Engineer quality signer → different Production Manager releaser → exact executing Production Operator result compiler → different Quality Inspector result acceptor → different Quality Inspector as-built reviewer

Process

1
Freeze manifest
Map every exact baseline software/firmware CI to one released software-load operation and artifact hash.
Engineering read-only
2
Freeze tests
Bind every inspection/test operation to a CLEAN procedure, adapter and exact acceptance parameters.
Quality source read-only
3
Sign definition
Product Engineering, Quality and Production make three attributable decisions on unchanged fingerprints.
No machine command
4
Execute & compile
Exact operator records released version/hash or parameters, then compiles latest passing controlled executions.
Evidence only
5
Accept & gate
Different Quality Inspector accepts unchanged results before as-built; its reviewer cannot perform downstream Quality review.
Read-only gate
READ ONLY

Role handoff

Detailed reference chapters

Signed software/test execution and result packs Manufacturing plan, execution evidence and authoritative as-built Controlled manufacturing BOM hand-off Product configuration and released baselines Controlled documents and evidence roles

Detailed steps

1
As Manufacturing Engineer, open Manufacturing → Software & test packs and select one current released plan whose routing has exactly one software-load operation per released baseline software/firmware CI and at least one inspection/test operation.
2
Bind each software entry to its exact configuration item, CLEAN artifact document, target and verification method; bind each inspection/test to its CLEAN procedure, manual/automated JSON adapter and unique objective parameter set.
3
Submit v1, reject it as a different Product Engineer and retain it. Create v2, obtain a Product Engineer technical signature, different Quality Engineer signature and third Production Manager release on unchanged source/definition fingerprints.
4
Schedule only after release. As the exact dispatched operator, record software version plus exact artifact SHA-256 or complete exact released test parameters. The adapter ingests evidence and cannot issue equipment or safety commands.
5
After all routing operations pass, compile exact controlled executions into result v1, submit and reject it as a different Quality Inspector. Replace with v2 and accept only unchanged source/result fingerprints.
6
Confirm as-built capture was blocked before result acceptance and requires a different named Quality reviewer from the result acceptor. Reconcile unchanged Engineering, Quality-source, machine, stock, custody, Assembly, identity and accounting witnesses.

Field-by-field practice data

Use a disposable training tenant

Create a signed software/test execution pack for one released manufacturing plan. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Manufacturing Engineer

Author the execution pack

Open /manufacturing/execution-packs

Select the released plan and pin manifests plus adapter definition before separate technical and Quality signatures.

Exact field name	Requirement	Sample value A	How to use it
Released manufacturing-plan version	Select existing	`TRAIN-A-MPL-001 v1`	Select the exact current released plan.
Pack title	Required	`TRAIN-A actuator software and functional test pack`	Use a unique controlled title.
Controlled scope and authority boundary	Required	`Software load and bench functional test only; no machine command or stock authority.`	State the explicit boundary.
Test-result adapter	Required	`TRAIN-ADAPTER-JSON-V1`	Use the approved bounded adapter.
Software manifest	Required	`TRAIN-A-SW-001 · sha256:example`	List exact signed artifacts and hashes.
Test manifest	Required	`TRAIN-A-TEST-001 · procedure TRN-TP-01`	List exact procedures and expected evidence.
Signed artifact, procedure and transition evidence	Select existing	`TRAIN-A-EXEC-EVID-001`	Select CLEAN controlled evidence.
Immutable external record prefix	Required	`TRAIN-A-RESULT`	Prefix must not collide with prior receipts.

Expected result: Compiled results remain immutable and require independent Quality acceptance.

End state

One released definition pack and one independently accepted build-result pack prove the exact signed artifact/procedure/adapter path through immutable executions before as-built, without acquiring machine, source, stock, custody or financial authority.