Your code occupies one layer. You write a declaration: a SQL query, an HTML element, a type annotation. The declaration crosses a boundary into the platform, where it expands into imperative steps that you did not write, do not maintain, and do not need to understand. The platform layer is written once by specialists, tested exhaustively, and shared by every developer who uses the declaration.
The imperative layers are not gone. They exist inside the platform. The query planner still evaluates index options. The DOM engine still lays out elements. The type checker still walks the AST. The work happens; you just do not do it. Every line of imperative code you do not write is a line you cannot get wrong.
The declarative principle is not about doing less work. It is about declaring the outcome and letting tested, proven, platform-level code handle the implementation. This is the principle that unifies every chapter of this book: pure functions declare a transformation, typed data declares a shape, supervision declares a recovery strategy, composition declares a pipeline. In every case, you say what. The platform handles how.