← Perplexity
Complex day at Perplexity

Choose a page policy for original reporting before the 48-hour rebuild

You’re the ai / ml engineer. Your team is in the room. Printed Oct 15, 2026.

The index rebuild must choose between broad recall and reliably original sources.

Keeping recall protects answer coverage while stricter page selection protects claim support in cited answers.

Who you’d be doing this for

“Three citations sent me to the same wire copy, and my editor asked where the original reporting was.”

Lourdes Moreno · Freelance Journalist

A consumer researcher using cited answers to orient a developing story before contacting sources.

What is at stake

Original-source selection fell 21 points after a parsing-model update, and weak claim support now reaches 18% in the affected set. You must weigh recall against a durable policy change that cannot be cheaply reversed.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • source recall vs. claim support
  • rebuild deadline vs. verified evidence
  • automated coverage vs. human-reviewed validity
  • original reporting vs. web-wide availability

Why Perplexity

Perplexity Search depends on crawling, parsing, indexing, ranking, and answer generation to turn current web information into cited answers.

Written with these in mind

Search ML engineerRanking engineerML quality and evaluation engineer

Not your kind of problem? 31 more at Perplexity, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.