Research

Evidence, references, and investigation notes.

Repo Context

• The workstream currently lives at the stable slug graph-library, but the display name should move to chart library because graphs are only one subset of charts.
• The chart rendering design philosophy already separates data, encoding, structure, and theme in dataface/core/render/chart/DESIGN.md.
• M2 and later milestones already assume deeper work around visual language lock-in, quality standards, and adoption hardening, so M1 should stay focused on foundation rather than trying to solve polish and launch concerns early.

Planning Implication

Because later milestones already cover quality standards, adoption hardening, and launch scope, M1 should avoid overreaching into "full design system maturity." The right job for M1 is to create the first reusable corpus: chart types, style packages, evaluation loop, design exploration, and dashboard composition patterns.