This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
What I Built
ScopeGuard is one static page that answers a question every freelancer on a fixed fee has asked themselves: which lines in this client message did I actually agree to?
You paste the scope you signed - the brief, the proposal, the SOW - and the message that just landed in your inbox. The page splits both into sentences, embeds them locally, and prints, line by line, how close each new ask is to something you promised. Anything that does not match gets flagged with its similarity score and the closest line from your scope. Below that it drafts a reply that separates "that was in scope, I'll pick it up" from "that's new work, here's a change order".
Who would pay for it: freelancers and two-person studios on fixed-fee projects - the people whose margin disappears into "while you're in there, can you also...". The version I would charge for is this page plus per-client project files, a change-order PDF export, and a read-only link the client can open.
The local-first part is not ideology, it is the actual blocker. A lot of this text is under NDA, or it is a client's unreleased roadmap. Those people cannot paste it into a cloud tool, and asking them to is how you lose the sale. A 23 MB model that runs in the tab is the difference between "I can use this at work" and "I can't".
Demo
Live, no signup, nothing to install: https://zoizero86-beep.github.io/scopeguard/
Click Load a sample and then Check this message. Short version of what happens on the sample: of the 4 sentences in the client message, 3 fall below the 0.45 threshold, the mean best-match similarity is 0.345, and the sentence that does match lands at 0.478 against "Rewrite the onboarding copy on three screens". The reply draft then lists the three flagged lines as new work.
The first run downloads about 23 MB of model once. After that it is served from the browser cache, and you can pull the network cable and it still works.
Code
https://github.com/zoizero86-beep/scopeguard - MIT, one HTML file, no build step, no dependencies to install.
How I Built It
The whole thing is one index.html. There is no backend, no account, no analytics, and no API key to leak.
- transformers.js (Apache-2.0) loaded straight from a CDN, running onnxruntime-web with WASM.
-
Open-weight model: Xenova/all-MiniLM-L6-v2 (Apache-2.0), loaded as
dtype: 'q8'- about 23 MB - throughpipeline('feature-extraction', ...). - Embeddings are mean-pooled and L2-normalised in the pipeline, so similarity is a plain dot product, which is why scoring 40 sentences stays instant.
- Sentence splitting is a small regex pass that drops lines shorter than four words, because four-word fragments produce noisy matches.
- I set
env.backends.onnx.wasm.numThreads = 1so the page does not depend onSharedArrayBufferand therefore does not need COOP/COEP headers. That matters on GitHub Pages, where I cannot set response headers. One thread is slower and completely fine at this size.
What the model is doing here is narrow and worth being precise about: it scores topical relatedness between your scope and the new message. It is not reading intent, and it does not know what a contract is.
The one thing I deliberately did not put through a model is the reply. Asking a small text generator to write a client email would produce something confidently wrong about money. So the draft is a fixed template with your flagged lines dropped in, and the page says that in as many words.
Why Does Open Innovation Matter?
Three things that a closed API could not have given this project:
- The privacy claim is checkable. "Your client's text never leaves the tab" is a statement I can prove - open the network panel after the model loads and watch it stay silent. With a hosted API, the same sentence would be marketing, not a fact.
- The cost curve is flat. This is meant to be used maybe forty times a month by one person. Zero marginal cost per check means the free tier can be genuinely free, and the paid tier can sell features instead of rationing tokens.
- The model is a swappable part. It is an ONNX sentence encoder. If a better small open-weight encoder appears, or someone needs a Chinese or German one, the swap is a string in one file. Nobody has to wait for a vendor to support a language, and nothing about the app depends on someone else's pricing page.
My First User
Not yet. I finished this during the entry period and have not put it in front of a paying freelancer, so there is no honest "they paid" story to tell here. What I can say is the obvious next step: three freelancers I know work on fixed fees, and the sample in the repo is built from a brief close enough to theirs that it should be an easy conversation.
