Odin Critique

Use when the user asks for a council, second opinions, or parallel investigation. Not for cross-examination of existing proposals: use cross-critique.

Use when the user wants adversarial stress-testing of a proposed architecture, structure, or shape. Not for tasks that require source or remote-system changes.

Use when a non-trivial decision sits under uncertainty and correctness matters more than speed. Not for patch review: use review. Not for plan attacks: use load-bearing-assumption-test.

Use when independent proposals on a contested decision need cross-critique before choosing, reusing the original authors. Not for parallel multi-stance investigation: use council.

Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.

Use when a workflow, plan, diff, or completed work cycle must be checked for practices that punish the project later. Not for source, remote, credential, publish, deploy, or irreversible changes.

Use when the user wants an answer only from the moat seat: building, keeping, and thickening defensibility. Not for rebuilding from primitives: use from-first-principle.

Use when a user wants an answer only from the human seat: what a person can love, trust, and tolerate. Not for rebuilding from primitives: use from-first-principle.

Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.

Use when a user wants an answer only from the career seat: effects on human trajectories. Not for any other from-* lens seat or multi-lens synthesis.

Use when asked to answer only from the impact seat: who and what actually moves. Not for rebuilding from primitives: use from-first-principle.

Use when the user wants an answer only from the skeptic seat: cold reasoning without project loyalty. Not for rebuilding from primitives: use from-first-principle.

Use when a user wants an answer only from the breaking seat (stakeholders, dependencies, accounting, compatibility under destructive pressure). Not for any other from-* seat or multi-lens synthesis.

Use when the user wants an answer only from the business seat: money, customers, timing. Not for any other from-* lens seat or multi-lens synthesis.

Use when asked to answer only from the codebase seat: what existing code tolerates or punishes. Not for rebuilding from primitives: use from-first-principle.

Use when the user wants an answer only from the stability seat: preservation of the working machine. Not for rebuilding from primitives: use from-first-principle.

Use when the user wants an answer only from the innovation seat. Not for rebuilding from primitives: use from-first-principle. Read-only. No source or remote mutation.

Use when the user wants an answer only from the rent-seeking seat: extraction without building. Not for rebuilding from primitives: use from-first-principle.

Use when the user asks why a plan is wrong or says "poke holes in this". Not for tasks that require source or remote-system changes.