← All workshopsRead What Should Happen When the Model Cannot Help?

Test the Design and Plan for Failure

Route unusable pump records to review

BOTIE

Return one use-model flag per record only when validity and freshness both hold.
Ready to test
0 passed · 0 failed · 2 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

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.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Return one use-model flag per record only when validity and freshness both hold.

Botie should use a model decision only when its record is valid and recent enough. Every other case needs the specified fallback action.

Inspect the component calculation
Multiply(
  Value: Record validity flags
  Multiplier: Threshold gate(
    Score: Maximum age in minutes
    Cutoff: Record ages in minutes
  )
)
Examples and results
Record validity flags
  1. 01
  2. 11
  3. 20
Maximum age in minutes
5
Record ages in minutes
  1. 02
  2. 19
  3. 21
Required result
  1. 01
  2. 10
  3. 20
Record validity flags
  1. 01
  2. 11
Maximum age in minutes
5
Record ages in minutes
  1. 05
  2. 11
Required result
  1. 01
  2. 11
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 review team needs its own capacity and response policy. This routing calculation does not prove that manual review is effective or timely. 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.

A fresh but invalid input still needs the fallback

This check uses the pieces from “Route failed preconditions to review”.

BOTIE

Botie may use a primary decision only when its input is valid and no older than 5 minutes. Otherwise use that row's specified fallback. Action codes are -1 for review, 0 for defer and 1 for inspect. Return the routed actions in row order.
Record validity flags
  1. 00
  2. 11
  3. 21
  4. 30
Record ages in minutes
  1. 01
  2. 15
  3. 26
  4. 30
Maximum age in minutes
5
Model action codes
  1. 01
  2. 10
  3. 21
  4. 30
Review action codes
  1. 0-1
  2. 1-1
  3. 20
  4. 31

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 workload and response promise must the review team support if every record takes the fallback?

A defined fallback still needs capacity, ownership, and recovery evidence; routing alone does not establish a usable service.

The review team needs its own capacity and response policy. This routing calculation does not prove that manual review is effective or timely.

Work through the Python challenges →
Continue the courseCan We Defend the Inspection Service Design? →
← What Should the Prototype Teach Us?