EPIP- Eternal Public Information Protocol
Ordering Officer: First Python Pyre Glorison | Classification: Public, no Redactions.
Purpose
To establish a permanment record of events, programs, projects, missions, and protocols available to all Pythonix Members and the general public on a classification scale basis.
Method
In order to have the clearest records available, the following classification system, along with recording procedure are to be immediately established. All records are to be stored in three locations, one of which must be a widely available digital drive, another must be a printed copy stored appropriately to prevent weathering. No one should be able to delete these records in the digital drive, but anyone should be able to create a record and upload it with ease.
Events
Put into calendar format of Day/Month/Year (XXXX). In a seperate document, provide brief description of event's intended purpose, and debriefing of actual occurance of event. Classification to be stated at the beginning of the documentation. Requires title.
Programs
Put into date range format of Day/Month/Year - Day/Month/Year, with an approximation of how many days the program was consistently followed. Statement of what the program was to achieve while in operation, alongside weekly reports of reached goals and adjustments required. Classification to be stated at beginning of document. Requires title.
Missions
Put into date format, or date range format where applicable. Statement of mission goals, personelle sent, guidelines for engagement, and signing officers to be in list format. Statement of debrief to be attached upon mission completion, alongside gathered intel/achieved goals statement. Requires classification and ordering officer to be stated at beginning of document. Requires title and/or success/unsuccessful declaration at top.
Protocols
Title required, ordering officer signature required. No date required. Must outline Purpose and Methods, and Compliance Assurance. Requires classification at beginning of document. Must clearly outline expectations and is intended for Programs not intended to have an end date. Monthly compliance reports to be created and attached to founding document.
Members writing or editing a given report may make comments at the bottom in the "Recorded Comment" section. This is optional, no comment is needed. No justification is needed.
Classification
Classification is defined as a scale of censorship before it is ready for public release. The following outlines the levels of classification
Public, No Redactions - whole document is available to public, no information is deemed to be sensitive or volitile to Pythonix interests and operations.
Public, Mild Redactions - Very little of the document is redacted, such as names, places, or comments made off-handedly that could be considered offensive to public interest or the interest of Pythonix.
Public, Major Redactions - Document has heavy redactions, information is considered sensitive, volitile to Pythonix operations and interests. Redactions may be made in the interest of public protection.
Private, Pythonix Only - Only Pythonix members may read the document, document may or may not be redacted. Document is not to be discussed with non-member parties, including civilians, hostiles, or neutral parties.
Private, Second Python or Higher - Only Pythonix members of the ranking Second Python or higher may read the document. Document is not to be discussed in public forums, including but not limited to; Public Access Dens, Pythonix Member Stores, Armouries, and Private Multi-Member rooms.
Private, First Python Only - Document is either in draft, or considered too volitile to release. Only first Pythons may discuss or reveiw document, and must do so in approved secured locations. These documents are not to be discussed anywhere else.
Redacted information should not be retreived under any circumstances. All documents must become "Public, No Redactions" fifteen years after their creation date and release from "Private, First Python Only" status.
Only fifteen documents at any given time should be "Private, First Python Only".
Compliance Asssurance
In order to assure compliance with this new protocol, education courses will begin on reporting within the first week of this protocol's release. Beyond that beginning week, any report submitted not within compliance will be reported as "Incomplete" and member responsible will be reminded the first three times to make corrections. On the fourth attempt to remind of the need for compliance to this protocol, the member responsible for the report will be reprimanded. Suggested reprimands include: Cleaning barracks, cleaning weapons, doing Headcount, clearing out livestock stalls, assigned solely to public program tasks, assigned to weekly safety breifings, and others of greater severity so long as the record compliance is lacking. Once report is submitted within compliance, member responsible will be released from reprimand.
Recorded Comment:
This is the first record of its kind. I specifically formatted it exactly like I expect it to be done, and will be creating other example documents using previous missions, events, and programs to illustrate how they are to be formatted. From here on out, this is how we do things. We will not lose our records again, we will not lose anyone because of a lack of knowledge again. -FP Pyre Glorison
SIGNED BY
PYRE GLORISON
FIRST PYTHON