Tools
Each tool is a text box. Write or paste your draft, and it is reviewed automatically against named checks. Every run is saved with its date, so you can see what changed between versions.
Pyodide workspace evidence sheet
This records how your project runs in this app's Python workspace: the file it starts from and the files it reads and writes. Write the entry file, the files in the workspace, and what you saw when you ran it.
Not openedEarly accessRecord data-flow tracer
This traces one real record through your program, from the moment it arrives to the decision and the output. Write where it enters, where its types are set, where the rule runs, where errors are reported, and where the output leaves with its reason code.
Not openedEarly accessStructured input contract
This turns a real JSON or CSV file you work with into named fields and failure rules. Write each field you rely on, its type, and what happens when it is missing or malformed.
Not openedEarly accessSQLite transaction planner
This plans how your import writes to SQLite so a failure never leaves half a record. Write what identifies a record, which tables each change writes to, where the transaction commits, and what rolls back when something fails.
Not openedEarly accessFailure response map
This sorts the ways your application can fail by who owns each failure and how it recovers. Write each failure, the message it shows, who fixes it, and the recovery step.
Not openedEarly accessRelease and handoff checklist
This collects what another learner needs to open, run and recover your project. Write how to open the workspace, configure and run it, what output to expect, the known failure messages, and how to recover.
Not opened