This catalog describes interpretation coverage, not which resources are included in your architecture. Managed and data instances present in a supported plan or state remain represented in the Form even when no selected Dialect or Rule interprets them. Rootform does not invent a classification, Context or Relation for them.
Presence in the Form does not imply a permanent card in every Explorer scene. How Rootform works explains the distinction; Explorer navigation shows how to inspect secondary resources.
Find your provider binding, then open its Dialect. A Dialect can bind more than one provider. A binding does not imply complete provider coverage; each constraint describes declared compatibility, not evidence that every provider version was tested. Rootform does not use an observed exact provider version to choose a Rule.
Dialect pages distinguish local vocabulary declarations, RF Vocabulary references and Rule behavior. Declared emissions and composition describe what a Rule can establish; each input must supply the evidence. Resource and data populations, conditions and independent composition members remain distinct. Presentation mappings supply visual identities, not architectural facts.
Plan JSON, state JSON and saved Forms are limited to 128 MiB per input. Rootform refuses an oversized input before loading the entire file. The language limits apply separately to authored and compiled definitions.
Choose an input covers accepted exports. Plans and saved plans covers pairing and reference evidence. Select Dialects covers local and OCI selections; this catalog describes the official embedded sources.