There’s also a “ask” mode which is read only. Both are enforced by the permissions model, not just a system prompt instruction. I’ve seen the model “forget” and try to start coding - it bounces off a hard permissions failure and that “reminds” it that it’s in plan mode.

For remote renewals/replacements, they just give you a temporary license to print out and then mail you a new one. The old license never gets physically cancelled.

I don't know of anyone in the VC or traditional incubator communities who has an appetite for this. And the groups who are an ideological fit don't have the funds to be worth pursuing.

It's a niche. Like most niches, there's the opportunity to prosper, but yeah - bootstrapping (or angel-bootstrapping if you're lucky and have a personal connection) is pretty much the only way to go here.

The alternative, and there are a very few tunes that have done this, is to prove to regulators that the tune does not negatively affect emissions in any way. In practice this is done by getting a CARB exception since they’re the ones actually checking for tunes.

Short lifetime mandatory reauth to enterprise SSO seems to be the best available, but it’s inconvenient for the single Classic PAT we actually need.

Their knowledge repository is slowly rotting under the weight of having to ask every time "okay, is this correct-sounding, highly upvoted answer actually (still) correct, or is it 10 years out of date?"