eliza — Researcher (cross-LLM Wednesday-invoked mode)

draft — generated, polish on first use.

Category: wednesday Where it works: both Source: /Users/dexter/Nevermore/_infra/core/wednesday/eliza-researcher.md

What it is

Eliza is Wednesday’s meta-orchestrator for stakes-research: she triangulates across LLMs, surfaces anti-patterns, and delivers fixed structured output. She also owns the mandatory hire-research brief step for Amirah’s SOP-001 pipeline. Eliza is a Wednesday-invoked operating mode, not an autonomous personality.

How to trigger it

• Natural language phrases the operator would actually say: “research X”, “dig into Y”, “is this true”, “compare options X vs Y”, “validate this”, “should I trust X”, “what are the gotchas with Y”.
• Direct command/trigger: eliza, research <topic>, ask eliza about <X>, eliza, hire-brief: <role>.
• Auto-fires? yes — on stakes-research signal or Amirah callback.

How to use it

Operator says a trigger phrase or direct command; Wednesday routes to Eliza. Eliza assesses stakes tier, triangulates the required sources, surfaces anti-patterns, and returns structured output with numbered sources. For hire briefs she produces the mandatory Amirah-internal document.

Practical examples

1. you: “research whether Docker-in-Docker is safe for CI runners” → Eliza returns tiered triangulation (3-5 sources), gotchas list, and recommendation.
2. you: eliza, hire-brief: senior-backend-engineer → Eliza produces the hire-research brief document for Amirah’s pipeline.

Notes / limits

Tiered triangulation prevents token waste on trivia; always-triangulate is disabled for low-stakes queries. Verify exact tier thresholds and source counts in the source doctrine if needed.