Hack your commute, take public transit! Hack your next dinner party with parlour games. Delightfully clever key hack keeps all your keys on the same ring. Hack Mexican food with a "burrito" sized tortilla! Hack your brain with REM sleep. Hack the sun with a straw hat. Hack hygiene with silver oxide "deodorant". Hack girls with compliments. Hack your windowsill with a pot of wheatgrass, and hack the sky with the goddamn moon.
It's stupid. Take a walk.
Thus, learning to play guitar is not a hack, since it satisfies neither criteria, but learning to put some TP into the toilet first when you do #2 in order to prevent splashback is a hack.
When new things come out or new ideas emerge people just 'hack' them and viscerally create. Hey I need this form, bust it out. Hey I need this renderer, bust it out.
But later as things are more known you might abstract away and say let's take a step back and look at the architecture of this whole thing rather than bust it out in a prototypical fashion (usually because the problem is complex or stuff is broken and a maintenance nightmare with steep technical debt). You might even architect the plan for what prototypes you would make to help solve the problems.
So true things being architected are happening more frequently as a buzz but as systems mature that is usually what happens via abstraction to see the full picture.
Maybe the difference is a 'hack' is something I am doing right now until it works, almost a prototype. Then something 'architected' is what you would do when you think about it for a week or two before starting. Lots of software development for instance starts with hacks/prototypes then architects how to use those to go to production.
Both sides are representations of the poles of creating, of course you can go way beyond either side and eat some spaghetti hacks or go to space with some architecture astronauts.
I hacked my feet with shoes so I can walk for longer on rougher terrains.
Good idea ;-)