AI assistance disclosure: This article was drafted with the help of Claude. All technical content, design decisions, code references, and screenshots reflect production systems I designed and operate at airCloset; the prose was revised by me prior to publication.
Hi, I'm Ryan, CTO at airCloset (a fashion-rental subscription service based in Japan).
"Everything changes with AI" is the prevailing mood. My experience building and then running an internal AI platform (cortex) points the other way. The principles don't change at all. Only the machinery does. This post is about what I've come to treat as principle, what I've concluded should be broken, and the thinking behind that split.
Disclaimer: "cortex" in this article is the internal codename for the AI platform built in-house at airCloset. It is unrelated to existing commercial services like Snowflake Cortex or Palo Alto Networks Cortex.
I've written about the individual pieces before: code-graph, product-graph, db-graph, biz-graph, AI-Observability, the auto-review harness, and Self-Healing. This post isn't about any of them. It's about the design principle sitting behind all of them, one abstraction level up, more essay than build log.
