anbende
Joined 12 years ago
Joined 12 years ago
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.
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/epics/e-epics/e014-clinical-domain-model/runs/run-e014-01-ops-catalog-20260302-173907-244c82
- Attempts
+ Steps
- Step 1
- Step 2
- ...
- Step 13
job_def.yamljob_instance.json
changes_final.patch
run_report.md
improvement_suggestions.md
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 :)
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.
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?
I found it again when mail order Netflix first came out in my early 20s. It was like rediscovering my childhood and completing a character arc.
Accessing information on a customer's server or tenant (I have been assured) would require a court order for the customer directly.
But... as an 365 E5 user with an Azure account using the 4o through Foundry... I am much more nervous than I ever have been.
It’s not exactly about rules consistency either as stated by the GP, though that’s part of it. It’s more about strong consistent application of scientific principles even theoretical or untested principles.
This is in contrast to futuristic fantasy with no real focus on the science. But futuristic or space fantasy can be very consistent just like magical systems in fantasy can be very consistent. Hard scifi has to be constrained by plausible consistent science and that science is typically a main character in the story, or even THE main character.
Addiction is highly dependent on the immediacy of the drug’s effect on the brain. For this reason, people who smoke cocaine (directly or as crack) are highly likely to get addicted. It may be the majority. People who snort it are less likely to get addicted. And there are a lot of casual cocaine users (snorting) who do not develop a long term life altering addiction. I believe he (researcher friend) said it was 10-15% who go on to become addicted. Still substantial and dangerous but much less than smoking.
His research was looking at delayed onset of cocaine in rats after they pushed their cocaine lever. At longer delays more and more rats showed little interest.
This is part of the overall addiction picture. Decoupling drug use behaviors (smoking, snorting, and lever pressing) from noticeable drug onset prevents reinforcement of the behavior and makes addiction less likely, often much less.
This would explain why nicotine patches and gum would potentially be much less addictive than cigarettes.
https://www.bipm.org/en/si-base-units/kelvin
Anyway, TIL.
At least that’s my attempt to defend the GP’s statement.
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.