vibeflow-case-dict

A case dictionary is a solver-neutral structured definition that consolidates physical problems, geometry, materials, mesh, execution, and reporting into a single source of truth for safe handoffs between workflow components and backend solvers.

You elicit user requirements and map them into a solver-neutral case dictionary by initializing intent, geometry, materials, and mesh sections from a user brief to capture assumptions, decisions, and artifacts in one structured definition.

A case dictionary manages stage gates by guiding workflow steps from intent through geometry, mesh, run, post-processing, and reporting, documenting clear handoff criteria and open questions before proceeding to downstream stages.

Yes, a case dictionary links geometry, materials, regions, boundaries, and artifacts for reproducibility and auditing, satisfying requirements for structured field definitions, provenance tracking, validation rules, and error handling.

The best way is to consolidate intent, assumptions, decisions, open questions, and artifacts into a unified case representation, enabling teams to align on next actions before proceeding to downstream execution stages.

You need a single source of truth to ensure safe handoffs between workflow components and backend solvers, maintaining traceability and reproducibility across the entire simulation lifecycle from intent through reporting.