41. Governed visual work instructions and execution observations
Add exact controlled visual guidance and attributable human observations to released manufacturing execution without creating another execution, workflow, machine-control, stock or custody authority.
Purpose
Add exact controlled visual guidance and attributable human observations to released manufacturing execution without creating another execution, workflow, machine-control, stock or custody authority.
Manufacturing Engineer, different Production Manager, Production Planner, different Production Supervisor, exact named Production Operator, different Quality Inspector and read-only Auditor
MWI-… v1 rejected → immutable v2 released against MPL-… / operation 20 → MDP-… pins v2 → operator step 10 acknowledgement → step 20 Quality hold accepted → run COMPLETE → existing operation PASS.
Before you begin
- The exact manufacturing plan is current, RELEASED and APPROVED
- Every media item is a same-site CLEAN immutable PHOTO, VIDEO or DRAWING document version within the plan classification
- Manufacturing Engineer and Production Manager are different named users
- A fresh Flow 28 dispatch is planned only after the required instruction version is released
- The exact assigned Production Operator and a separate Quality Inspector are active, scoped and cleared
Version pinning, media and authority boundaries
A package binds one current released plan version and either the whole-plan start or one exact operation copied into that version. No arbitrary object, URL or template target is accepted.
IMAGE accepts CLEAN PHOTO JPEG/PNG/WebP; VIDEO accepts CLEAN VIDEO MP4/WebM; DRAWING accepts CLEAN DRAWING PDF/image. The package fingerprints exact document-version identity, SHA-256, type, MIME, classification and caption.
Title, purpose, ordered steps, inert instruction text, acknowledgement/evidence flags, hold points and media snapshots form one SHA-256 definition. Rejection and later replacement never edit an earlier version.
A released version remains active while its replacement is drafted or rejected. Approval supersedes it for future dispatches; already pinned dispatch requirements never change.
The existing Production Planner dispatch transaction pins the active plan-start package only on the first operation and the active exact-operation package on that operation. A legacy or ungoverned target creates zero requirements and executes unchanged.
Only the exact assigned operator on a currently RELEASED, live-ready dispatch may start/continue the run. Steps are single-record, immutable and strictly ordered; required acknowledgement and evidence fail closed.
A QUALITY step stops the run. A different Quality Inspector—separate from package, planning, release and operator actors—accepts it to continue or rejects the run. A rejected run cannot unlock operation execution.
Flow 37 does not execute manufacturing. The established Flow 27/28 endpoint merely verifies that every requirement pinned to its exact dispatch is COMPLETE before recording its normal immutable operation attempt.
There are no external URLs, scripts, executable attachments, callbacks, machine commands, SQL, tenant JavaScript, generic workflow/template administration or customer-specific forks. No route changes receipt, quarantine, inspection, custody, current stock, stock ledger, Assembly, configuration or notification state.
Procedure
- 1
Upload controlled PHOTO, VIDEO or DRAWING evidence in Documents and wait for CLEAN malware state.
- 2
Create package v1 against the exact current released plan or operation, add unique ordered steps and attach exact media versions, then submit with controlled evidence.
- 3
Reject v1 as a different Production Manager, retain it, create v2 and approve only unchanged plan-source and definition fingerprints.
- 4
Plan a fresh Flow 28 dispatch and inspect its pinned requirement/version. Replace the package later and confirm the existing dispatch remains pinned while a new dispatch receives the replacement.
- 5
As the exact named operator, open each controlled media preview, acknowledge and record observations in order. Attach evidence when required and stop at declared Quality holds.
- 6
Accept or reject each pending hold as a different Quality Inspector. After all pinned runs complete, record the existing operation and reconcile audit/outbox plus unchanged source, custody, stock, ledger, Assembly, machine, workflow and notification witnesses.
Expected result
- Package lifecycle retains DRAFT → SUBMITTED → RELEASED/REJECTED immutable versions and active-version replacement
- Only current released plan/operation targets and same-site within-classification CLEAN media are accepted
- Author cannot release their own version
- Fresh dispatches pin exact version/fingerprint while older dispatches stay immutable
- Only the assigned live-ready operator records unique ordered observations
- Acknowledgement and execution-evidence requirements fail closed
- Quality holds require an independent inspector and rejection prevents operation execution
- Legacy dispatches with zero requirements continue through the existing path
- Operation execution remains the sole established Flow 27/28 transaction
- Flow 37 changes no receipt, quarantine, inspection, custody, stock, ledger, Assembly, source, machine, workflow or notification state