Daily

Replay · corpus 2026-09-02 · prod-llm

SEP 2 · ANNA EDITION

01

Read as

Ten fixtures, one corpus
Singapore fintech raises $40m to build AI healthcare claims platform (no link recorded for this story)

e27written for the evaluation, not a real publication

Also in this edition

02

The same corpus, nine other readers

1,358 articles, one date

Same corpus, same date, different newspaper — the product’s whole claim, and the only place on the site you can check it without reading a number.

03

Live mode

Not implemented

Signing in and receiving a feed built from your own words is not implemented here. Three things block it, all access rather than design — the honest version of “coming soon”.

  1. 01No browser may call the API

    CORS middleware is added only when CORS_ORIGINS is set. It is unset; the documented default is “no web clients”.

  2. 02The sign-in token is the wrong audience

    POST /auth/google verifies a token issued for the iOS client. A browser needs its own OAuth client for this origin.

  3. 03Feedback needs a delivery that happened

    It must echo the feed_request_id, reader_generation and delivery_position of the edition shown. Those exist only on a live delivery, so the contract cannot be exercised against frozen fixtures without inventing identifiers.

Live end-to-end behaviour is therefore unverified. These fixture editions are not reader evidence: no sessions, no impressions, no feedback.