What problem does it solve? In a multi-agent Databricks SDLC pipeline, validated requirements must be translated into a structured Business Understanding Document before downstream agents can discover metadata, build mappings, or write code. Doing this manually is slow and inconsistent, and ad-hoc LLM calls produce outputs that break the orchestrator's contract validation. ## Core Features & Use Cases - Business Understanding Generation: Articulates the business objective, current-state vs future-state process, business rules, KPIs, risks, assumptions, and deliverables from a validated requirement. - Contract-Compliant Output: Returns JSON matching a strict output contract (status, artifact_path, summary, citations, tool_calls, tokens) that the LangGraph supervisor validates before handoff. - Databricks Tool Integration: Calls the Foundation Model API for synthesis and the Genie Agents Conversation API for natural-language business-metric questions, with citations recorded. - Use Case: A Jira ticket flows through Agents 1-2 and arrives as a validated requirement; this agent reads it from the Unity Catalog volume, produces business_understanding.md/json, writes it to /Volumes/{catalog}/state/artifacts/{ticket}/, and logs the run to state.agent_runs. ## Quick Start Hand this agent a validated requirement from the upstream pipeline and ask it to produce the Business Understanding Document for the ticket.