Self-Contained Report Systems Need Format-Distinction Accountability, Not Theme Tokens Alone
A design system can look mature because it has palette tokens, samples, and many format names. Those assets are necessary but not enough. If every output shares the same frame, a dashboard, data register, research paper, and long-form report collapse into one reskinned document. This workspace-grounded conceptual synthesis studies the html_report_design repository through its README, DESIGN.md, format router, foundation contract, data-driven contract, data-register, dashboard, long-form, research-paper, and icon specifications, then compares the design with HTML data-block, JSON Schema, and WCAG sources. The contribution is a format-distinction accountability ledger with seven stages: shared DNA, format router, schema contract, template shell, interaction contract, icon law, and sample coverage. The inspected workspace includes 35 sample HTML files, 39 design-spec files, and 862 icon-related files. The conclusion is that report design systems should report format distinction and interaction evidence, not only theme tokens.
Introduction
Dense institutional report systems need a shared identity, but shared identity can become sameness. The inspected workspace defines brand-neutral HTML reports with dense 13px typography, themeable palettes, rounded panels, bespoke icons, self-contained output, and structurally different document formats [[cite:designReadme,designMd]].
This paper asks how to distinguish a real multi-format design system from one frame with many names. The answer is a format-distinction ledger that records not only theme tokens but also document type, data schema, interaction, icon law, and sample coverage.
Method
The study mode is workspace-grounded conceptual synthesis. I inspected the design-system README, DESIGN.md, format router, foundation contract, data-driven contract, selected format specs, icon README, and icon SPEC. External sources bound the HTML data-block, JSON Schema, and accessibility claims [[cite:whatwgHtml,jsonSchema,wcag]].
Local descriptive counts are used only as checkout facts: the sample directory contains 35 sample HTML files, the designs directory contains 39 design-spec files, and the icons directory contains 862 files in the inspected workspace.
Results
The first result is that the repository has a strong shared DNA but also explicit anti-collapse rules. The foundation contract requires self-contained HTML, system fonts, theme swaps, print friendliness, and a distinctness mandate; the router says a reader should identify the document type at a glance [[cite:foundation,formatsReadme]].
The second result is that data-driven rendering and icon law are first-class controls. The data-driven contract puts content in a report-data JSON block and requires real controls on visuals, while the icon spec mandates currentColor, a 24-grid, a single-colour law, and a ban list against generic AI iconography [[cite:dataDriven,iconsSpec]].
Discussion
The ledger reframes design-system quality from colour consistency to document-type accountability. A data register must be a table application; a dashboard must be a console; a long-form report must be a reading document; a research paper must carry academic apparatus. If those claims are not separately evidenced, the system has naming variety but not format variety.
External standards support the same split. HTML data blocks make a JSON content source feasible, JSON Schema makes format-specific field contracts auditable, and WCAG reminds that interactive filters, toggles, and nav controls introduce focus and keyboard obligations [[cite:whatwgHtml,jsonSchema,wcag]].
Limitations
This paper did not visually audit every sample or run accessibility tooling. It reports design-governance evidence from specs and local file counts.
A stronger follow-up would compare screenshots across all 35 samples and score whether each format remains visually distinct under all nine themes.
Conclusion
Self-contained report systems need format-distinction accountability, not theme tokens alone. The inspected repository has strong ingredients: a shared DNA, explicit format router, data-driven contract, schema policy, distinct format chrome, icon law, and sample coverage. The next maturity step is a visible coverage matrix for every format's schema, sample, interactions, print behavior, icon usage, and accessibility checks.