Urgent.News

What's breaking now, across hundreds of outlets.

Tech

RAG Citations in 2026: 5 Ways to Debug Wrong-Page Chunk Metadata

Short answer: Rebuild chunk text, page metadata, and offsets as one immutable revision, then verify the cited quote before publishing it. For an edtech compliance-policy watcher, I treat retrieval text, source revision, page identity, and offsets as one immutable evidence record; if any member changes, the alert must link to the newly parsed record rather than reuse old metadata. This costs…

Short answer: To prevent RAG citations from pointing to the wrong page, combine chunk text, page metadata, and offsets into one immutable revision. Verify the cited quote before publishing. Treat retrieval text, source revision, page identity, and offsets as one evidence record, linking to the newly parsed record if any member changes.

This costs ingestion time but prevents wrong-page citations. Reasons for wrong-page citations include differing retrieval and citation resolution identities, offset shifts due to document edits, and similar failures. Use an immutable key combining content digest and parser version across the pipeline. Store page labels and parser page indexes separately.

Make one revision the unit of publication, parsing fetched responses into staging revisions, emitting chunks and locators, validating the set, then publishing one revision pointer. Reject mixed provenance before it reaches search by checking bounds, validating quoted bytes, and refusing batches with mixed revisions. Test the locator by resolving it and asserting the displayed quote hashes to the stored quote. Build fixtures with various policy changes and assert locator correctness for each.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Testing Terraform with AWS Emulator

  • AWS Emulator emulates AWS API endpoints locally for Terraform testing.
  • Enables "Plan Apply" workflow with mock AWS infrastructure for testing.
  • Integrates into CI pipeline for early error detection in Terraform code.

Your buyer's SDK chose POST: we ran that test on 60 of our own paid routes

On 14 November, a seller-side census on dev.to (edvyno, "I POSTed to 137 x402 paid routes. 49 of them returned 404." ) sent one empty-JSON POST, without a payment header, to 137 paid routes across 78…

  • Seller conducted test on 137 paid routes using seller-side census
  • 49 routes returned 404 status, 35.8% of total
  • Only 22 out of 78 routes answered 402 on every POSTed route

Why a no-signup Arabic chat room still beats an app in 2026

Most chat products in 2026 start with a 40MB download and a phone number. For a large group of users that is the whole problem: they want to talk for ten minutes, not create an identity.

  • No-signup Arabic chat room offers quick access for users
  • Lightweight mobile page outperforms app downloads in 2026
  • Privacy-focused design prioritizes Arabic-speaking communities

More from Sunday 22 November →