How PHRONEN works
You state an outcome. PHRONEN owns it until it is verified or until it tells you exactly why it cannot be.
| Move | What happens |
|---|---|
| Understand | What you want, what must stay true, what counts as done. |
| Look around | Which devices are trusted, what is installed, what is in reach. |
| Choose a way | The most direct legitimate route: an application’s own interface first, then automation, the browser, the accessibility tree, the screen, the terminal. |
| Do it | On the device that has the capability. Irreversible steps wait for your decision. |
| Check | A verifier that did not do the work re-reads the world and confirms every condition. |
| Keep it | If you asked for an outcome that must stay true, PHRONEN keeps checking and repairs when authorised. |
The same loop runs whether you started from the web, your phone, the terminal, Zed or the API. A task has one identity everywhere and can be followed or continued from any of them.
Was this page helpful?