I wasn't trying, with this article, to define "details". I don't think I need to, and I don't think I can, concisely. I don't want people to remember only *rules*, and forget the principles. :)
As for "implementation choices", I think that's quite specific, but I didn't define it. I mean specifically the choice of implementation class. In other words, if a few of your controllers depend on a CustomerRepository interface, then the "implementation choice" in your entry point might be SpreadsheetBasedCustomerRepository or HibernateBasedCustomerRepository. I hope this clears that part up.