Shielding Constructs

 Your base construct must be easy to program, but hard to be deprogrammed and scanned by others. New layers should be easily added. This can be done by thinking of a codename, then programming the "codename" itself. This tells your mind that you are assigning these attributes to the name, meaning you could just add energy to the name, and your construct will start taking its shape. Now, you can call it using the codename. After calling the construct, you should be able to automatically add new layers if the need arrives. 

For people who've just started venturing into shielding constructs, here's a basic shielding construct from Psi Palatium.

Addition of multiple layers might take a while, and extreme amounts of time. If you wish, you can add an outer layer that adds extra protection and interfaces all of the intents of the previous layers at once. Though focus on learning how to create basic shields and test them if you are a beginner. There might be a layer limit, which is when your construct goes bonkers, but that should be able to be fixed with proper focus.

Below is a list of possible "layers" you may use to build your shield with. Make sure to link them appropriately to create your all-purpose shield. It might look overwhelming at first, but taking your time with it is all that's required. I use the word "modules" to describe basic constructs that only make sense when they are added to the main construct. 

Layer-interface module - takes all of the intent layers and "activates" them on the main protective layer.

Energy-absorption construct - takes energy from outside or other people to power the construct in its entirety. 

Witchcraft/Astral shielding module - Defends against Astral constructs & other abstract influences. It must be able to adapt to different intents. An adaption layer can be added as a different layer altogether for simplicity sake.

Construct shielding - must defend against more direct/piercing intent, especially constructs.

Basic deprogramming protection - must be able to defend itself against basic deprogramming.

Anti-scanning protection - defends itself against readers, scanners and clairvoyance. 

Advanced deprogramming protection - must be able to defend itself against complex deprogramming and other deprogramming constructs.

Intent-deprogrammer - scans incoming influences and deprograms them before they can cause any problems. Scan module might have to be made separately.

I'm fairly new to programming, but most of my constructs work more often than not.