Set release boundaries for the 3×3 plus-sign image classifier

Before release, define what the artifact refuses to do. The operational risks here are wrong dimensions, non-binary pixels, rotations, one-pixel corruption, and a threshold fitted only to memorized examples. Validate ranges, minimize retained data, pin the reviewed configuration, and assign an owner who can disable the feature. Safety is implemented at the boundary and release process; it is not a warning paragraph placed after an unsafe function.

The artifact's user-facing goal is specific: classify a tiny pixel grid as plus or other while keeping the pixels, score, threshold, and prediction visible. Its accepted input is exactly three rows of three binary brightness values. Those statements are intentionally narrower than “build an AI system.” Narrow scope lets us inspect every input and expected result, and it prevents a toy result from being presented as a production claim. Run this gate as part of a release command. A failed assertion means stop, investigate, and do not publish.

Save this as lesson.py and run python3 lesson.py. It uses only the language standard library, so the example is reproducible offline.

meta={'image_id':'local-001','consent':True,'retention_days':0}
assert meta['consent'] and meta['retention_days']==0
print('process in memory; do not log pixels')

Expected output: an in-memory privacy gate. Exact floating-point formatting may vary slightly, but the asserted behavior must not. Read the output as evidence about this stage, not merely proof that the interpreter started.

Print the 3×3 grid, flattened indices, five selected pixels, score, threshold, and label. If a rotated or shifted plus fails, that is an invariance limitation rather than a Python bug. Enumerate all nine single-pixel flips instead of trying one convenient corruption. Shape and binary-value errors should stop before scoring so malformed images cannot masquerade as confident predictions.

At the safety and operations stage, save the smallest failing fixture beside the expected result. Change one cause at a time and rerun the exact command printed above; that makes the repair reviewable and keeps this chapter's progressive artifact reproducible.

Use named positive and negative grids to compute confusion counts, then report every single-pixel-flip result. Accuracy alone hides whether the toy misses pluses or calls unrelated lines pluses, so include recall and false-positive count. Keep the threshold in the report and test a rotated plus separately. This evaluates a handcrafted detector, not a camera-ready vision model.

For this safety and operations page, preserve the fixture and result as evidence for the next page. Label observations separately from conclusions: a passing assertion establishes the behavior it names, while broader usefulness requires the chapter's full evaluation set and stated operating limits.