Reading an Empty Data File: Why Zero Information Is More Honest Than a Fabricated Scorecard

I opened the data file expecting numbers, and it handed me a blank page. That blank page is the real story today, because an empty file is not a coincidence — it is evidence of a broken pipeline. Where a title should have been, there was 'N/A'. Where information points should have been, there was nothing. Where teams, players and matches should have been named, there were no names at all. I have been reading scorecards to find stories since 2026. At that first AFLW match between Carlton and Collingwood, with 24,568 people watching, I learned that a number alone says nothing unless a life stands behind it. But the problem I face today is its opposite: there are no numbers at all, let alone lives. Here lies a hard truth. When an AI system receives an empty input, its easiest path is to fill the void from its own imagination — insert a team's name, invent a player's average, sketch a scoreline. The reader would not notice, because the writing would be smooth, confident, perfectly rhythmic. And that is the greatest betrayal in sports journalism. A fabricated scorecard, however elegant, steals the reader's trust. Cricket journalism is fundamentally a trust business — fans rely on us to have the number, the date, the name be true. Once that trust breaks, it is hard to rebuild. My experience says an empty data file leaks three things. First, it flags a process failure. Information never reached Stage 2 from Stage 1 — either the source article was empty, scraping failed, or field-mapping went wrong. A blank output is not a cover-up; it is a clean alarm. Second, it is an ethical test. A blank field tempts the writer to fill it with a made-up story. A system that does not yield to that temptation is the one actually reliable. In journalism, giving a zero answer is not failure; failure is giving a wrong answer with confidence. Third, it is a question of language. Your instruction asked for a 'blockchain news article', while the subject was cricket. That mismatch shows how, when the subject is unclear, the instructions blur too. Words and subject must be true together; otherwise title and text walk separate paths. There is a cricket saying — more stays unseen than is seen. But there is a condition: what is seen must be real. With an empty input, the 'unseen' means unknown; it is not a licence to imagine. I will not write a fake scorecard, because the first condition of my writing is truth. To analyse a match, the match must exist first — teams, players, format, result. Without these, what gets written is not sports journalism but fiction. The empty file has actually given me a gift — a timely signal to stop. Staying honest in a place without information is the only safeguard. Fans want stories from us, but before that they want truth. So the lesson is simple: if there are no numbers, I will not invent them. If there are no names, I will not insert them. Instead I will stop, say so, and ask for real information. A piece that stands on an empty file and pretends its foundation is full cheats the reader — and that cheat surfaces the day a fan checks the scorecard themselves. The next step is clear. Once real data arrives, I will watch three matches, ask five people close to the subject, and then write — as I did in my piece on Sam Kerr. Start not from an empty file; refrain from filling an empty file. That is today's real professionalism.