The primary issue with this is the way shares and equity work. Elon Musk is a trillionaire on paper. He pays himself famously little.
That net worth is, under our current system, tightly linked with his interest and control in his various enterprises.
He can borrow against it which gets around taxes and that should probably be addressed, but he like the hypothetical fresh billionaire startup founder don’t have that money. And the mega rich on paper can’t access more than a small percentage of that money without reducing their control of the company they built or are building.
Ideas like a wealth tax, or the new sovereign fund paid into by an equities tax or grant are all interesting, but they are all more complicated on the ground than “wouldn’t $100m be motivating enough?”
FWIW, I think that some sort of public endowment and/or sponsored healthcare, education and safety net and/or tax or management of hyper wealth is one of the problems of our age.
But part of that problem is that it’s not clear how to do that in a way that is workable in an increasingly multipolar world of tech and soon healthcare giants that are as powerful as small but growing nation states. Economically and in some cases militarily linked to great powers.
A generous read of this comment might be that you did catch it internally in testing AFTER it shipped but shrugged it off as something you'd patch in the next release in a week or two. Is that what you meant here?
Or that it was caught but didn't surface fully before release?
A helpful governance policy here might be that anything that mutates user content without opt-in consent requires a distinct sign-off or a double sign-off. If the goal is to prevent this from happening in future.
Well, if you personally were building von Neumann machines do any purpose in the solar system, would YOU be interested in sending some to neighboring systems knowing that you could conceivably get a response in your lifetime.
Would you be at all interested in expanding that project to outlast you?
And even if you personally wouldn’t be so inclined, surely you know or have met people who might?
Once you have the self replication, expanding scope may just be additional code…
local-governor is my store for epics, specs, run records, schemas, contracts, etc. No logic, just files. I want all this stuff in a DB, but it's easier to just drop a file path into my spec runner or into a chat window (vscode chat or cli tool), but I'm tinkering with an alt version on a cloud DB that just projects to local files... shrug. I spend about as much time on tooling as actual features :)
Here’s how I do the same thing, just with a slightly different wrapper: I’m running my own stepwise runtime where agents are plugged into defined slots.
I’ll usually work out the big decisions in a chat pane (sometimes a couple panes) until I’ve got a solid foundation: general guidelines, contracts, schemas, and a deterministic spec that’s clear enough to execute without interpretation.
From there, the runtime runs a job. My current code-gen flow looks like this:
1. Sync the current build map + policies into CLAUDE|COPILOT.md
2. Create a fresh feature branch
3. Run an agent in “dangerous mode,” but restricted to that branch (and explicitly no git commands)
4. Run the same agent again—or a different one—another 1–2 times to catch drift, mistakes, or missed edge cases
5. Finish with a run report (a simple model pass over the spec + the patch) and keep all intermediate outputs inspectable
And at the end, I include a final step that says: “Inspect the whole run and suggest improvements to COPILOT.md or the spec runner package.” That recommendation shows up in the report, so the system gets a little better each iteration instead of just producing code.
I keep tweaking the spec format, agent.md instructions and job steps so my velocity improves over time.
---
To answer the original article's question. I keep all the run records including the llm reasoning and output in the run record in a separate store, but it could be in repo also. I just have too many repos and want it all in one place.
I think this one way of looking at what your parent was describing.
They weren’t just saying ‘AI writes the boilerplate for me.’ They were saying: once you’ve written the same glue the 3rd, 4th, 5th time, you can start folding that pattern into your own custom dev tooling.
AI not as a boilerplate writer but as an assistant to build out personal scaffolding toolset quickly and organically. Or maybe you think that should be more systemized and less personal?
They likely won’t take any of their acquisitions down with them. They’ve been pretty good about keeping them mostly separate. They’ll be spun off in any eventual liquidation.
Unless you think they are being mismanaged or mismarketed now?
That net worth is, under our current system, tightly linked with his interest and control in his various enterprises.
He can borrow against it which gets around taxes and that should probably be addressed, but he like the hypothetical fresh billionaire startup founder don’t have that money. And the mega rich on paper can’t access more than a small percentage of that money without reducing their control of the company they built or are building.
Ideas like a wealth tax, or the new sovereign fund paid into by an equities tax or grant are all interesting, but they are all more complicated on the ground than “wouldn’t $100m be motivating enough?”
FWIW, I think that some sort of public endowment and/or sponsored healthcare, education and safety net and/or tax or management of hyper wealth is one of the problems of our age.
But part of that problem is that it’s not clear how to do that in a way that is workable in an increasingly multipolar world of tech and soon healthcare giants that are as powerful as small but growing nation states. Economically and in some cases militarily linked to great powers.