Admitted, not assumed

Not everything in the system is yours. A reset normalises the browser's defaults; a vendor library brings its own opinions wholesale. The question is where such borrowed code sits in the cascade — and the answer is at the edges, admitted on purpose, never assumed into the foundation.

Resets come first and lose to everything; that's the point — they clear the ground, then get overruled by every layer that follows. Vendors come last and win in their own scope; also the point — you opted into the library's opinions, so within its components it gets the final say. Neither belongs in the middle, where your vocabulary lives. Pull vendors/ out and the system is still whole, because nothing depends on it: it's an enhancement, not a load-bearing wall.

The word that matters is admitted. Borrowed code is let in deliberately, with a known place and a known reach, not absorbed in silence into the base. A reset is off by default and switched on when a form genuinely needs it; a vendor is sandboxed to the components that asked for it. You can always name what you took, and where its authority ends.

This is the same honesty the rest of the grammar asks for, pointed outward. A folder should tell the truth about its role. Foundation code earns its authority by being depended on; borrowed code earns its place by staying at the edge, where its opinions can't quietly become yours.