Agents
Separate the record check from the asset lookup
A perfectly shaped answer names P-9
Botie proposes diagnosis records. The application needs to tell a malformed record apart from a well-shaped record about an unknown asset.
BOTIE
The inputs we are comparing
Candidate response record
Known asset
{
"asset": "P-2",
"diagnosis": "seal wear"
}An unfamiliar asset
{
"asset": "P-9",
"diagnosis": "seal wear"
}Required field names
Same in both cases
- 0asset
- 1diagnosis
Known asset IDs
Same in both cases
- 0P-2
- 1P-3
Result for known asset
- 0true
- 1true
The model adds an unexpected approval field
This check uses the pieces from “Keep two different verdicts visible”.
BOTIE
- Candidate response record
{ "asset": "P-3", "diagnosis": "inspect the seal", "approved": true }- Required field names
- 0asset
- 1diagnosis
- Known asset IDs
- 0P-3
- 1P-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.
What can remain wrong when both flags are true?
A structured proposal is ready for further checking, not automatically ready for execution.
This is a small hand-built validator for supplied records. It does not parse model text or check clinical, mechanical, or factual correctness.
Work through the Python challenges →