Fair, and thanks for saying it plainly. Which part bothers you, the tool being written with AI help, or AI anywhere near the vault? The second never happens. No model sees an export in either route. Route B does use AI twice: one builds the script on your machine, and a second, different one reviews the code before you run it. Only the code is shown to it. Route A has none of that. It's a plain script you can read top to bottom.
Thanks for weighing in. Agreed on both counts. Option A is exactly that: one readable script, runs offline, no dependencies. Option B is for people who won't run anyone else's code against their vault, even if they can read it. Same tests, same offline checker, but the code comes out of their own machine. Both routes get the test-before-vault step.
Fair, and thanks for saying it plainly. Which part bothers you, the tool being written with AI help, or AI anywhere near the vault? The second never happens. No model sees an export in either route. Route B does use AI twice: one builds the script on your machine, and a second, different one reviews the code before you run it. Only the code is shown to it. Route A has none of that. It's a plain script you can read top to bottom.
Thanks for weighing in. Agreed on both counts. Option A is exactly that: one readable script, runs offline, no dependencies. Option B is for people who won't run anyone else's code against their vault, even if they can read it. Same tests, same offline checker, but the code comes out of their own machine. Both routes get the test-before-vault step.