# Data-Model-First Releases Reduce Decision Coupling Shipping a narrow data and rendering path lets useful work proceed before interface design, presets, and broader product decisions settle. ## Scope & conditions - This applies when the stored value and rendering behavior are stable enough to support early developer use without locking in the later interface. - The first slice needs a clear compatibility contract; otherwise early adopters build on an accidental shape. - A developer-only phase creates documentation and accessibility obligations even before ordinary users get controls. ## Source anchor > "This release adds the smallest useful piece: the ability to declare a text-shadow value directly in theme.json." <!-- atomicity: 1 idea ✓ --> ## Links - [[3. Resources/Permanent Notes/Default-Off Feature Flags Decouple Shipping Speed From Production Risk]] — extends: both patterns separate landing useful code from exposing a finished interface to every user. - [[3. Resources/Permanent Notes/Core Abilities Must Be Consumer-Neutral Primitives Not One Interface's Mirror]] — applies-in: a stable underlying primitive can ship before one consumer interface defines its final shape. - [[Product & Startup Instincts MOC]] — belongs-in: a smallest-useful-slice release tests the foundation while deferring avoidable decisions. ## Source - [Text Shadow Support in Global Styles](https://make.wordpress.org/core/2026/07/23/text-shadow-support-in-global-styles/) — WordPress 7.1 ships `theme.json` storage and rendering before controls, presets, and block support. Reader doc `01ky7rgwsw4f5qw5q8bre8h2va`.