Verify request lifecycle map
You're new to a 200k-line Python monolith and ask an AI agent to map the request lifecycle so you can safely move authentication into middleware. The agent produces a clean call graph and concludes "auth happens only in the decorator @require_login on each view, so centralizing it in middleware is a safe, mechanical move." What do you do before you trust that map and start the refactor?
Implement
find_unmapped_auth_sites(source_lines: list[str], claimed_sites: list[str]) → list[str]Examples
in
[["views/orders.py|@require_login","views/orders.py|def list_orders(request):","core/base_viewset.py|if not request.user.is_authenticated:","middleware/legacy.py|check_auth(request)"],["views/orders.py"]]out["core/base_viewset.py","middleware/legacy.py"]in
[["views/home.py|return render(request)"],[]]out[]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 20 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.