Prototype operating model

bloom-design-ops is Bloom’s design operations workbench. Prototype routes are interactive design references for product feel, hierarchy, motion, and flow. They are not production app implementation by default.

Statuses

• Exploration — direction is being tried; do not implement from it.
• Hypothesis variant — a testable version linked to a product/design question.
• Selected direction — preferred direction, not yet dev ready.
• Promoted — reviewed and moved into Figma, UI kit, Storybook, or app handoff.
• Prototype-only — useful reference that should not become production scope.
• Superseded — replaced by a newer direction.

Promotion rule

Prototype code becomes implementation input only after a promotion packet names the selected version, reviewed design trail, required states, responsive behavior, component source, known deviations, non-goals, and QA expectations.

Until then, product implementation should use the approved production UI kit package unless Bloom records an explicit exception or migration decision.