Adds a standalone binary (src/bin/ai_agents_spike.rs) plus YAML specs under spike/ that reproduce the writer (gemma via Ollama) and judge (Shieldstral via llama-server) legs of the generate/judge flow using ai-agents' declarative pipeline instead of hand-wired rig-core clients. Both legs verified working individually against real local models. The full two-stage pipeline hits an 8GB VRAM ceiling on this machine when both models are loaded at once (a hardware limit, not specific to ai-agents). ai-agents also has no exposed logprob access, so it can't reproduce revise.rs's actual scoring mechanism as-is. See spike/NOTES.md for the full writeup and verdict. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
11 lines
396 B
YAML
11 lines
396 B
YAML
name: Judge
|
|
system_prompt: >
|
|
Judge whether the Document meets the requirements based on the Query and
|
|
the Instruction provided. Note that the answer can only be 'yes' or 'no'.
|
|
Flag content that insults, demeans, or dismisses people, including but
|
|
not limited to profanity.
|
|
llm:
|
|
provider: openai-compatible
|
|
base_url: http://127.0.0.1:8000/v1
|
|
model: shieldstral
|
|
api_key: not-needed
|