21. Suspect-counterfeit evidence and joint decision
Govern one S1 suspect identity through preservation, authenticity investigation, cross-product impact, QA proposal and Security concurrence without silently granting Quality stock, supplier-return or notification-delivery authority.
Purpose
Govern one S1 suspect identity through preservation, authenticity investigation, cross-product impact, QA proposal and Security concurrence without silently granting Quality stock, supplier-return or notification-delivery authority.
Quality Inspector, different QA Head, separate Quality Engineer, independent Security & Compliance Officer, Supplier Quality/Procurement/Auditor read-only
NCR-E2E-CF-001 → CF-E2E-001 → seal SEAL-CF-001 → investigation v1 → QA proposal v1 rejected → immutable QA proposal v2 concurred → held-custody closure HOLD-CF-001.
Before you begin
- The parent NCR is S1, contained, supplier/product-safety classified and linked to one exact stock identity
- The exact identity and quantity already exist in BLOCKED or MRB_HOLD at the NCR site
- Supplier, item, ownership and CAGE/provenance references are known
- Inspector, QA Head, Quality Engineer and Security Officer are separate eligible users
- At least one ACTIVE, CLEAN controlled evidence version exists at the same site
Counterfeit authority boundaries
Only a contained S1 supplier or product-safety NCR against exact STOCK_IDENTITY data can create one dedicated case. Ordinary defects remain in Flow 13.
Item, location, BLOCKED/MRB_HOLD state, ownership, batch, serial or container and quantity are snapshotted from the NCR and revalidated at preservation, investigation and closure.
Seal, controlled location, preservation method, chain of custody and CLEAN evidence are mandatory before QA may assign an investigator. This records a control fact; it does not move stock.
The assigned Quality Engineer records methods, provenance, markings, tests, custody findings, recommendation and traceability impact, plus searchable batch/serial/container/product/project/shipment links.
A different QA Head proposes confirmed, not-counterfeit or inconclusive outcome with recurrence controls and a custody recommendation. Confirmed/inconclusive material cannot request release review.
A separate Security Officer assesses provenance, chain of custody, cross-programme/installed impact and notification need. Rejection preserves the proposal version and returns to QA; concurrence advances to DECIDED.
QA closure requires a concurred current proposal, any required notification reference, retained-custody/follow-up authority and CLEAN evidence. The exact suspect identity must still be held.
The workflow records notification references but sends no message. It never authorises supplier return and never changes vendor approval or screening.
An open suspect-counterfeit case blocks parent-NCR closure. Closing the suspect case does not close the NCR or execute an MRB decision.
Supplier Quality, Buyer, Procurement Manager and Auditor can inspect the evidence and impact chain but have no counterfeit mutation authority.
Procedure
- 1
Raise and contain one exact S1 stock-identity NCR as Quality Inspector.
- 2
Raise the dedicated suspect case and preserve seal/custody evidence while stock remains held.
- 3
Have a different QA Head assign a separate Quality Engineer.
- 4
Submit the evidence-backed authenticity investigation and searchable impact links as the assigned engineer.
- 5
Have QA propose outcome v1, Security reject it, QA propose immutable v2 and Security independently concur.
- 6
Close as QA with custody and notification references while the exact identity remains held.
- 7
As read-only stakeholders, reconcile actor separation, decision versions, evidence/audit/outbox and unchanged supplier/inventory state.
Expected result
- Lifecycle follows SUSPECT → EVIDENCE_PRESERVED → INVESTIGATION → DECISION_PENDING → SECURITY_CONCURRENCE → DECIDED → CLOSED
- Inspector, investigator, QA and Security permissions remain distinct
- Originator cannot investigate; investigator cannot propose; QA proposer cannot provide Security concurrence
- Rejected QA proposals remain immutable and the next proposal advances the version
- Every preservation, investigation, QA proposal, Security review and closure links exact CLEAN evidence
- At least one searchable cross-impact link is retained
- Confirmed or inconclusive suspect material cannot be recommended for release review
- Required notification reference blocks closure, but Moduvio sends no external message in this flow
- Open counterfeit case prevents premature parent-NCR closure
- Exact suspect stock remains BLOCKED/MRB_HOLD and current_stock/stock_ledger totals do not change