Where you work

Three views of the same product. An affordance that exists on only one of them is treated as unfinished.

One engine, three windows onto it

Most tools make you pick a surface and then live with what that surface cannot do. Tharas treats that as a defect. The terminal, the dashboard and the Telegram bot are not three products with overlapping features — they are three renderings of the same running state, and none of them owns anything the others cannot reach.

That has a practical consequence you will feel within a day of using it. Start a goal from the terminal before you leave the house, watch the plan land on your phone, approve it from a train, and open the dashboard that evening to read what actually happened — without any step being unavailable because of where you were standing when you needed it.

The rule behind it is deliberately blunt: a capability is not finished until it exists on all three, and is documented. A control that ships to the dashboard alone gets treated as work in progress rather than a release, because the moment one surface falls behind, the other two stop being trustworthy — you start having to remember which window can answer which question, and that is exactly the overhead the product exists to remove.

What differs between them is attention, not capability. The terminal is for when you are already in a repository and want to say what you want in one line. The dashboard is for when you want to see everything at once — live task state, spend, plans awaiting approval, and the health of work already shipped. Telegram is for when you are not at a computer at all and the only thing standing between an agent and six more hours of progress is somebody saying yes.