Advisor

Routing Boundary

advisor pulls JUDGMENT in from a different model. It is the inbound half of the cross-runtime pair; handover is the outbound half (it sends mechanical build work OUT to Codex). Keep them distinct:

• Second opinion on a judgment / design fork / decision → advisor (default).
• Adversarial critique of a PREPARED plan → advisor --panel.
• Review a code diff → review.
• Hand unfinished mechanical build work to Codex to DO → handover.
• Sharpen a fuzzy idea by self-interview → grill.

advisor never writes code, never commits, never touches git. It asks another model and returns the outside view; the caller decides. Never auto-incorporate a finding.

Step 0: Locate the seat (zero-config)

Detect the current runtime only to guarantee that the outside opinion comes from a different model family: