The agent can advise, but cannot complete the work.
Promising automation stays trapped in experiments and support chat.
ENTERPRISE AI · STRATEGIC BRIEF
Let AI agents work on Windows—
without losing control of the machine.
An agent can complete a command and still leave a workstation silently broken. When software acts on a real PC, organizations need to constrain what it can touch, preserve working state, and verify the outcome.
Pinman gives Windows workstations a versioned memory of the configurations that matter—and gives people, automation, and AI agents a controlled, auditable, and reversible way to work with them.
AGENT OR AUTOMATIONProposes and performs work
PINMANState · history · boundaries · verification
WINDOWS WORKSTATIONSelected files, settings, and devices
FROM DEMONSTRATION TO DEPLOYMENT
That is where the hard questions begin.
An impressive agent demonstration is not the same thing as a production operating model. Before an agent works on a real Windows machine, an organization needs concrete answers.
- 01What should an agent be allowed to inspect and change?
- 02What machine state and data should it be allowed to access?
- 03How will you detect a wrong or incomplete action?
- 04When must a person approve or intervene?
- 05How will actions be authorized, audited, and reversed?
- 06Which workstation workflows are bounded enough for production?
- 07How will you prove operational and business value?
These questions are larger than any one product. Pinman addresses a specific part of them: the state, change, recovery, and evidence at the Windows workstation where an agent’s action has consequences.
THE WORKSTATION BLIND SPOT
The model can reason. The workstation is still fragmented.
The configuration of a working PC is spread across application data, the Windows Registry, operating-system settings, and connected devices. A screenshot or successful command exit code does not show the complete operational state that matters.
The agent can act, but the blast radius is unclear.
Security and operations teams inherit risk they cannot easily observe or reverse.
THE MISSING OPERATIONAL LAYER
Legible state · scoped authority · durable history · verification
WHAT PINMAN PROVIDES
A local state and change-control layer for the workstation.
Pinman models the selected configuration that makes a particular machine or workflow operate correctly. The same model is available through the browser UI, CLI, REST API, and MCP interface.
Legible state
A Schema selects the files, Registry areas, Windows settings, and device settings that matter for a particular machine or workflow.
Operational memory
Captures, comparisons, and the Journal preserve what the selected configuration was, what changed, and the context around the work.
Bounded action
Named Pinman operations, Profiles, roles, and product permissions give automation a narrower surface than unrestricted access to the PC.
Recovery and verification
A workflow can preserve selected state before a change, apply an intended result, and compare afterward to see whether it actually worked.
01ObserveRead selected current state
→02CompareFind relevant drift
→03ActUse a permitted operation
→04VerifyConfirm the resulting delta
THE MATERIAL IMPROVEMENT
Replace broad intervention with bounded, measurable operations.
The immediate value is not “more AI.” It is a better operational method for people and automation working on consequential Windows machines.
Operational problemTypical result todayWhat Pinman adds
Blind interventionA command finishes successfully, but the workstation may still be in the wrong state.Read selected state before the action and compare again afterward.
Broad recoveryA difficult configuration problem can end in a reinstall, reimage, or an overly broad restore.Recover selected tracked settings or file data while preserving unrelated work.
Tribal knowledgeA few specialists remember the sequence of settings that makes a complex machine work.Encode relevant locations in Schemas and intended configurations in reusable Profiles.
Opaque evaluationAn agent pilot demonstrates activity without proving that workstation outcomes improved.Define a baseline, record changes, and measure a bounded workflow against explicit results.
THE ASK
Bring us one consequential Windows workstation problem.
Parkerhill Technology is seeking organizations with a consequential Windows workstation problem and an interest in determining whether Pinman can create a measurable improvement.
The proposed next step is a paid, structured evaluation focused on one workstation, workflow, or machine class. Together, we define the baseline, model the relevant environment, test the Pinman-assisted approach, measure the results, and decide whether and how to deploy.
A SUCCESSFUL EVALUATION SHOULD PRODUCE
- A working Pinman configuration for the selected environment
- Measured operational results against an agreed baseline
- An initial ROI and TCO analysis
- A documented security and authorization approach
- A defined path to deployment
GO DEEPER
Read the complete strategic brief.
The PDF expands the argument, the operational comparison, and the proposed evaluation model in a portable format.