orchestrate-input-tracinglisted

# Orchestrate: Input Tracing **Source**: *The Engineer's Notebook*, "Getting better at HackerRank Orchestrate" (Shloka Shah) — the article's recommended self-check framework for verifying a layered agent architecture actually works as designed: pick one input and trace it through the entire system, checking where each stage occurs. ## Why tracing beats reading your own architecture diagram The article's recommended architecture separates concerns explicitly — input loading & normalization, context building, LLM invocation, response parsing & validation, schema enforcement, retry/error handling, fallback/escalation. It's easy to *draw* that separation and never actually confirm each stage exists as a distinct, checkable step in the running code. Tracing forces the confirmation: pick one real ticket/claim, and for each stage, answer "what did this stage receive, what did it do, what did it hand to the next stage" — concretely, not from memory of what you intended to build. ## The practice 1. Pick one representative input — not a trivial one, one with some real complexity (references multiple corpus documents, or has ambiguous phrasing). 2. At **input loading**: confirm exactly what fields were extracted and normalized. Print or log the parsed representation. 3. At **context building**: confirm exactly which corpus documents/images were retrieved for this input, and why — not just "context was built," but the actual retrieved content. 4. At **LLM invocation**: confirm the a