Tables are valuable up to a point. A table with 6–60 cells usually improves comprehension; a table with 300+ cells is usually a maintenance artifact that belongs in generated output or structured data.Documentation Index
Fetch the complete documentation index at: https://mehen.ophi.dev/llms.txt
Use this file to discover all available pages before exploring further.
Per-table burden
Combines wide, long, and cell-count saturation terms with missing-header, empty-cell, and alignment-complexity penalties:Table Scaffolding Score
Uses a piecewise size credit:| Cells | Credit |
|---|---|
| 1–5 | 0.2 — too small to matter. |
| 6–60 | 1.0 — useful comparison scaffold. |
| 61–150 | max(0, 1 − (cells − 60) / 120). |
| > 150 | More burden than scaffold; credit is near zero. |
cells > 300 OR cols > 12 OR rows > 100, with the suggested
remediation: split the table, generate it from structured data, or move the source to YAML/JSON/CSV.
How DMI uses it
Table Burden contributes to DMI via theT_norm term; Table Scaffolding is one
of the components of Good Scaffold.
References
- Tufte, E. R. (2001). The Visual Display of Quantitative Information, 2nd ed. Graphics Press — classic reference on when tables aid comprehension and when they become noise.
- Few, S. (2012). Show Me the Numbers: Designing Tables and Graphs to Enlighten, 2nd ed. Analytics Press — concrete guidance on table sizing and the cell-count thresholds adopted here.
- W3C: Tables Tutorial — Tables in WCAG — defines header-row requirements that the missing-header penalty enforces.
See also
- Visual Scaffold — same idea for diagrams and images.
- Artifact Debt — broader artifact-hygiene metric.