What this page was worried about has largely stopped being a problem. The checking tool now runs on your own computer against an AI account in your name, so the transfer described here as a large future build has already happened.
What is left is a smaller question about a small amount of underlying code, and it is not urgent.
The handover stopped at a setup step on your machine, so nothing is handed over that has to be installed. Anything you cannot open like a web page stays running on my side and you get the result rather than the software.
Worth reading first: it explains why owning this tool outright is not a matter of handing over files.
The parts that make it a working tool: the piece that serves it, the piece connecting it to a session, the way sessions are kept separate, the login, and the search across the reference library.
All of that is a second deployment of a stack I built for my own work. It is why the tool went up in days rather than months.
The checking itself is done by an AI model. The tool is a way of talking to that model, not a program containing it, which is why no file can hold the intelligence.
The model is now reached through your account rather than mine, which is the part that changed.
When this was written the intelligence sat in my environment and no version could simply be handed over. The tool has since been rebuilt as an application that installs on your computer and talks to the AI through an account in your name.
You had in mind a cloud account in your name with the AI billed to you. What it does now is simpler.
You install it like any other application and open it from your own computer. No server to rent, no cloud account, nothing to pay for beyond the AI itself.
It uses your own AI subscription. Nothing routes through me or is metered by me, so if you stopped working with me tomorrow the tool keeps working.
The documents you check and the answers it gives sit in a folder on your computer, outside the application, so updating the app does not touch them. Only the question you ask leaves your machine, and it goes to the AI rather than to me.
The tool's own screens work with no connection. A check does not, because the AI doing the checking is not on your computer. That limit applies to any tool of this kind.
These apply to any build where I would otherwise reuse something I already own.
| Option | Who owns the code | Time | Money | Restriction on you |
|---|---|---|---|---|
| 1. From scratch | You, outright | Highest, and it repeats on every build | None beyond the contract | None |
| 2. Reuse, terms written down | You own the product. I keep the reused files. | Lowest | None beyond the contract | Those files cannot be sold on their own as code |
| 3. Buy the code | You, outright | Low | A one off cost per piece | None |
Nothing. There is no decision to make this week and nothing is waiting on one.
The checking tool and the image tools are yours to run either way. These options are about the small amount of underlying code that came from my own projects, and that only needs settling when we start something new that would reuse it, most likely the study dashboard.
Before I ask you to choose, I will bring a time estimate for option 1 and real figures for option 3, worked out from an existing build rather than guessed.
If any part reads unclear, say which and I will rewrite that part. If you would rather someone else look at it before you decide, that holds nothing up.