*Note that this document is part of Imperial Law, and should be treated as such.Guide Outline:
Introduction to Imperial Protocol
- Introduction to Imperial Protocol
- Article I: Standard Protocol
- Article II: Correspondence Protocol
- Article III: Imperial Meetings Protocol
- Article IV: Foreign Relations Protocol
For a government as highly organized as the Galactic Empire, protocol is an essential document to follow. Protocol is the standard way an Imperial should act and behave whilst performing their duties for the Empire, and also show the Empire as the organized, unified organization that it is. Therefore, Emperor Karl von Roma has decreed that all members of his Empire are to follow the standard protocol of the Galactic Empire.Article One - Standard Protocol
It is the duty of all Imperials to follow standard protocol. They must:
• Report any conversation which is hostile to the Emperor or the Empire to the Imperial Security Bureau. The investigation will be taken up by officials. Investigations not authorised by the Imperial Security Bureau violate Imperial Law, and anyone found performing them will be punished accordingly.
• Report any unauthorised requests/interrogations for classified information to the Imperial Security Bureau. If you have any doubt whatsoever about an official requesting information, refuse to cooperate in a polite manner and seek clarification from your commanding officer or the Imperial Security Bureau.
• Report any conversation/action which is disrespectful to another Imperial to the Imperial Security Bureau. Punishment will be issued as the ISB Director General/Emperor sees fit.
• Follow standard salutation protocol. You must:
The Emperor/Regent - Kneel or Bow
The Empress - Salute or Bow
Executors - Salute
Moffs/Grand Moffs/Supreme Moffs - Salute
Superior Officers of the Imperial Military - Salute
Superior Officers of COMPNOR - Salute
Ministers - Salute
Directors - Salute
• Refrain from spreading rumours and information which is not known to be true. Members of Imperial High Command will distribute information as and when necessary.
• Follow the Emperor’s will on relationships. Members of the Imperial Royal Guard and the Imperial Inquisition are to remain celibate throughout their lifetime, unless the person in question has direct consent from the Emperor himself to be part of any relationship, bear any children etc.Article Two - Correspondence Protocol
Correspondence (Email, message boards, XBL Messaging etc.) within the Empire also follows strict protocol. Punishments may be issued to those who deviate from the protocol set down.Email/XBL Message Protocol
All internal emails of the Empire, that is to say emails which are sent from one Imperial to another Imperial, are to use the following template:
To: [Main recipient of the e-mail]
CC: [All secondary recipients if applicable]
From: [Sender's Identification. Include Rank if applicable]
Subject: [The basic subject of the e-mail]
[Proper Salutation (Rank and Name for superiors (Sir/Ma'am can also be used), rank alone for subordinates],
[Body of the e-mail]
Please contact your commanding officer if you have any questions regarding email protocol.Message Board Protocol
All message boards needed will be supplied on the main Imperial site. No off-site boards are to be created without express permission from the Emperor. If you require a new forum to be created on the message boards, please contact an administrator.
Note that on Imperial message boards, you must use your official Imperial Avatar and Signature, which can be requested in the 'Graphic HQ' forum. More details can be found there.In-Character Messages
In-Character messages are generally used in roleplaying posts. They are called 'ScanDocs'.
From: [Rank] [Name], [Branch], [Sub-branch*], [Unit assignment+]
To: [Rank] [Name], [Branch], [Sub-branch*], [Unit assignment+]
Subject: [Subject of message]
Context: [Action code]; [Security item]; [Response item]
Phasecycle: PSEG[A set of ten random numbers]; [days/hours/minutes BMUT]; [days/hours/minutes RMUT]
* If applicable
+ Provided the assignment is not classified to the recipient
Each field has a specific purpose, and should be filled in correctly. Note that these scandocs can be used in any IC situation – they are designed to be extremely secure, with very little chance of successful decryption.
From – The sender of the message (Including rank, branch, sub-branch [If applicable] and unit assignment [provided this information is not classified to the recipient]).
To – The recipient of the message (Including rank, branch, sub-branch [If applicable] and unit assignment [provided this information is not classified] to the recipient).
Subject – The subject of the message.
Context – Usually consists of three parts - an ‘action code’, a security item and a response item. Messages may only use one action code, one security item and one response item. Here are the possible action codes, security items and response items:
AOPT – The orders in the message are optional. The sender expects the recipient to use his/her best judgement to deem if the actions are necessary or not.
AADV – The orders in the message are ‘advised’. There is significant pressure from superiors for the orders to be followed, but they have not been made mandatory. The recipient must use their best judgement and decide if they should be carried out or not.
AMAN – The orders of the message are mandatory.
AEXC – The orders of this message are to be carried out exclusive of everything else – they are of the utmost priority.
PERS – The message and its contents are restricted to the recipient only. No one else is allowed to know.
IMMD – The message and its contents may be shown or disclosed to the necessary superiors and subordinates only of the recipient.
USYS - The message and its contents may be shown or disclosed to any superior of the recipient.
DSYS – The message and its contents may be shown or disclosed to any subordinate of the recipient.
ASYS – Any Imperial may be allowed to see the message. Usually only reserved for public transmissions.
ROPT – A response to the message is optional.
RMAN – A response to the message is mandatory.
Phasecycle – The software which is used to send an Imperial Scandoc is dynamic – it constantly changes to avoid any sure-fire decryption methods being discovered. Similarly, an Imperial Scandoc itself is similarly modified to avoid decryption by unauthorised persons.
PSEG – PSEG is a set of numbers which the scandoc software uses to decrypt a scandoc for viewing. Only the software which has the relevant PSEG (IE: The scandoc software which the recipient uses) can decode the scandoc’s encryption. Guessing a scandoc is next to impossible – and often, by the time it is guessed, the message will have mutated so much that the message will become unreadable (more on message mutation to follow).
Imperial Scandocs have the option to ‘mutate’ – they slowly but surely scramble themselves so that eventually they will become useless. This is to prevent messages falling into enemy hands if the recipient forgets to delete the message. There are two parts to a mutation:
BMUT – This tells the recipient how long until the mutation of the message begins. It is measured in days, hours and minutes. For example: 01/03/32BMUT means that the message will begin to mutate in 1 day, 3 hours and 32 minutes from being sent.
RMUT – This tells the recipient how long between each mutation, in days, hours and minutes. After several mutations, much of the message will be unreadable. It will be severely scrambled, and virtually impossible to reconstruct. For example: 01/02/07 means that the message will mutate every 1 day, 2 hours and 7 minutes. Generally, after five mutations, a message will be totally destroyed.
Note that these mutations are generally only used with top secret messages, or messages to those who are out in the field. Simply do not include them if they are not needed.
More information can be found in the 'Imperial Information Network' forum.>IRC Protocol
IRC is the most common form of communicating with fellow Imperials. Therefore, it is extremely important that this protocol is taken into account. You must:
· Behave as an Imperial. Fighting, arguing and petty squabbles are not deemed Imperial behaviour, and therefore must be avoided.
· Always do as a channel operator (A person with an @ next to their name) says. Channel operators have a duty to maintain order within the channel. Their status can and will be removed if it is abused.
· Always do as a member of the Imperial Security Bureau says. Members of the Imperial Security Bureau are appointed to help enforce channel rules, and therefore they must be respected. Complaints regarding the ISB are to be sent to the ISB Director General.
· Always salute upon entry if superiors are present, and kneel or bow if the Emperor is present.
· Always salute a superior if they enter the channel, and kneel or bow if the Emperor enters the channel.Article Three - Imperial Meetings Protocol
At an Imperial meeting, you will be required to follow a special type of protocol.
• Ranks must be displayed (using acronym form if the rank is too long). For example, Captain Gilad Palleon becomes CAPT_Palleon during a meeting. Contact your commanding officer if you are unsure of your rank's acronym.
• When you wish to speak on a topic, you must Request the Floor - this is done by saying "RTF". Also, give a brief summary of what you wish to speak about. For example, "RTF - Ship Assignments in the First Assault Fleet".
• When you have finished speaking, you must Yield the Floor. To do this, simply say "YTF" when you have finished what you are saying.
• If possible, have any pre-planned material that you know you must report on typed out and ready to copy and paste in order to save time.
• During meetings, gestures such as bowing, saluting and kneeling are suspended until the meeting has concluded.Article Four - Foreign Relations Protocol
In Character contact with enemies of the Empire is forbidden. Only authorised members of the Empire may contact the enemy. Also, remember that you represent the Empire. You must therefore act as such. Treat enemies and allies alike with OOC respect.