ArchSpec 1.0: Executable Architecture Specification for Ruby’s Agent Coding Era 0 ▲ Carmine Paolino 25 minutes ago · 8 min read1559 words · Tech · hide · 0 comments More and more code is written by a model. Tests still tell you it works. RuboCop still tells you it’s tidy. Nothing tells you it still follows your architecture. I released ArchSpec 1.0 today. It’s an architecture linter for Ruby and Rails. You declare your components and boundaries in one file, and every change gets checked, whether a person or an agent wrote it. This is part of my push towards making Ruby one of the best languages to build with AI. RubyLLM is one piece. Schematist is another. Making the default Rails job queue fiber-based is another. People and AIs take shortcuts An agent or a person that’s in a hurry or doesn’t fully understand your architecture takes shortcuts. The shortcuts work. They pass tests, implement features, and cross your boundaries. Months later, you realise your beautifully crafted architecture is now a patched mess. Or, perhaps, you’re starting a new project and you want to ensure that the agent is using a good architecture, without having to police… No comments yet. Log in to reply on the Fediverse. Comments will appear here.