nextbig.dev
Vancouver, B.C. · Intelligence on AI and the machines that run it
nextbig.dev

Editorial Guidelines

How we source, write, and publish content

Last updated: June 13, 2026

How the briefing is made

Transparency statement: nextbig.dev is written and edited by Oday Brahem. The daily briefing is produced with AI tools: Claude drafts from a curated, human-scored source set, and every edition is shaped and signed off before it publishes. We believe in saying exactly how the work is made.

Every daily briefing is generated using Claude's frontier model from Anthropic. The AI synthesizes information from curated sources into original editorial content. It does not simply copy or rewrite existing articles. Hero images are generated using AI image generation tools.

Audio narrations of briefings, when available, are generated using text-to-speech technology and are clearly labeled as such.

Content Sourcing

Our news monitoring infrastructure tracks 300+ curated sources on X, plus Hacker News and GitHub trending, including:

Sources are selected for credibility, relevance to the AI builder community, and track record of accurate reporting. We do not use anonymous or unverified sources. All source articles are linked in the original news feed so readers can verify information independently.

Source Scoring

Each incoming article is automatically scored 1–10 by Claude's frontier model on relevance to builders, novelty (is this genuinely new?), information content (concrete numbers beat adjectives), and impact on the compute layer. Only articles meeting our quality threshold appear in the news feed, and the highest-scoring stories are selected for the daily briefing.

Editorial Process

The daily briefing follows a structured editorial pipeline:

  1. Aggregation: Our system continuously monitors curated sources and ingests new articles throughout the day
  2. Scoring & Ranking: Claude evaluates each article for relevance, novelty, and impact, assigning a numerical score
  3. Selection: The top-scoring articles from the past 24 hours are selected as briefing source material
  4. Synthesis: Claude reads the selected articles and writes an original editorial briefing: the mechanism behind each story, the arithmetic the sources skipped, and concrete implications for builders
  5. Publication: The briefing is published daily at 6 AM UTC with structured data (JSON-LD), proper meta tags, and an auto-generated hero image
  6. Audio: An optional audio narration is generated for accessibility and convenience

The human editorial team oversees source curation, scoring parameters, the publication pipeline, and reviews output quality on an ongoing basis. The team can intervene at any stage to adjust, correct, or withhold content.

Original Analysis & The Call

We hold our writing to an originality bar: a story summary must add information beyond its headline, the briefing must say something the wire didn't, and the weekly essay's thesis must be a claim found in none of its sources. Synthesis is the floor.

The signature device is The Call. Every daily briefing closes with one original, non-consensus claim about what happens next: stated with the evidence behind it, the publicly observable event that would prove it wrong, and a date by which it settles. The weekly essay develops the strongest call of the week into a full thesis and ends with a call of its own.

Why falsifiable: predictions are cheap when nobody checks. Ours are written so any reader can settle them with public information. When a call goes against us, we say so in print. The archive is the scoreboard, and it stays up.

Fact-Checking Standards

Because our briefings synthesize information from multiple sources rather than conducting original reporting, our fact-checking approach focuses on:

We acknowledge that AI-generated content can contain errors. Our system is designed to minimize this risk through careful source selection and prompting, but we do not claim perfection.

Corrections Policy

We take accuracy seriously. If you spot an error in any of our content:

When we confirm an error, we will update the affected briefing with a correction notice and note the date of the correction. Significant factual errors will be addressed as quickly as possible, typically within 24 hours of being reported.

Calls are treated the same way: when one settles against us, we acknowledge it in the next briefing or essay rather than quietly letting it expire.

Content Independence

nextbig.dev does not accept payment for coverage. Our news feed and briefings are not influenced by advertising, sponsorships, or commercial relationships. Source selection and scoring are based solely on relevance and quality criteria.

If we ever introduce sponsored content or partnerships, they will be clearly labeled and separated from editorial content.