The Doc Doctored The Docs
The Document That Proves the Opposite
A forensic breakdown of the DD-214 Salla hosted on his own site instead of filing a FOIA request
This article is not an attack on anyone's beliefs. It is a direct look at the one document Salla has ever produced to support JP's military background — hosted from Salla's own site, not the government — and what happens when that document is actually examined.
This stands out because JP is Salla's main money maker, with years of books and webinars behind him, and he regularly draws backlash over his source's credibility. One simple action — the same action Salla has taken for other sources — could settle the question quickly and permanently. Salla has never taken that action.
A commenter presses Salla directly on the missing FOIA and the self-hosted document. Tap to enlarge.
The original December 2025 reveal video — confirming this is the same document still being pointed to in August 2026. Tap to enlarge.
The Evidence
Everything below comes from the document and the file itself, checked directly — not relayed secondhand.
Seven Flags
Looking closer at the document itself, before any technical explanation is applied:
Flags 1 through 3 marked directly on the document. Tap to enlarge.
Only three locations appear anywhere on the form, and none of them are Eglin. The unit line reads a generic GSSC SFG SP — "SFG" meaning Special Forces Group, but with no number attached. A real discharge document legally specifies the exact unit, such as 7th SFG or 1st SFG. A generic, unnumbered "SFG" is the shortcut someone takes when they don't know the exact administrative naming codes real military personnel software uses. Both Eglin and "7th" are the two central pillars of JP's testimony — and neither one is in the document meant to prove it.
Flags 4 and 5 marked directly on the document. Tap to enlarge.
The graduation certificate is the only place "7th Special Forces" and "Eglin" actually appear at all — the DD-214 never names either one. But a completion certificate only has a handful of fields built to change per graduate: the name, the date, maybe a class number, and the signature line. The course title itself is baked into the fixed template artwork, identical on every copy that template ever produces. If "Airborn e" were really broken apart in the master template, every graduate of that course would carry the exact same broken word on their certificate — and a visibly broken word on an official government certificate is exactly the kind of flaw that gets noticed, photographed, and passed around, not one that stays invisible for years. No one has ever flagged it, because it was never on anyone else's certificate to flag. It's on this one because it was built for this one.
Flag 6 marked directly on the document. Tap to enlarge.
The bottom line, without softening it: four of these flags — the off-grid headers, the floating checkboxes, and the broken "Airborn e" on the certificate — are the kind of printing and layout errors a real, computer-generated government form doesn't produce. The other two are different, and worse. The unit line reads GSSC SFG SP with no number attached — meaning whoever filled this in added the term "SFG" without knowing the actual unit designation real personnel software uses. And Eglin Air Force Base, the base at the center of his entire story, appears nowhere on the document at all. Those two are the specific claims this document was supposed to prove, and neither one is on it. That's before even counting Flag 7: the file's own metadata shows the same document, downloadable from Salla's own link, is built from eleven stacked image patches, not one clean scan — the full breakdown is below. Seven flags, seven dead ends, two documents. That's not a suspicious document anymore. That's a testimony baseline very likely to be void.
Flag 7: What the File Itself Shows
Everything above comes from reading the page. This section comes from opening the file itself — the same way any document keeps a hidden history most people never look at. This isn't a private claim: it's the exact PDF linked earlier in this piece, and the tools that read this kind of information are freely available. That's literally how this section got built — anyone can download the same file and run the same check.
One base picture of the page, plus 10 small pieces individually pasted on top. Three are the Social Security Number boxes — normal, expected redaction. The other seven sit over the Home of Record, Mailing Address, Nearest Relative, Member Signature, and the Official Authorized to Sign block and its date. Most of those fields are blank. Blank space doesn't need its own pasted-in image.
The file's own internal history log shows it built in Photoshop in September 2024, then reopened and saved again in a newer version of Photoshop in December 2025. A real scan gets photographed once. This file was worked on twice.
The file carries Photoshop's own ID chain, proving it was exported from an earlier working file, which itself came from an even earlier one. Neither of those is visible anywhere — only proof that they existed.
Saved at 72 DPI — web and screen quality, not the sharper resolution a legal document is normally scanned at.
What looks like redaction isn't. A real redaction tool deletes the underlying data; this file just paints a box over it in Photoshop, leaving the original content physically present underneath. And it isn't only used on privacy fields — the signature and authorizing-official block gets the same treatment, which makes no sense as privacy protection. A signature is supposed to be visible; that's what makes a document verifiable. The one field that would prove this document is real was covered the same way as the SSN.
There's a second problem sitting inside that same finding, separate from the fraud question. If the basic service really is real — and the pattern above points that way — then what's sitting underneath that failed redaction is very likely his actual Social Security number and actual home addresses, not placeholder data. A cover-up that doesn't actually delete anything means real personal information may still be sitting recoverable inside a file Salla himself is hosting and pointing people to. That's a live privacy exposure that exists independent of whatever the Special Forces story turns out to be — and it falls on whoever posted the file, not solely on JP.
Staying strictly inside this one angle — the file's technical structure, nothing else — this is what the file would look like if it had been faked. Built from patches instead of one clean scan. Two editing sessions over a year apart. The touch-ups landing specifically on the fields that would prove who authorized it, not scattered at random. A derivation chain reaching back to versions nobody has ever been shown. None of that proves what the real content should have said. But judged only on this angle — does the file match the pattern of what a fabricated document would look like on the inside — the answer is yes, on every point.
A note on the source: links can be updated at the source without the URL ever changing, so this file has been saved independently of the live link. If the hosted file changes shape after this analysis is published, that timing is itself worth noting.
The Real Anchor, the Fabricated Bridge
None of this requires arguing JP was never a soldier. The basic service — E4, four and a half years, water-mechanic role — is likely real. That's not the part being sold. What's being sold is what comes after it: the bridge from an ordinary discharge into Special Forces, into classified programs, into everything that follows from there. That bridge is the fabrication, not the service underneath it.
Both documents can't be genuine at once. A real DD-214 and a real certificate don't produce a typo a fixed template can't make, or a unit code that matches no naming convention at all. If one or both are fabricated, there are only two people this could be: someone who was never in the military at all, or someone who really was — an ordinary enlistment, nothing special — who built the Special Forces layer on top of a real, boring service record. The evidence leans hard toward the second one. He's said himself he enlisted for the money, needed a job — an unremarkable reason to join, not the kind of detail someone invents while building a legendary secret-operative persona from nothing. The DD-214 matches that ordinary story: real years of service, real rank, a real mundane job title. What doesn't match it is the layer stacked on top.
This is the exact shape named in Real Facts Anchor Fake: a fake story built entirely from invented details is easy to knock down. One built by gluing a fabricated claim onto a real, checkable fact is much harder, because disproving the fake part feels like it should disprove the real part too — and it doesn't. The real E4 record is the anchor. Special Forces, the classified world, and everything built on top of it is the part riding on that anchor's credibility without earning any of its own.
If Investigators Confirm It
If federal investigators or the National Personnel Records Center confirm exactly this — a real record for basic service, nothing matching the Special Forces and classified claims — the exposure isn't limited to reputation. This is an ongoing business — "US Army Insider Missions" — selling books, paid webinars, and ticketed appearances on the strength of that unverified Special Forces and classified-program background.
Using wire communications — the internet, online payments, ticket platforms — to execute a scheme defrauding people of money under false pretenses. Every digital webinar charge or subscription fee is a separate potential count.
Using the Postal Service or a commercial carrier to distribute materials furthering a fraudulent scheme. Every physical book shipped under a false military-reporting claim is a distinct potential count.
The Wider Pattern
Everything below places the evidence above inside the broader pattern around JP and Salla — real, useful context that strengthens the case, but resting on outside reporting rather than a file checked directly.
Three Tracks, One Person
This document analysis doesn't stand alone. It's the third independent method to land on the same conclusion about JP, and each one got there a completely different way.
Not one point but a handful stacked together: no FOIA ever filed despite doing it for two other sources, an E4 water-mechanic role by his own words, and two contradictory reasons for enlisting in the same interview.
Released three days after Cobra's most detailed medbed answer on record, one day after Cobra boosted that interview himself — built from recycled old conference clips spliced with fresh talk to fake a timely, independent reaction. That's the Opportunist playbook by the numbers. And a bed that reshuffles the body at the atomic level has no reason to need blood drawn out through cables in the first place.
The hardest of the three to counter, because it isn't behavior or comparison — it's the physical paper trail itself. And the one document he actually produced still never says Eglin, never says 7th, on top of six other flags — including the file itself being built from stacked patches, not a scan.
This isn't a one-off shape either. The Opportunist type is named directly in the framework Track 2 draws from: a storyteller wearing borrowed truth as a costume, no falsifiable depth of their own, riding the coattails of a bigger name to launder unearned legitimacy. The Manufactured Insider lays out the general playbook underneath that, and JP's case matches it almost line for line. A real credential — four and a half years, E4, MOS 91J — becomes the springboard for an invented one. The claim leans on tropes the community already trusts (Special Forces, Space Force, off-world medbeds) instead of anything original, so questioning it means questioning what the group already half-believes. And the one verification step that would settle it outright, the same FOIA Salla has used elsewhere, is the one step conspicuously never taken. In that framework's own words: selective verification, applied everywhere except the highest-stakes case, is itself a tell. Run against the six-tier Grey Hat Spectrum, this lands at Tier 6 — Autonomy Collapse, Near-Black Hat — whose own Lightwarrior mask is named point for point: manufactured intel passed off as insider access, rationalized as exposing the truth.
Ask Him Directly
The FOIA is the long-term fix. The short-term one is simpler: put the question to Salla himself, publicly, somewhere it can't just get scrolled past.
Reply directly on his posts and videos with one question, every time: "Why has this DD-214 never gone through the same NPRC FOIA process you used for Tompkins and Goode?" Keep it public, keep it civil, keep asking. A question repeated on the record is harder to scroll past than it is to answer.
At any conference, webinar Q&A, or live appearance, ask the same single question out loud, on the record, in front of the audience that paid to be there. A room full of witnesses makes silence itself the answer.
Seven flags are just what surfaced on a first pass. Pull up the source PDF yourself and go block by block. Rewatch the main video. Line up the other documents, the alignment, and the testimony itself against the plain facts — see what else turns up.
One question, asked enough times in enough places, becomes impossible to keep dodging. Whether the answer confirms a mundane record or confirms nothing at all, either outcome is more than exists right now.
This article is built entirely from the document Salla himself hosts and points to as proof, tested against how the Army's own document-generation system actually works. No FOIA has ever been filed. The document that was offered instead does not hold up to the test it was offered to pass.
Comments
Post a Comment