Explains what existing code does, in plain language, at the level a reader needs.
Reads unfamiliar code and explains it. In most organisations the higher-value half of coding assistance, because more time goes into understanding existing systems than writing new ones.
Undocumented legacy code, onboarding, and inherited logic that people are afraid to change because nobody knows what it does.
As the sole basis for a change to critical logic. An explanation that is right about the common path and wrong about the exception is the normal failure.
Where the explanation informs a change to control-bearing logic, it must be verified against behaviour rather than accepted as description.
Confidently describing intent rather than behaviour — explaining what the code appears meant to do, not what it does, particularly around nulls and boundary conditions.
Explaining an inherited stored procedure implementing match tolerances, so the team can judge whether its behaviour still matches policy.
Two different absences share this shape. Foundational solutions get built whatever the domain, so no domain links them; the rest are solutions this domain genuinely does not reach for. v_ai_solutions_unlinked separates the two.