Agents
Keep invented citations out of Botie’s answer
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Connect the proposed answer to Check the answer fields. Inspect the valid flag and the citations it retains.
The maintenance interface needs a readable answer with references it can open.
Inspect the component calculation
Check the answer fields( Proposed answer record: Candidate answer record )
Examples and results
- Candidate answer record
{ "answer": "Inspect the mounting.", "citations": [ "manual-7" ] }- Required result
{ "valid": true, "citations": [ "manual-7" ] }
- Candidate answer record
{ "answer": "Inspect the mounting.", "citations": "manual-7" }- Required result
{ "valid": false, "citations": [] }
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
This toy boundary does not judge whether the source entails the answer and does not run Pydantic AI or a language model. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
One valid citation hides another invented reference
This check uses the pieces from “Make the citation boundary explicit”.
BOTIE
- Candidate answer record
{ "answer": "Inspect the coupling and mounting.", "citations": [ "manual-2", "manual-9" ] }- Excerpt IDs available to this run
- 0manual-2
- 1manual-4
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
Could an answer pass both checks while contradicting the manual? Explain what test would catch that different failure.
Keep structural validation separate from evidence support. Framework code can organise both without making them the same claim.
This toy boundary does not judge whether the source entails the answer and does not run Pydantic AI or a language model.
Work through the Python challenges →