1,054
edits
Master Number Code: Difference between revisions
no edit summary
(Created page with "Master Number Codes are given to create security transmission between the user and Guardian Host Network, to unlock chakra seals for frequency access and integration, and to i...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
Paraphrased from Pages 191 -192 HGS Manual | Paraphrased from Pages 191 -192 HGS Manual | ||
==Also:== | |||
In the context of a HGS session, a Master Number Code (MNC) may be generated as personally guided through the practitioner HSP in a multitude of ways for use to secure the session content. It is through personal HSP this code may be generated, so it is always unique to the user. For those reasons only guidelines can be provided here that describe more detail of how MNC are used in a HGS session: | |||
1. To create a IP address for the session to be linked into and secured through a specific “line” or location. Like an internet address, the number generates an address which is placed at a location of the field where the HGS Mentor band can keep the session content secure for the needed duration. This may also work like a cell phone with getting a dial up number. This may be at any time during the session. | |||
2. To create the energetic amplification for the necessary clearing/event within the communication link connected from a higher dimensional space. Sometimes the user location cannot be accessed with necessary broadband strength from the point in the field that the HGS Mentor Band has an access, which stems from a multitude of environmental or energetic factors. (interference, ELF disturbances, communication link blockage, gamma rays, atmospheric condition, etc.) | |||
3. To create communication link which may be used for observation, re-coding the Instruction set (Morph field), or group class or case study in another dimension for Krystal Host. Case studies can be required when architectural damage in the field require specific problem analysis. Our HGS Teams provide this case study upon performing certain sessions. This is to increasingly strengthen and perfect the architectural template within the group efforts and the HGS Field instruction sets from the ground crew level (us) and as they link into multiple other domains under Krystal Star hosting. | |||
4. Personal lightbody recoding sequences, MNC may be for securing body parts, ie. Chakras, 12 Tree Spheres, Crown Chakra, etc. | |||
5. Planetary lightbody recoding sequences, MNC may be used for securing Stargates, Spheres, Vortices, Ley Lines, and Pylon Networks for communication with and between parties for the Krystal Host. | |||
6. Dial up line to various Ascension or Planetary Templar Teams that have certain expertise with the session content. Secure Data transmissions for any Krystal communication station. | |||
Since the MNC is generated for secure session and energy lines it is highly probable that the best course of action in general terms, is to keep the MNC personal to the user. HGS is spiral in nature, and the MNC field collapses when session is closed, it is generally undetected within a “closed” session content that is shared after the fact. So sharing the MNC code to the public may defeat the intention of why the code was generated, for any multitude of purposes. | |||
So for general guideline, when a MNC is generated within a session content, keep it private or internalized. | |||
==Reference== | |||
HGS Stewards Discussion | |||