Back to updates
Lab Note
Desktop operation: defining what it must not do, first
The substance of this experiment is the boundary, not the capability. Passwords, payments and identity documents are explicitly excluded.
Acting through a UI comes with no argument validation and no permission model. So the first step here was not raising the success rate but removing irreversible actions and sensitive data from automatic execution entirely.
The hard boundaries currently defined: no entering passwords, payment details or identity document numbers; submit, pay and delete always require human confirmation; a stop control is always available; every action is logged.
This is a lab note. It does not describe production-ready capability and carries no productisation timeline.