How BitDepth is built.
A byline, not a persona.
Every pillar on this site carries one byline: the BitDepth Team. It is a collective editorial identity, not an invented author. We would rather show you exactly how the work is made than dress it up with a face that isn't real.
BitDepth is a reporter, not an analyst. We don't claim deep technical authority in every subject we cover. What we claim is editorial judgment — in choosing what matters, organizing it, and synthesizing what credentialed sources have already said, with links back to those sources so you can check us.
We're also candid about the tooling: AI drafts, humans verify.AI helps assemble and phrase a draft from sourced notes. No draft is published without a human checking it against primary sources, tightening the citations, and reading it cold for anything that overreaches. That division of labor is the whole method, and it's why the next section exists.
Draft, verify, edit, maintain.
A pillar isn't written once and forgotten. It moves through four stages — and then keeps moving, week after week, for as long as the topic stays live.
Draft
A pillar starts from sourced notes — primary documents, filings, transcripts, technical papers. AI assists the first draft, working only from those notes, never inventing facts to fill a gap.
Verify
Every factual claim is checked against a primary source before it ships. Numbers, dates, and quotes are pulled verbatim from the document they came from — not paraphrased from memory.
Edit
A human editor tightens the voice, confirms every inline citation resolves, and does a cold read for anything that reads as certain but is only plausible. No draft publishes unread.
Maintain
Pillars are living documents. As the story moves, we add dated, sourced timeline entries, bump the edition number, and stamp a fresh last-revised date so you can see how current the page is.
Primary sources, linked.
When a primary source and a write-up of it both exist, we cite the primary one — the press release over the article about it, the earnings transcript over the summary, the technical paper over the recap.
Attribution happens at the point of the claim. Sources are linked inline, in the sentence where the claim is made, so you never have to hunt through a footer to see where a number came from. Every entry in a pillar's timeline carries its own link to a primary source.
We quote sparingly and link generously — at most a short excerpt from any single secondary source, and our own words for the rest. We don't republish other people's articles; we point you to them.
When we're wrong.
We get things wrong sometimes. When we do, we fix the page rather than quietly leaving it — and the page shows its own history. Every pillar displays a first-published date, a last-revised timestamp, and an edition numberthat increments each time we revise it. Those aren't decoration; they're how you gauge whether what you're reading is current.
If you spot an error — a stale figure, a broken source link, a claim that doesn't hold up — tell us. Corrections from readers are a feature of the process, not an embarrassment to it.
Found something off?
Corrections, sourcing questions, or a topic you think deserves a pillar — we read every note.