cms-decision-rules

To choose between Supabase and Sanity, map your client brief archetype and content signals to a cmsMode. The decision tree constrains outputs to none, sanity, sanity-plus-supabase, or supabase-only based on specific content model requirements.

For app_lite, brochure, and editable_brochure archetypes, the CMS decision applies specific decision tree rules (cms-001 through cms-004) to derive the correct cmsMode and contentModel from your editor profiles and content signals.

Mapping editorial workflow requirements to a CMS plan translates client brief inputs into a structured cmsPlan. This includes studio deployment, editor seats, preview configurations, and migration guidance based on archetype and content signals.

Yes, supabase-only is a valid cmsMode output for editable_brochure archetypes. The decision tree evaluates your specific content signals and editor profiles to determine if supabase-only is appropriate or if sanity-plus-supabase is required.

A CMS refusals matrix is required during site planning to record explicit governance constraints and open questions. It ensures auditable CMS choices by documenting when certain cmsMode or contentModel configurations are rejected by the decision tree.

The limitation of using a decision tree for content model selection is that it constrains outputs strictly to rules cms-001 through cms-004. Any ambiguous archetype signals or missing editor profiles will result in open questions rather than a forced cmsMode.