Well, you mentioned Gas Town — that deserves an immediate reflexive downvote :P I actually upvoted your post. I'm not sure I entirely agree with it, but I was

Well, you mentioned Gas Town — that deserves an immediate reflexive downvote :P I actually upvoted your post. I'm not sure I entirely agree with it, but I was interested to see more discussion about it, and that felt worthy of an upvote. As for the reaction against the idea, I see it from two angles. Is the standard corporate hierarchy / architecture really the optimal organization principle for AI? Or is that just a skeuomorphism to make this project seem more serious than it really is? Maybe Yegge did us a favor by mapping to Mayors & Polecats, forcing people to question if it really is the correct organizational hierarchy? The other angle is heresy here - HN is full of employees now. There is little incentive for employees to be interested in what a C-suite does, and we see that with the comments about CEOs needing to be six foot and walk impressively. Employees have no interest in AI organization principles that optimize them away and highlights their obsolescence. I am surprised there hasn't been more discussion about how this specific project optimizes away the C-suite humans instead - I would have thought that could have had some appeal to employees, at least until those people realized it makes employees a swarm that works for AI leadership. As for AI organization, the organizational mapping needs to be productive, not affectation or cargo-culting. That's not peripheral — that's load-bearing. Especially in a corporation model, you can find the organization layers only create busywork with lots of unnecessary middle managers. You don't want your AI C-suite swarm burning tokens on endless meetings about what should be in the upcoming meeting... especially not at Fable API pricing.