| 1 | # Red-note Structural Self-check |
| 2 | |
| 3 | ## P0 - Not Deliverable |
| 4 | |
| 5 | - Content exceeds the note canvas or is clipped. |
| 6 | - Text-bearing modules use absolute/fixed positioning instead of grid/flex flow. |
| 7 | - Body text is below 18px, headings below 24px, or auxiliary text below 12px. |
| 8 | - The page lacks a clear hook. |
| 9 | - The value body is not readable as a saveable note. |
| 10 | |
| 11 | ## P1 - Should Fix |
| 12 | |
| 13 | - The hook does not give a clear stop reason. |
| 14 | - The body has too many ungrouped points. |
| 15 | - The note lacks a bottom takeaway, action, summary, warning, or source. |
| 16 | - A checklist/step guide uses paragraphs instead of concise rows. |
| 17 | - A data note lacks nearby interpretation. |
| 18 | - A template note hides the reusable structure in prose. |
| 19 | |
| 20 | ## P2 - Consider Optimizing |
| 21 | |
| 22 | - The hook could be more concrete as a benefit, question, number, or claim. |
| 23 | - Rows can be grouped under 2-4 section labels. |
| 24 | - A framework can use fewer facets with stronger labels. |
| 25 | - Source/footer text could be simplified into one auxiliary line. |
| 26 |