Agents
Keep the draft tied to the requested pump
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 draft to its field check. Inspect the valid flag before comparing it with request data.
The display needs a draft about the requested asset, with a matching supplied citation and text that remains text.
Inspect the component calculation
Check the draft fields( Proposed maintenance draft: Proposed maintenance draft )
Examples and results
- Proposed maintenance draft
{ "asset": "P7", "citation": "M7", "text": "Check <coupling> & mounting." }- Required result
{ "valid": true, "draft": { "asset": "P7", "citation": "M7", "text": "Check <coupling> & mounting." } }
- Proposed maintenance draft
{ "asset": "P7", "citation": "M8", "text": "Check the mounting." }- Required result
{ "valid": true, "draft": { "asset": "P7", "citation": "M8", "text": "Check the mounting." } }
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
The example does not establish factual support, maintenance safety or permission to perform an inspection. Its encoding is specific to an HTML text node. 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.
Matching IDs still carry literal markup
This check uses the pieces from “Check what the display is about to consume”.
BOTIE
- Proposed maintenance draft
{ "asset": "P4", "citation": "M4", "text": "Read <note title=\"P4\"> & verify." }- Asset requested by the technician
P4
- Supplied citation-to-asset map
{ "M4": "P4" }
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 the resulting draft still contradict its cited manual? Describe the question an evidence-support review must answer.
Name the consumer and the property each validator establishes. A safe representation is not a verified maintenance recommendation.
The example does not establish factual support, maintenance safety or permission to perform an inspection. Its encoding is specific to an HTML text node.
Work through the Python challenges →