MES evidence adapters
Release an ingest-only evidence profile for one exact automated test/acceptance target, retain immutable external receipts and require independent Quality acceptance before single use.
Screen orientation
MES evidence permissions, exact site and classification apply. Manufacturing author, Product Engineering, Security, Production release, operator importer and Quality verifier are separated.
Profile definition and ordered reviews release the exact binding. Receipt panels ingest a canonical payload for an eligible target and show Quality review and downstream consumption state.
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 |
|---|---|---|---|---|
| Profile title · Purpose and authority boundary | Text | Required. | Name the profile and state its evidence-only purpose. | Freezes the definition context. |
| External system · Controlled system reference | Text | Required. | Identify the named source system without storing connector credentials. | Pins source identity. |
| Transport | Select | Required. | Choose the bounded named-user JSON API or signed-file ingestion method. | Defines accepted ingress evidence. |
| Adapter definition evidence | Controlled evidence | Required. | Select CLEAN evidence for the fixed contract mapping. | Pins profile evidence. |
| Exact target | Select | Required for receipt ingestion. | Choose one eligible exact build test or acceptance phase matching the released profile. | Pins receipt destination. |
| Immutable external record ID · Observed at | Text/date-time | Required and unique per profile version. | Use the exact external identity and observation time. | Creates replay protection and chronology. |
| Immutable receipt evidence | Controlled evidence | Required. | Attach CLEAN evidence supporting the canonical payload. | Pins the immutable receipt. |
| Decision · Attributable note · Decision evidence | Quality review controls | Required. | A different Quality Inspector accepts only an unchanged PASS receipt. | Creates the immutable receipt review. |
Actions and effects
When to use: For one exact current released automated target.
What it does: Creates an immutable INGEST_ONLY / MES_EVIDENCE_JSON_V1 definition.
When to use: By distinct Product Engineering, Security and Production actors.
What it does: Releases the exact unchanged profile.
When to use: By Production Operator for an eligible exact target.
What it does: Stores source/payload/receipt hashes; it sends no outbound command.
When to use: By a different Quality Inspector.
What it does: Accepts a PASS receipt for atomic single use by the exact downstream result.
Lists and states
- Adapter profile and receipt 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
Direction is fixed to ingest-only. The surface has no callback, credential store, arbitrary mapping, outbound command, machine/safety, message, delivery, source, stock, custody, identity or finance authority.