When you let Noah fix something, where does it get the know-how? From a set of written guides — one for each kind of problem. There's a guide for a Wi-Fi connection that keeps dropping, one for a full disk, one for a printer that won't cooperate. About two dozen come with the app.
You can read them
Each guide is a plain text file — the same kind of file a note is written in — that opens in any text editor. Open one and you'll see, step by step, how Noah thinks about a problem. Here's a real line from the Wi-Fi guide:
Steps 1–4 resolve about 85% of connectivity issues. Most common fix: power-cycling the router.
That's the actual instruction the AI reads while it works on your Mac. Plain, honest, written for a person.
Two kinds of guide
Some are a set of if-this-then-that steps — if the connection test fails, start here; if it passes, skip ahead — and Noah picks its path based on what it actually finds on your machine.
Others are a numbered checklist, for something with a set order. When a guide is written as numbered steps, Noah shows you a progress bar as it works through them, and it counts the steps itself instead of taking the AI's word for how far along it is.
You can write your own
Because a guide is just a text file, someone who wants to change how Noah handles a problem can simply edit it — no programming, no rebuilding the app. Drop a good file in the folder and Noah starts using it. You can even hand Noah a written tutorial and have it turn that into a guide for you.
We keep them fresh
There's a rule with teeth: if a guide goes six months without a review, the app won't build. A stale guide can't quietly slip through.
Two last things. A guide is a starting point — Noah still checks your actual machine and adjusts as it goes. And every command a guide suggests still goes through Noah's safety checks, so even a bad guide can't do more than those checks allow.