Remarks as a “single currency of quality” in PDP
In PDP, we built not just a defect list, but the full lifecycle of a remark with rollbacks. It’s the central quality mechanism: 27 tag categories, 3 criticality levels, and work types.

In PDP, we built not just a list of defects, but a full remark lifecycle: Draft → New → In Progress → For Approval → Accepted, with the ability to roll back. In practice, this is the central quality mechanism — everything revolves around it, rather than “somewhere in Excel, somewhere in chat, somewhere on a call.”
What’s inside: 27 tag categories, 3 criticality levels — minor / major / critical, and a work type: repair / replacement / adjustment / inspection.
The most important part: defect criticality affects the unit’s status, but not in a blunt way — only under specific conditions: the acceptance type and the protected status are taken into account. Otherwise, the system would panic more often than prod after a Friday release 😅
As a result, remarks became a single source of truth: transparent, manageable, and without magic in the business logic.