HOW TO VERIFY LEAKED DOCUMENTS

THE AUTHORITY'S DOCUMENT NUMBERING SYSTEM

Every official Authority document has a unique serial number following this format:

Common Department Codes:

• DBM - Director/Board Memoranda
• BDM - Border/Checkpoint Directive Memoranda
• IA - Internal Affairs
• OPS - Operations
• HR - Human Resources
• TECH - Technical Services
• MED - Media/Communications

VERIFICATION METHODS

1. Cross-Reference with Authority Systems (For Insiders)

If you work for the Authority, you can verify document serial numbers in your own internal systems:

• Search the document ID in your classified database
• Compare classification levels (they should match)
• Check distribution lists (who received the memo)
• Verify signatures and approval chains

2. Check Metadata and Formatting

Real Authority documents follow strict formatting standards:

• Headers: Always include TO/FROM/RE/DATE/CLASSIFICATION
• Classification markings: TOP SECRET, LEVEL 7, RESTRICTED, etc.
• Page numbers: Format "Page X of Y" in footer
• Watermarks: Digital docs have embedded Authority seal watermarks
• Font: Official documents use Times New Roman 12pt

3. Corroborate with Other Evidence

Real leaks rarely stand alone. Look for:

• Multiple sources: Do other whistleblowers mention the same events?
• Timeline consistency: Do dates align with known events?
• Personnel verification: Are the named officials real people in those positions?
• Cross-references: Does the document reference other known files?

4. Challenge the Content

Don't just believe everything. Ask:

• Does this align with Authority behavior patterns?
• Is the language consistent with official communications?
• Are there verifiable facts you can check independently?
• Does the leak explain previously unexplained events?

RED FLAGS FOR FAKE DOCUMENTS

The Authority sometimes plants fake leaks to discredit resistance sites. Watch for:

• Too convenient: Makes Authority look cartoonishly evil
• Wrong formatting: Doesn't match official document standards
• Unverifiable claims: Can't be cross-checked with any other evidence
• Suspicious timing: Appears right after a major leak to muddy waters
• No document ID: Real Authority docs ALWAYS have serial numbers

SPECIFIC EXAMPLES FROM THIS SITE

Example 1: The Continuity Memo (2029)

Example 2: North Ribbon Deployment Order

HOW I VET SUBMISSIONS

When someone sends me a leak, I:

1. Verify the source: Establish credibility through secure channels
2. Check the document: Format, metadata, serial numbers
3. Seek corroboration: Do I have other evidence supporting this?
4. Test with insiders: Can Authority employees confirm in their systems?
5. Wait if uncertain: Better to delay than publish fake material

FOR AUTHORITY EMPLOYEES READING THIS

You can verify every document on this site yourself. Here's how:

1. Note the document serial number from any page on this site
2. Search it in your internal classified database
3. Compare the content
4. Ask yourself: Why do they claim this doesn't exist when it's in YOUR OWN SYSTEMS?

ADDITIONAL RESOURCES

Security Practices for Whistleblowers - How to leak documents safely without getting caught

Submit Evidence - Secure channels for sharing documents with me

Browse Leaked Documents - See the evidence for yourself

---

"The truth doesn't need to hide. Only lies do."
— Elena Vasquez