ETHOS
Why we build, and what kind of company we want to be.
Read the Ethos →BUILD 17 · 04 SEPT 2026 · 12:23 BST
The Ideas Shed
The Ideas Shed way of building software.
A living philosophy for building useful, trustworthy software with AI. Serious underneath. Pink Cow on top.
Cow Rules grew from real Ideas Shed builds, mistakes and frustrations. It now holds the Ethos, Principles, Rules and Tools that help humans and AI make better software together.
Cow Rules is becoming the public, living source of truth for how The Ideas Shed builds software with AI.
It preserves practical lessons from real building so the next build benefits from what we have already learned.
Will this lesson make the next build better?
If yes, it probably belongs in Cow Rules.
We are deliberately showing the process we follow, what we learn and how that process changes over time. This is how we currently build, not a claim that everyone should build this way.
See How We Build →Four layers. No corporate treasure map required.
Why we build, and what kind of company we want to be.
Read the Ethos →The few durable beliefs that guide every product decision.
See the Principles →Practical instructions for how humans and AI should behave.
Read the Rules →Useful things we build once and sensibly reuse.
Use the Tools →AI can now build more of the software. That means humans should spend less time learning plumbing and more time deciding what should happen, what matters, whether the AI understood, and whether the solution truly works.
Remove complexity from the human.
Preserve the truth and the judgement that matter.
Cowglish translates the machinery into the minimum useful human understanding. Nerd Stuff is there when you want to learn what is happening downstairs.
“Production is currently resolving to a deployment generated from an earlier commit, while the latest changes have not reached the live environment.”
🐄 The thing you're looking at isn't the thing you just built.
Publish the latest build and check the normal live URL again.
Meaningful actions need obvious feedback. A tiny click deserves a tiny response. A major action can celebrate with stronger movement, clarity, or reward.
Avoid forcing people to remember random folders, threads, or versions. The current destination should be obvious every time.
Publishing once should mean one clear current live build. If the user refreshes, they should get the latest version without cache games.
Use chat for discovery, strategy and critique. Use WORK for implementation, execution, deployment and delivery.
No seven pillars. No 38-point framework. No Cow Rules Certified Practitioner™ Level 2 Diploma.
Cow Rules should stay small, sharp, and useful. A rule only survives if it repeatedly improves real products.
Before you build, check cowrules.theideasshed.com and follow the current Cow Rules relevant to this task.