The same idea, described consistently — whether you’re a sales leader, a security reviewer, or the engineer who has to sign off.
Software invocation the idea
Making the software you already own do the work — invoked by a person or an AI, governed at the moment it fires, with a record it ran. Adoption is what people do; invocation is what software does.
Execution of record what you get
Every company has a system of record. The execution of record is the chain of every command sent to real software — checked where it landed, bound where its result went, and kept. One record for people and agents.
Governed programmable runtime what it is
A runtime for unmodified applications on Windows, macOS and Linux, where every command passes a check at the live target and lands in one chain.
Native application invocation how it works
Agents call the application’s own commands, discovered from the running application — not from a screen, and not from a plugin the vendor had to ship.
Callable surface
What an application can already do, discovered live from the application itself. The API is what the vendor chose to expose; the callable surface is what the software can do.
In place
The application stays where the operating system drew it, on the user’s own machine. No virtual desktop, no re-hosting, no pixels shipped anywhere.
Human in seat
The person stays at the machine. The agent works alongside them on the same surface, both using the same controls, and either can take over.
Per-command authority
A grant that covers one command, checked against the exact live window it is about to touch, for a bounded time. It is not a seat and it does not persist.
Bound output
Where a command’s result may go is part of the grant and part of the record — decided per command, not per machine.
Screen state
A whole desktop — which applications, where, showing what — saved under a name and pushed to any number of machines. The repeatable framework you can open.
Composed workspace
Your real applications joined into one live workspace arranged for the task. Grounded in the software itself, not a dashboard generated beside it.
Attested
Kept by the endpoint where the action happened, so the record can vouch for it. Only a party at the action can attest to it.
Local-first, cloud-optional
The runtime, the broker and the record run in your environment. A cloud model or a local one works the same way, and nothing leaves the endpoint unless you send it.
The governed workstation
The picture: a person and an agent on one desktop, using the same controls, with one record between them — and a check on every command before it lands.