What they spent decades trying to bury. Watch before accessing the files.
This is not a history book. It is the unredacted evidence they spent decades trying to bury.
"A point where I stopped enjoying the surprise and actually felt unsettled."
— Nicole L., readerTap or click a page to open it full size, and see exactly how deep this game goes. Once you read these titles, everything connects.
You know the names of empires. The wars that changed borders. The leaders remembered as heroes and the people remembered as enemies. But knowing the familiar story is not the same as knowing how it came to be told.
Who left the account behind? Whose voice is missing? What happened between the decision made behind closed doors and the explanation given to everyone else?
Project Fileveil follows those questions from the ancient world to the present day. Across 76 chapters, it revisits the people, events, and decisions behind the history you thought you knew.
Start centuries ago. Follow the accounts forward. Examine who held power, who challenged it, and who lived with the consequences. Then bring those same questions to events close enough to remember.
The point is not to make every event fit one hidden explanation. It is to look closely at each story, especially when it feels too familiar to question.
A signature in one archive. The same name in another. Then a date that makes you go back and read everything again. How many times can the same people appear before you start asking why?
It started with a date. One record placed a meeting before the event it was supposedly responding to. An error, perhaps. Until another file mentioned the same meeting. Then a third named someone who was never supposed to have been there.
We searched the name. Different folders. Different institutions. Documents written years apart. Sometimes a signature. Sometimes a recipient. Never the subject of the account, but always somewhere close to the decision.
One report referred to an enclosure that wasn’t there. Without it, the final paragraph made little sense. We searched the reference number instead of the title. A copy appeared in another archive, filed under something entirely unrelated.
Separately, the documents seemed unremarkable. Put in date order, they raised a different question. The explanation given afterward did not match the instructions circulated before. We went back to the beginning and checked every date again.
The final page carried the name we had been following. No confession. No dramatic warning. Just an approval beneath a decision, written as though it were routine.
Started around eleven and eventually checked the time because I could hear birds outside. A couple of parts genuinely caught me off guard. I had to reread them to make sure I hadn’t misunderstood. Went to work on barely any sleep and still found myself thinking about it at lunch.
My brother kept sending me the link, which usually guarantees I won’t read something. Finally gave in. I still disagree with him about plenty, and there are things in here I’m not sold on, but I owe him an apology for dismissing it without opening it.
While I was reading, I kept thinking, okay, interesting. Then the next morning something came on the radio and I caught myself asking questions I normally wouldn’t ask. That’s when it hit me. The book had stayed with me more than I realized.
The name made me think it would be all dramatic claims and capital letters. I almost passed. Glad I didn’t. I read it slowly, mostly on my commute, and kept taking screenshots of passages to come back to. Some of those are still sitting in my camera roll.
Fair enough, I interrupted her about twenty times. But there were passages I couldn’t just keep to myself. She eventually told me to finish it and hand it over. Now she’s reading it and interrupting me, so I suppose we’re even.
Giving this a good review doesn’t mean I’m signing off on every argument. A few sections left me with questions. But I’d rather read something I have to wrestle with than another book that tells me what I already think. This definitely wasn’t that.
There’s a point where I stopped enjoying the feeling of being surprised and actually felt unsettled. Made a cup of tea, did something else, came back later. Hard to explain without spoiling the experience. Just wasn’t the casual evening read I’d planned.
First time I rushed because I wanted to see where it was going. Second time was slower, with notes. Funny how different a passage can feel when you’re not racing to the next one. I got more out of that second read than I expected.
Real readers after opening the pages for the first time.
Plain answers.
Project Fileveil is a book by Elian Wade that invites you to question familiar explanations and take a closer look at what you believe. It asks for your attention, not your automatic agreement.
Come with curiosity, not credentials. You don’t need to arrive with a position to defend. Give yourself room to consider an unfamiliar argument without feeling obliged to accept it.
No. Read critically. Question the connections, challenge the reasoning, and distinguish what convinces you from what needs more support. Disagreement is part of taking a book seriously.
Read at your own pace. Pause when something deserves a closer look. Make notes, follow up on references where provided, and revisit the passages you find difficult. Finishing a chapter matters less than understanding what you make of it.
Elian Wade is the author of Project Fileveil. The invitation is simple: judge the book by what is on the page, not by the name on its cover.