Lab: A checked plan for every request

Module 6 · Lab · About 75 minutes · Needs: the Module 3 lab's tools.py, and lessons 1 and 2 (Plan, CHECKS, PlanStore, run_plan and revise; done-checks, the consistency check and run_checked)

What you are building

The lessons built plans and verifiers in a notebook. This lab moves them into returns_desk/plan.py, the file Module 6 adds to the package, on top of Module 3's tools.py. A plan is a list of steps, each with a done-check that reads BrightCart's systems. Code keeps the plan in a file, runs it wave by wave, holds any email whose claims the systems contradict, replans once from evidence, and then hands over to a person. Tests pin each promise, and a real model plans R-1001, Aisha's $129.00 robot vacuum. Everything at BrightCart is simulated.