The Documentation Classification & Standards Handbook (DCSH) establishes the official standards for document classification, portion-marking, headers, distribution controls, and record lifecycle management across the League military. While issued by League Naval Intelligence, the handbook governs documentation standards for all three service branches, as any military document or communication may fall under LNI purview.
The current version (3.7) was ratified in CY 2687 under the authority of Fleet Admiral Alastair McKenzie, Director of League Naval Intelligence.
The League uses a six-tier classification hierarchy:
| Level | Marking | Description |
|---|---|---|
| Θ-BLACK | Θ-BLACK | Special Access Programs (SAP) - LNI only |
| TOP SECRET | TOP SECRET | Grave damage to League security if disclosed |
| SECRET | SECRET | Serious damage to League security if disclosed |
| RESTRICTED | RESTRICTED | Operationally sensitive information |
| OFFICIAL USE ONLY | OFFICIAL USE ONLY | Not for public release but unclassified |
| Unclassified | UNCLASSIFIED | Public-release material |
Classification levels derive from three factors:
The formula is: [HIGHEST FACTOR] + [COMPARTMENT IF APPLICABLE]
Every League Naval Intelligence record begins with a standard header block, is justified by a Classification Authority Block (CAB), and ends with a standard footer.
The first (cover) page carries the complete pedigree of the document:
LEAGUE NAVAL INTELLIGENCE
[CLASS]//[COMPARTMENT]//[HANDLING]
[DOCUMENT TITLE] ([CLASS])
Version [X.Y] – Effective [DDD.YYYY]
DTG: [DDD.YYYY.HH:MMZ]
Originator: [UNIT / OFFICER] (OCA if applicable)
Serial: [YYYY-ORGCODE-NNNN]
Classified by: [Rank Initials Surname], [Title] (OCA)
Reason: [Directive & paragraph]
DECLAS: [DATE or CONDITION]
DISTRIBUTION: ACTION: […] INFO: […] EXCLUDE: […]
The elements of the CAB are:
DDD.YYYY.HH:MMZ format; never in local timeLNI-[ORGCODE]-YY-####Cover pages are unnumbered or carry a Roman numeral "i" per house style.
Subsequent pages require a running header:
| Line | Left-aligned | Right-aligned | Notes |
|---|---|---|---|
| 1 | LEAGUE NAVAL INTELLIGENCE (optional) |
vX.Y (if applicable) |
Line 1 may be omitted if the document isn't subject to revision control |
| 2 | Short title | Effective DDD.YYYY (if applicable) |
If Line 1 is omitted, move the short title to Line 1 |
The Effective Date is the point after which the document's guidance or information is considered actionable:
On all pages except the cover, the following footer is required:
| Line | Left-aligned | Right-aligned |
|---|---|---|
| 1 | [CLASS]//[COMPARTMENT]//[HANDLING] |
Page C of D |
| 2 | [Master Page Template Revision] | [Serial] vX.Y |
Consistency allows all officers handling materials to recognize the classification and handling requirements at a glance.
The current Master Page Template is LNI Form 2290 (Rev 2687).
Internal annexes that begin on a new page repeat a mini-header (not a full cover):
LEAGUE NAVAL INTELLIGENCE
[CLASSIFICATION]//[COMPARTMENT]//[HANDLING]
Annex B - Sensor Tables (S)
The CAB is not repeated; it remains valid for the entire document set.
All narrative text, tables, graphics, and captions shall bear an individual portion mark:
(TS) Fleet jump vector …
(R) Asset B-6 reported …
(U) See annex for glossary …
Approved Exceptions - Portion marks may be omitted when all of the following are true for the block in question:
| Exception | Allowed When | Required Indication |
|---|---|---|
| Block-classified material | Consecutive paragraphs/rows share the identical level | Mark first line (S THROUGH S) (for example); resume marking when the level changes |
| Embedded source documents | A full, unaltered reproduction of an already marked document is inserted | Enclose in a bordered box or shading and label: INCL 1 - Pre-marked document (TS//STYGIAN//NOFORN). Do not add new portion marks inside the inset |
| Static forms & check-lists | LNI standard forms whose fields never mix classifications | Banner & CAB alone suffice; portion marks optional |
| Public-source extracts | Entire section is verifiably UNCLASSIFIED open-source text | Header line (U) Open-source extract follows - portion marks waived |
If any sentence inside an exception block requires a higher or lower level, restore full paragraph-by-paragraph marking.
The (X THROUGH X) notation reads "everything from here until the next portion mark is [LEVEL]." It eliminates redundant marks on each line while maintaining clarity.
The drafter is accountable for correct marking; security reviewers verify compliance during the program-audit cycle.
Certain information requires additional access controls beyond standard classification:
Project codewords follow the format: [PROJECT]-[ASPECT]-[ITERATION]
Example: NYX-PRIME-SEVEN
ACCESS: [COMPARTMENT]//[SUBLEVEL]//[READ-IN DATE]
VERIFIED BY: [AUTHORIZING OFFICER]
All League military communications use a standardized date-time format:
DDD.YYYY.HH:MM:SS.SZ or DDD.YYYY.HH:MM:SS.S.PTC
Zulu time is understood as UTC time and kept to honor military tradition. It is the only single-character PTC allowed. When using a three-letter PTC, a dot precedes the code. The Z suffix has no preceding dot.
Examples: 74.2687.14:35Z, 74.2687.14:35:30.5Z, 74.2687.14:35:30.5.UTC
When local time is required: DTG: 127.2361.27:32.NOR
If there is no relevant PTC, use LOC with a dash and the location name: 127.2361.09:15.LOC-JUNO
When specifying a year, include the appropriate designator (CY for Calendar Year, FY for Fiscal Year) in front of it. In cases where it may be ambiguous, place an Era designation afterward.
Examples: FY 2673, CY 1312 BCE
Classification alone does not guarantee proper protection: the drafter must also tell recipients who may read, copy, or forward the material.
| Marking | Meaning | Typical Use |
|---|---|---|
| EYES ONLY | Deliver solely to explicitly named individuals; no sub-forwarding | Director-level planning papers, personnel vetting files |
| REL TO [NATION/SPECIES] | Releasable to the specified ally on a need-to-know basis | Fleet liaison updates, joint exercise plans |
| NOFORN | Not releasable to any non-League entity | Sources-and-methods, Θ-BLACK annexes |
| ORCON | Originator retains final release authority; downstream copies require written permission | High-risk HUMINT traffic, draft policy options |
| PROPIN | Contains proprietary data supplied by industry under NDA | Vendor design submissions, tech-demo results |
Placement - Append dissemination markings to the banner line, after compartments, separated by double slashes:
SECRET//STYGIAN//NOFORN
Multiple markings may be chained (e.g., TS//DAEDALUS//ORCON//NOFORN). If mutually exclusive markings collide, the most restrictive governs.
A distribution list is mandatory for RESTRICTED and above and is strongly encouraged for lower levels when more than one office receives the document.
DISTRIBUTION:
ACTION: FLEETCOM LNI-OPS-SIG (primary)
INFO: LNI-LOG LNI-RAB (secondary)
EXCLUDE: CIVIL PRESS, UNREGISTERED FREELANCE
If a document is limited by EYES ONLY, list the individual billets instead of offices:
DISTRIBUTION:
EYES ONLY - ADM McKenzie, VADM Tenley, CDR N. Hayes
When foreign disclosure is anticipated, the drafter specifies what may be shared and under what caveats.
Marking Scheme:
REL TO [ALLY CODE] → May share with that ally (subject to restrictions)NO [ALLY CODE] → Explicitly forbidden to shareCombine with standard caveats as needed: SECRET//PANDORA//REL TO LYNDRI//NOFORN
(Above, Lyndri personnel may read; all other foreigners may not.)
| Ally / Partner | Approved Marking | Standing Restrictions | Notes |
|---|---|---|---|
| Lyndri Empire | REL TO LYNDRI | Exclude EIDOLON material | Long-term counter-piracy partner |
| NorAellian Hegemony | REL TO NORAEL | Technical data only; no Θ-BLACK | Shares jump-engine R&D |
| GikDaa Enclaves | REL TO GIKDAA | Case-by-case; prior ORCON approval | Mercantile outposts; variable reliability |
| Freelance Stations | NO FREELANCE | Unless waiver issued by DLNI | Broad category covering non-aligned habitats |
Record-Keeping:
Intelligence reports use a two-character code combining source reliability (A-F) and information credibility (1-6):
| Code | Reliability | Description |
|---|---|---|
| A | Completely Reliable | Proven source with 100% accuracy |
| B | Usually Reliable | Minor inaccuracies possible |
| C | Fairly Reliable | Has provided valid information previously |
| D | Not Usually Reliable | Significant doubt about authenticity |
| E | Unreliable | Known to provide false information |
| F | Cannot Be Judged | New or untested source |
| Code | Credibility | Description |
|---|---|---|
| 1 | Confirmed | Verified by independent sources |
| 2 | Probably True | Logical and consistent with known facts |
| 3 | Possibly True | Reasonable but unconfirmed |
| 4 | Doubtful | Possible but improbable |
| 5 | Improbable | Contradicts known information |
| 6 | Cannot Be Judged | Insufficient data |
Format: [SOURCE][CREDIBILITY]
Example: B2 = Usually reliable source, probably true information
All classified documents follow a defined lifecycle:
LNI distinguishes between Active records (supporting an ongoing program or operation) and Archived holdings stored with RAB.
| Classification | Program-Audit Interval (Active) | Historical Review Interval (Archived) |
|---|---|---|
| Θ-BLACK (SAP) | 180 days | 5 years - batch review |
| TOP SECRET | 1 year | 10 years - batch review |
| SECRET | 1 year (if program still live) | 25 years - automatic declass* |
| RESTRICTED | 3 years | 25 years - automatic declass* |
| OFFICIAL USE ONLY | 5 years | 25 years - automatic declass* |
| UNCLASSIFIED | Review optional | N/A |
*Automatic declassification occurs unless the compartment owner files an exemption with RAB at least 90 days before the deadline.
Failure to complete a scheduled program audit triggers an automatic Suspense Notice to the custodian's chain of command after 30 days.
Each drafter must embed a DECLAS line in the CAB: DECLAS: [CONDITION or DATE]
| Example | Meaning | Use Case |
|---|---|---|
DECLAS: 272.2737 |
Release on day 272 of 2737 | 50-year rule for routine SECRET material |
DECLAS: UPON CESSATION OF HOSTILITIES |
Event-driven release | War plans, battle logs |
DECLAS: OADR |
Originator-Authorized Declassification Review | Θ-BLACK and SAP files lacking a safe end-date |
Default DECLAS Timelines (when no directive applies):
When the DECLAS condition is met, records are sent to the League Historical Directorate per LNI Archives Instruction 44-02 or destroyed under Fleet Destruction Standard FS-11-3.
All documents undergoing revision must maintain a change log:
| Rev | Date | Auth | Summary |
|---|---|---|---|
| #.# | DDD.YYYY | [RANK] [INITIAL]. [SURNAME] | Brief Description |
Documents requiring version tracking:
| Document Classification | Minimum Authority Required |
|---|---|
| OFFICIAL USE ONLY | O-3 (Lieutenant) or GS-12 |
| RESTRICTED | O-4 (Lt. Commander) or GS-13 |
| SECRET | O-5 (Commander) or GS-14 |
| TOP SECRET | O-6 (Captain) or SES |
| Θ-BLACK | O-6 (Captain) or SES |
Task Force Commanders (O-7 and above) may authorize revisions for any classification level within their operational area. Joint Chiefs members may authorize revisions to any LNI document.
Individual documents should use their own version numbers starting at 1.0, independent of the handbook version.
| Agency | Designator | Liaison Protocol |
|---|---|---|
| Naval Operations | NAVOPS | Direct coordination |
| Marine Operations | MAROPS | Direct coordination |
| Spaceforce Operations | SPFOPS | Direct coordination |
| Local Law Enforcement | LAWENF | Through J-2 channels |
| Diplomatic Intelligence | DIPINT | Ambassador approval required |
| Technical Intelligence | TECHINT | Project-specific basis |
Terran Intelligence Sharing:
TERRAN EYES ONLY//[SPECIFIC AGENCY]When multiple agencies collaborate on a document, add to the header:
JOINT PRODUCT: [AGENCIES]
LEAD: [PRIMARY AGENCY]
POC: [CONTACT INFORMATION]
LEAGUE NAVAL INTELLIGENCE
SECRET//ORIGINATOR CONTROLLED
DTG: 142.2687.08:00Z
ORIGINATOR: LNI-STATION-PROMETHEUS
SERIAL: 2687-LSP-0456
SUBJECT: UNUSUAL SHIPPING PATTERNS - OUTER COLONIES (SECRET)
1. (U) SUMMARY: Analysis indicates irregular cargo movements.
2. (S) DETAILS: Commercial traffic analysis reveals a 23% increase
in unscheduled stops at Freelance stations. Pattern suggests
smuggling operations. Source reliability: B2.
3. (S//OC) IMPLICATIONS: Possible weapons trafficking to
insurgent groups. Further investigation warranted.
4. (U) RECOMMENDATIONS: Deploy additional assets for monitoring.
DISTRIBUTION:
ACTION: DLNI, NAVOPS-SECTOR 7
INFO: TASK FORCE 12, STATION PROMETHEUS
EXCLUDE: COMMERCIAL LIAISON OFFICE
SECRET//ORIGINATOR CONTROLLED
Page 1 of 1
LNI FORM 2290 (Rev. 2687)
LEAGUE NAVAL INTELLIGENCE
Θ-BLACK//EIDOLON//EYES ONLY FADM MCKENZIE
DTG: 15.2687.12:00Z
ORIGINATOR: PROJECT NYX DIRECTORATE
SERIAL: 2687-PDD-0001-NYX
SUBJECT: ENHANCED STEALTH FINDINGS (Θ-BLACK)
VERSION: 2.1
[Content would follow compartmented guidelines]
| Rev | Date | Auth | Summary |
| --- | ------- | ---------------- | --------------------------- |
| 1.0 | 10.2687 | CDR T. Singh | Initial draft |
| 1.1 | 11.2687 | LT J. Park | Corrected coordinates |
| 2.0 | 14.2687 | CAPT R. Chen | Added technical assessment |
| 2.1 | 15.2687 | FADM A. McKenzie | Final approval |
DECLAS: 15.2737
FLASH OVERRIDEPRIORITY IMMEDIATEPRIORITY| Rev | Date | Auth | Summary |
|---|---|---|---|
| 1.0 | 01.2687 | LT S. Fakename | Initial release |