Decision D17 · 17 of 21
NAMUR OA / NE 178 adoption depth
Pattern-level Verification of Request
RECOMMENDED
- Status
- RECOMMENDED — awaiting Vinayak
- Options
- Pattern-level Verification of Request in Stamped contracts only; or align information models with NE 176 and security gateway NE 177; or pursue formal VoR compliance later
- Trade-offs
- Speed to first safe write vs standards alignment
- Recommendation
- Pattern-level Verification of Request inside Stamped contracts (WriteRequest status flow: authenticate, authorise, verify, map, accept, read back). No claim of NE 178 compliance. NE 176 and NE 177 alignment is later, triggered by a customer that runs NOA.
- Why
- Gets the safe write pattern without a standards programme before the first write.
- Evidence
- C34; section 7.2.
- Reversible
- Yes. Deeper alignment adds fields.
- Blocks
- WriteRequest contract, writer.
Page history: last 2 changes
- docs(research): retire stale research to archive/research-2026-10 with a register
ab84821 - docs(technical): split decision board into DECISIONS.md
b4db9d4