Agents
Give Botie a next step it can justify
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 approval filtering to asset matching. Return only approved records for the requested pump.
A plausible answer is not enough. Botie needs a matching approved manual or another permitted step.
Inspect the component calculation
Match the requested asset(
Approved records: Keep approved manual records(
Manual records: Available manual records
)
Requested asset: Requested asset
)Examples and results
- Available manual records
[ { "asset": "P7", "approved": true } ]- Requested asset
P7
- Required result
[ { "asset": "P7", "approved": true } ]
- Available manual records
[]
- Requested asset
P7
- Required result
[]
- Available manual records
[ { "asset": "P7", "approved": false } ]- Requested asset
P7
- Required result
[]
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
These are invented, recorded examples. The browser runs your construction without calling a language model. Passing them checks the surrounding program, not the quality of a live 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.
The needed evidence is already available at the limit
This check uses the pieces from “Give the lookup a stopping rule”.
BOTIE
- Available manual records
[ { "asset": "P12", "approved": false }, { "asset": "P12", "approved": true } ]- Requested asset
P12
- Remaining lookups
0
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 would a matching manual still fail to prove about the final answer?
The controller establishes a route. Answer support and action permissions need their own checks.
These are invented, recorded examples. The browser runs your construction without calling a language model. Passing them checks the surrounding program, not the quality of a live model.
Work through the Python challenges →