chief cybernetics officer
177 Followers
I was about to write something like, “If things go wrong for United States democracy, I think it’d look more like Operation Condor than Nazi Germany.” But then I remembered that Operation Condor kinda did happen in the US. It was called COINTELPRO. Its tactics were exported to Latin America in supercharged form during the 1970s via School of the Americas, which still exists, but has since been renamed to the charmingly innocuous “Western Hemisphere Institute for Security Cooperation.” Keep your mfkn eyes peeled.
it's a long complicated story (among, at least, one other long, complicated story) but one result is: i've started enforcing skills and workflows as code, which is, like... ok i guess we could just call it code. is how you get agents saying things like "The CLI expects an exact feedback line in the critique, and the artifact says “Verdict: accepted…” in prose but not the machine-readable `Decision: accepted` line." or: "I’m running the phase verifier again to see whether README-7C needs another fresh review cycle or can now advance." ...like it just seems cleaner this way but also: idk tho aha, I'm not really sure 🤔 i always just kinda do my own thing, but it seems like people are converging on this sort of approach, e.g., The skill for when agents need to collaborate and write a spec is now but a thin dispatcher, as Codex likes to say, and reading the skill now, it really doesn't have to be more than this:
I’ve seen videos of two difference ICE retards yelling “Did you not learn from what just happened?” at protestors, which is weird that it happened twice. But what do you expect when they're treated by the federal government like they’re Trump’s secret police.
acquired protardio