HNHiroyuki Nakahatainblog.iroha1203.dev·16h ago · 19 min readThe SAGA Theorem: The Day Software Architecture Became Genuine Algebraic GeometryTL;DR Every module passes review, yet the system as a whole is broken. This "locally correct, globally inconsistent" phenomenon has a name in mathematics: cohomology, specifically H^1. AAT (Algebrai00
HNHiroyuki Nakahatainblog.iroha1203.dev·May 31 · 19 min readAtom Is All You Need: Read a Codebase as an Atom Map, Not a Dependency GraphTL;DR In the AI era, architecture analysis cannot stop at reading code as files, functions, imports, and dependency graphs. We need to observe the smallest units that carry architectural meaning. I ca00
HNHiroyuki Nakahatainblog.iroha1203.dev·May 22 · 14 min readForecast Cone: A Grand Theorem for Computable Software EvolutionTL;DR This article starts from the ForecastCone in Software Field Theory (SFT), then reads modularity, technical debt, review, governance, and learning as parts of one research program. The goal is si00
HNHiroyuki Nakahatainblog.iroha1203.dev·May 13 · 20 min readSoftware Architecture as a Field: Asking Better Questions About Software EvolutionAI coding agents are making us faster at writing code. That is a major shift. But writing code faster is not the same as helping software evolve in a healthy way. The faster we stack up changes, the m10
HNHiroyuki Nakahatainblog.iroha1203.dev·May 11 · 18 min readAI Agents Don't Need Meetings: Gotanda Style for Stigmergic Software MaintenanceMost multi-agent systems make agents talk to each other. We tried something different: our agents do not talk to each other at all. They leave traces in a shared environment. Other agents read those t00
