ChiralityThe Chirality app
It drafts, checks and keeps track. You decide.
A desktop application in which you direct agents inside your own project folders. Ask for something small and it does it. Ask for a design basis memorandum and it works section by section from the documents you admitted, stopping at each gate. Ask it to review a draft and it comes back with findings, each with its evidence, for you to rule on.
Free under the MIT licence. macOS today, Windows to follow. A local model, your own API key, or an OpenAI login.
Review the draft design basis, rev C, against the knowledge base.
Four scans ran on the draft: section coverage, extracted claims, TBD markers, thin sections. From those and the accepted decomposition I prepared fourteen candidate findings. Two contradict accepted state, five have no support in the knowledge base, three state a TBD as fact. Each is in the notes beside you with its evidence.
Accept, revise, waive or defer each finding. The draft does not change until you do.
Working in Northgate expansion · Working Items · Read only · Plain chat
How the work divides
Tools scan. Agents prepare. You decide.
Three layers, and none may skip the one above it. This is written into every workflow the agents follow.
What reaches you, and how it got there.
Deterministic tools do the mechanical part and produce facts without opinions: which sections are present, which values appear, where the TBDs are, which paragraphs are thin. Agents read that beside the project’s accepted knowledge and prepare candidate findings, each typed and each with its evidence.
- Scans are repeatable.The same draft gives the same substrate, run by anyone.
- Findings are typed.Incorrect, unsupported, missing, flattened, outdated, incomplete.
- Evidence travels with each one.The file, the section, the accepted state it was checked against.
Accept, revise, waive, defer.
Nothing in a published workflow produces a verdict. A finding waits for your disposition, a section waits at its gate, a lifecycle state changes only when you say so. The application enforces which folder an agent may touch and whether it may write. The rest is a discipline the files make easy to keep.
- Gates are conversations.The agent asks; you approve, edit, or redirect.
- Permissions are enforced.Read only, ask before changes, or write, per folder.
- The record accumulates.What ran, what it read, what you decided.
What you can ask for
The workflows are already written.
-
Publish a design basis memorandum
From accepted project state, section by section, with the open items listed alongside.
-
Prepare the basis of an estimate
Rates indexed to their sources, the effort assumptions, the basis itself. It stops before the total.
-
Review a draft
Against the knowledge base: coverage, claims, TBDs, thin sections, then findings for your disposition.
-
Read the source material
PDFs into Markdown you can cite. Drawings read: title blocks, equipment, valve counts. Equations audited.
Eighteen working agents, forty-five method packs, two hundred tools, published under MIT. Yours become versions of them, shaped to your work.
What you get
Three kinds of file. All of them yours.
Everything the application works from is a plain file in your project folder, in the version control you already use. Nothing lives in our product.
- Workflows
How a job gets done, written down once, with the gates marked. Agents keep it current; you edit it like any other file.
- References
What the work may rely on: the admitted documents, the standards, the decisions already made. Agents read these and say which.
- Checklists
What a result has to pass: what gets scanned, what gets listed, what a reviewer looks at first.
- The record
What ran, what it read, what you decided, accumulating in the folder while the work happens.
How it is built
Built for a person and an agent at once.
A human-agent system, with the agent native to it. The shape of everything Chirality AI makes.
The agent sees what you see
An agent working in the application operates on the same files, in the same terms, as the person in front of it. Not a thinner, translated view of the project.
A model of your choosing
A local model on Apple Silicon, your own API key, or an OpenAI login. Every run records which one served it.
Specialists you write yourself
The roles that ship are general. The corrosion engineer and the tender reviewer are yours to write, as files in your own repositories.
Straight answers
What it is, and what it isn’t.
It is a desktop application
macOS today, Windows to follow. No server, no account with us, no subscription.
It is not a chat window
It works from files in your folders and leaves files behind. The conversation is how you direct it. The record is what remains.
It does not produce verdicts
In every published workflow a finding, a gate, and a lifecycle change wait for a person. The application enforces scope and permissions. The discipline is yours to keep, and the method makes it the easy path.