ChiralityDeployment and security
Written to be forwarded to your security team.
Where the software runs, what does and does not leave your network, how a licensed professional relies on agent work and still meets their obligations, and what we have not built.
Professional accountability
Your obligations do not change. That is the point.
A licensed professional who relies on work produced by someone else must supervise it, review it, and accept it personally. Those duties are written in terms of what the professional must do, not what the worker must be.
- Who built this
Chirality AI Ltd is an engineering company registered with APEGA, the regulator for professional engineering in Alberta, under permit #17007. You can verify that on APEGA’s public register.
That is a fact about us, not about the software. No regulator certifies software. It means the people who designed this hold professional obligations of their own, and built against the standard they are held to.
- The standard we work to
A written practice standard for the use of AI agents in regulated engineering work, grounded in the Engineering and Geoscience Professions Act, the General Regulation, and the APEGA practice standards on relying on the work of others and on authenticating professional work products.
Its position: an agent producing work under a professional’s direction is one of the “others” those standards already contemplate. The obligations that attach to relying on it are the same.
- How the obligations are met in the software
The architecture is mapped clause by clause against the practice standard on relying on the work of others, so a reviewing professional or an auditor can trace any requirement to the mechanism that satisfies it. The mapping ships with the source.
It is our mapping, not an endorsement by the regulator. It exists so your own professionals can check our reasoning.
The shape of it
A desktop application on your own machines.
- Where it runs
A desktop application installed on the user’s own machine. No server component to host, and no Chirality account, tenancy or cloud service required for the product to function.
- Platform, and why
macOS 15 or newer today, signed and notarised. A Windows build is planned, and may ship before it is signed.
Apple Silicon came first because it shares one pool of memory between processor and graphics, so an ordinary workstation can run a model large enough to do this work locally. On other hardware, local inference means a discrete accelerator; the practical answer is a hosted model.
- Where project data lives
In the folders you point it at, on your own storage, in whatever version control and backup you already use. Workflows, records, evidence and outputs are ordinary files in those folders. Nothing is copied into a vendor system, and there is nothing to migrate out of later.
- Models
-
Three ways to run a model: local on the machine, your own API key with a provider, or an OpenAI login. For material that cannot leave the network, the local model serves the work with no external inference call at all.
Local operation fails closed. When the resident model cannot serve a request the work stops. There is no fallback path that quietly reaches for a hosted API because the local one was busy.
Every governed run records which model and provider actually served it, including any substitution.
Where you choose a hosted provider instead, you supply your own account and key. The relationship is between your organisation and that provider. We do not proxy, intercept or retain anything.
- Permissions
Each conversation carries a declared scope: which folder, and whether the agent may read only, ask before changing, or write. Scope is enforced by the application. Work that reaches a hold point waits for a named person; the workflow asks, and does not record an answer on anyone’s behalf.
- Source code and licence
Free and open source under the MIT licence, published at github.com/sgttomas/chirality. Your security team can read it before it runs, your IT team can build and package it themselves, and you can fork and maintain it internally if you ever need to.
MIT is deliberate. A field-of-use restriction would sit badly beside a claim that you own what you build.
- Telemetry
The application does not require a connection to us to function. If optional diagnostics are ever added they will be opt-in and documented here.
How the limits hold
What the application enforces, and what the method asks.
Two kinds of rule, and we keep them apart. The first three are enforced by the application. The rest are written into the workflows the agents follow and looked for by the review scans; they are discipline, and the record shows when it lapses.
Folder scope · enforced
An agent works inside the folder it was given. Reads and writes are contained and recorded.
Permissions · enforced
Read only, ask before changes, or write, set per folder. Runtime behaviour, not a prompt hint.
Model recorded · enforced
Every governed run records the provider and model that served it, including any substitution.
Provenance · method
A substantive claim cites the file and section it came from, or carries a marker saying it has none.
No invention · method
A missing value is recorded as missing and raised as an open item. The review scans look for values with no source.
Gates · method
A finding waits for a disposition and a section waits at its gate. The workflow asks; a person answers.
Straight answers
What we have not built.
The application is real and in use. The apparatus an enterprise expects around it is not built. If your controls require one of these before anything can be installed, this does not fit yet.
- Single sign-on
No. The application has no accounts of its own; a hosted model provider, if you use one, has its own.
- Central administration
No. Policy is per machine and per folder, as files.
- Cross-project reporting
No. Each project folder is its own record; a coordination plane for organisations is in early development.
- Document-management connectors
No. It works on folders. Point it at a synced folder from the system you already use.
- Windows or Linux
No. See Platform, and why above.
- A hosted or SaaS edition
No, and none planned. The product is the desktop application and the files it works in.
- Certification of outputs
No software can. Acceptance remains an act by a person who can be held to it.