React Component Governance

Make consistent React component architecture decisions without drifting into ad hoc local conventions.

Workflow

Inspect the immediate UI question and its surrounding React architecture. Read references/workflow.md and references/extraction.md first. Check whether the local problem is isolated or reveals recurring boundary confusion, missing packaging or ownership convention, duplicated behavior, or a misplaced responsibility.
Surface a meaningful React architecture choice before editing. When both a local answer and a materially different, evidence-backed wider React architecture option are credible, explain both, recommend one, and wait for the user's choice unless the user already expressed a preference or delegated the decision. Do not manufacture a wider option from unrelated cleanup.
Decide whether a meaningful boundary should exist at all. Choose whether UI should stay inline, become a local helper, become a component boundary, or become another boundary kind.
Decide what kind of boundary the extraction creates. If the result is a component boundary, read references/classification.md to classify it as presentational, interactive, or container. If the result is a headless behavior boundary, provider/infrastructure boundary, or support boundary, keep that boundary kind explicit and do not force a component role onto it.