The model is not the product
Every AI product you can install is really two things. Underneath sits the model — the engine that reads, reasons and writes. Around it sits the harness — the application built around that engine: the window you type into, the sign-in it uses, the files and systems it is allowed to touch, the tools it can operate, and the guardrails and audit trail wrapped around all of it.
Harness is the industry's word for that outer layer, and it is where most of the real product competition is currently happening.
The engine and car analogy holds up well. Several manufacturers buy comparable engines, but the vehicles built around them differ enormously — and the vehicle is what you actually drive, insure, and let onto your property.
The four things a harness decides
When two AI products seem to have different capabilities, it is almost never a difference in intelligence. It is a difference in what the harness permits.
The harnesses you will hear about
Why this is a governance question
If you take one thing from this: the question can our AI reach that folder is not a question about how clever the model is. It is a question about identity and consent — which account it runs as, and what an administrator has permitted that account to do.
That makes harness selection a policy decision with a technical implementation, rather than a technical decision with policy consequences. It belongs in the same conversation as your access standards, not in a separate one about tooling.