Adherence report - backend technical implementation plan

Problem to solve

With the design for the adherence report in the final stages here 🎨 UX theme: Design for Adherence report (#398212 - closed) we need an implementation plan on how to implement this, especially in the backend.

Some questions that need to be considered:

• How will we verify standards? (most seem to be based off projects settings, some form os async validation on project save?)
• Where/how will we store the validations? (utilise current audit event system? new database table? schema?)
• Where/how will we store the standards? (new database table? schema?)
• Where/how will we store the standards configurations per group/project? (new database table? schema?)
• APIs required to allow frontend to interact with the above?

Outcomes

An architectural plan that is broken down into issues to begin work on in %16.1

Proposal