Substance over hype. The operator filter: name the substrate, refuse the rebrand.
In 2018, I was running V2 Games. A blockchain startup. While writing that blockchain was a database innovation with better marketing. Money was on the table. The category was being hyped by people with aligned financial incentives. The honest read still said: real substrate, borrowed framing. That tension is the whole thing. The procedure is not contrarianism from the outside. It is honesty under financial exposure.
Reduce any hyped category to its substrate, then evaluate. Name what it actually does at the layer below the brand. If the substrate is genuinely new, the excitement is earned. If the substrate is borrowed technology with a better-sounding name, refuse the frame. Applied consistently over eight years and four distinct hype cycles, this produces a record.
The procedure across four cycles
2018: blockchain as database innovation. "Blockchain is a database innovation first, which can be used to improve a lot of processes." Written while running V2 Games, under real financial exposure to the category. The ICO extension followed immediately: "Somewhere in between blockchain and ICO, the product is getting lost. ICO is a funding tool which helps visionary teams build product for the future." Separate the funding mechanism from the product claim. Conflating them is the most common failure mode in a category hype cycle.
2020: no-code as UI layer, not paradigm shift. The no-code wave arrived with claims of democratizing software development. The substrate test: what does it actually let practitioners do that they could not do before, and at what fidelity ceiling? No-code tools shipped faster time-to-prototype for low-complexity workflows. They did not shift the ceiling for production systems under real load. The category was real. The paradigm-shift framing was not. Evaluated and constrained accordingly.
2023-2024: GenAI as genuine substrate change. "Almost everyone believes GenAI is overhyped. Yet there is something magically different from other techs that were hyped and never lived up." The substrate test passes here. GenAI radically reduces the cost of cognition at scale. That is genuinely new. The hype is earned. The 2018 callback is intentional: the same test, applied with the same rigor, produces a different verdict when the substrate is actually different. The procedure is not contrarian by default. It is honest about what is new.
2025: anti-customization as cost accounting. "Every customization setting is a design decision deferred to the user." The hype-word is "flexibility." The substrate is implementation cost: six months of integration work, an implementation partner, hundreds of training documents to configure a system a vendor marketed as plug-and-play. The flexibility claim is not false. It is incomplete. Fully accounting for the cost changes the ROI calculation for every enterprise procurement decision that accepted the flexibility framing uncritically.
Why this is the root
Every theme in the knowledge graph applies a version of this procedure to a specific domain. Agent-first applies it to AI architecture: agents as substrate, not chatbots with UX skins on top. Enterprise AI reality applies it to deployment: demo versus production as the real test. The PM taste theme applies it at the PRD level. Anti-customization is the same disposition executed at the product decision layer. Breadth as differentiation applies it to career strategy: Human-GPT integration as the failure mode of breadth without a real substrate underneath.
The eight-year through-line is what makes this more than a stylistic preference. The disposition was enforced inside categories, not just from outside them. Operator discipline at B2B scale requires the same move: evaluate the substrate, not the label. The label rotates every eighteen months. The substrate evaluation procedure does not.
The question worth asking
The harder version of this procedure is applying it to yourself. Not "is this category overhyped?" but "is my own conviction about this category substrate or rebrand?" The cases above held up because the analysis was written down before the market resolved. Not after, when it would have been easy to claim the obvious read as a prior belief. If you're in a hype cycle right now and haven't written down the substrate argument yet, the question is whether you're applying the procedure or just pattern-matching to the contrarian position, which is its own kind of rebrand.