However, to the point of your blog post, there have definitely been others talking about when "technical debt" might be okay.[1] A big challenge is not only that people disagree on when debt is present, there really are multiple completely different definitions, and while some look a little like debt many don't behave like debt at all.
[1] http://agilefocus.com/2012/07/02/technical-debt-the-good-the...
(I wrote that post, but it also has lots of links to other people talking about different definitions of technical debt.)
So architecture is the important stuff when you think about the project, and tech debt are the things that don't fit how you think about the project.
To me, technical debt is about the trade-off of short term progress for long term flexibility of the code base. Essentially, the need of the business to ship -- side note: I wrote that as shit initially. Freud would be amused. -- the feature immediately outweighs the need of the business to write maintainable code. So, you expend fewer engineering resources than you should now and you spend more than you would have later. Basically, you borrow against the future productivity of your engineering team.
So, to me, it's about doing less work now and more work later. That can be a conscious decision or a consequence of ignorance. Things like choosing the wrong abstraction are about being ignorant of the problem space.
FWIW, I wrote a blog article a few days ago on TD, including times when it might be appropriate.
http://tiny-giant-books.com/blog/technical-debt-edge-cases/