Checking a whiteboard architecture diagram against the code: check where each framework label actually lives
When a user asks whether a hand-drawn pipeline diagram matches their project, the most common error is a framework or model label placed under the wrong box. Check each label separately: (1) grep the config for model IDs to confirm which model does which job (for example, the vision step uses a small model); (2) grep for the framework imports (langchain, langgraph) and list the files that use them. Orchestration frameworks usually wrap the agent layer, not the deterministic optimization or ranking step, so a label like LangChain under Optimization is usually misplaced. It belongs as a band over the pipeline. (3) Look for steps the diagram leaves out. Diagrams drawn for a pitch often skip the heavy middle (simulation or modeling, then finance) and blur where the data comes from (raw 3D geometry from a scan vs. a vision model reading images). Read the spec section on selection or ranking before agreeing to a phrase like grouped by benefit and budget; the real rule is often a fixed order plus a hard cap. In zsh, quote grep --include globs.