visual-critic

Topics in the source

• Visual Critic (orchestrator)
• Purpose
• When to invoke
• Inputs
• Required intermediate representation
• Procedure
• Rubric (100 pts; soft ranking only — hard gates are pass/fail and override)
• Hard constraints

Drive the whole reasoning sequence and adjudicate the result. The critic decides which skills to invoke and in what order, holds the shared artifact state, applies the failure taxonomy and the scoring rubric, and owns the final SHIP decision. It is the single place where the hard-vs-soft discipline (QA-01) is enforced across skills. For any nontrivial "make me a good visualization of X" request (end-to-end mode). To review, grade, or repair an existing figure/slide/diagram (critique mode). The user request and data, plus medium/audience if known. In critique mode, the existing artifact (rendered) to evaluate. A case file that accumulates each skill's output: 1. Route. Always start with visual-intent. Then visual-encoding. If the subject is scientific/spatial/network/diagram/map, invoke scientific-visualization in parallel with encoding/composition. Then visual-composition. Then visual-render-qa. Do not re-implement their rules here — call them and collect their outputs into the case file. 2. Follow the reasoning sequence (do not skip levels): intent → abstraction → task → representation → encoding → hierarchy → composition → annotation → style → render → inspect → repair (S01 neste

This is an excerpt. Refer to the complete source and its current requirements.