PXI · UI code mode · Policy trace

Approval is per script, not per click

The user approves a script's described changes once, before it runs. Every action the script then asks for is checked against that approval. A script that never asked can read, but not change.

Approval is per script, not per click Two scripts issue the same dataset.create action. Both pass validity checks. The approved script passes the approval check and the page creates the dataset. The unapproved script fails the approval check, never reaches the page, and is refused. Same action in both scripts ui.dataset.create(…) Script A user approved its changes Script B no approval asked for 1 Is it a real, available action with valid input? checks 1–4 · else an error code says what is wrong ✓ PASS ✓ PASS 2 Did the user approve this script's changes? check 5 · else APPROVAL_REQUIRED · reads skip this WHERE THEY DIVERGE ✓ PASS ✕ FAIL · APPROVAL_REQUIRED 3 The page performs the action check 6 ✓ PASS — NOT REACHED Dataset created ok Refused, nothing changed PXI asks for approval and retries LEGEND ✓ PASS ✕ FAIL · the script gets an error code back — NOT REACHED
←/→ step · Space play/pause · R replay · Home/End jump

Skipping the approval step never skips approval. The unapproved script still runs, its reads work, and its first change is refused with APPROVAL_REQUIRED so PXI can come back with a description for the user to accept.