NCR Draft

Purpose

Produce the terminal artifact: NCR + inspection summary rendered from templates/ncr-template.md, populated only from the contract payload.

When to use

After defect-grade whenever graded_defects[] is non-empty; on request for an inspection summary even with zero defects (accept lot).

Inputs

graded.json (contract mfg.quality-inspection.v1, the {graded_defects} hop).

Steps

Validate input against the contract; surface escalations[] - document conflicts (#4.3) and borderline calls (#4.2) go in a visible "Open escalations" block above the disposition.
Fill templates/ncr-template.md: lot identification, nonconformance description with statistics, full characteristic table, grading with rule citations, watch list, draft-first containment actions, CAPA handoff note, contract payload as appendix.
Render to the requested format (markdown by default; other formats via the template).
Mark the document DRAFT - pending QE approval.

Output

NCR-.md - the terminal artifact of the contract flow.

Grounding requirements

Every numeric claim traces to engine:tolerance_check; every grade cites its rule section; certificate conflicts cite the CoC document ID and ISO 9001 8.4.3.

Constraints

Draft-first: no containment is executed and nothing is filed or sent; the draft is a recommendation for the quality engineer.
Nothing appears in the NCR that is not in the contract payload.
Scope ends at the NCR; corrective/preventive action belongs to Quality Incident & CAPA (Wave 2).

ncr-draft