Playability:
Difficult without a tutorial to guide people through the basics. Would definitely check out Grey Hack for inspiration here. Love that you showcased IoT devices and moving through them.

Theme:
Fits the theme well in that the game is all about surveillance and perception.

Cleverness:
Really awesome game concept here. I think it just needs some time to smooth out rough edges for players. Good work overall.

Artistic Style:
Simple models and consistent design. Nice work.

I err....didn't manage to do anything....I read the instructions and tried different inputs but I was comprehensively defeated. As others have said a tutorial or just a initial indicator or example to get me going may have helped. It looks interesting and I like the concept - would have liked to have got past the first camera. Well done on putting it together though!

Seems like a game for smart people, so I am not the target audience. I tried my best reading through the instructions and trying all the different code inputs but I just couldn't figure out how to do anything. I don't use terminals that much irl anyway so I'm already at a disadvantage. 

Maybe if there was a tutorial and made a bit easier it could end up being a very fun game.

Cool game, I liked how it makes you feel like a hackerman (Kung Fury meme).

Some feedback:
* Calling felt pointless, it takes as much time to write the call command than hack command, up and rename "hack" to "access". I couldn't control the cameras, so it was rare to see them on camera when they received a call. Most network cameras are pointed inwards to some area, so even if they are at the other end of the park, they are out of the range for the call. More often, they were behind the network camera view, but those cameras see only one way. I wish network cameras had mouse control and some could be even 360 cameras.
* I couldn't figure out how to set up an alias that executes 2 commands with parameter, like "hack -r 123 & access -r 123" as "ha 123". Updating the alias for id each time is slower than setting "alias hr hack -r" and "alias ar access -r" and then just executing "hr 123" and "ar 123".
* Camera skipped frames every time I executed a command. A bit annoying.
* Phone cameras seemed to be too much in front of the characters, so they clipped through walls before turns.
* After capturing 5 targets, I got "Victory Achieved!" message, next target and then game froze.
* It doesn't remember my aliases the next time I visit the page.

It seemed they all followed the same trajectory, so I hopped on one, drove to the church and then executed list, hack, access, download, curr commands while they did their circle inside of the church, then hopped on the next one coming into the church. After getting all the names from everyone, I went to the networked park camera in the middle of the city and executed list command as long as I noticed my next target.

It's a cool idea, but definitely something that requires a lot from the player without a proper tutorial to give them an example "first catch". I tried to give it a fair shake, and I am a sucker for CLI's in my normal day to day work, it's just not exactly obvious to me what I'm attempting to do. Even something as simple as swapping to a new camera was something I couldnt do in a couple minutes. I'm sure some part of that is a skill issue on my end, but I think part of it is the project itself may have been too ambitious for a game jam.

For the positives though I did like the story write up on the game itself, definitely some good flavor there!