curivra.

Previous version (policy package P-55a8b32e0a50, effective 2026-10-15). It applies until the current version takes effect: read the current version.

Editorial standards and corrections

Responsible for editorial decisions: Brandsap · Corrections: contact@brandsap.com or, in the app, ⋯ on a card → Report a problem

1. What we publish

2. How an automated card is made

  1. Curivra reads the agency's feed every few minutes and identifies the agency, the exact feed and the event.
  2. A fixed template fills a card from the source's own fields (magnitude, place, time, alert type, area, end time). No generative AI writes or edits these cards.
  3. A separate automatic check compares every figure, name and time in the card with the source record. A card that fails is never published.
  4. Publishing rules approved by the operator then apply. A card is not published if the source information is more than 6 hours old, if a warning has less than 10 minutes left, or if the event is sensitive: possible casualties, a tsunami flag, an extreme warning or a tornado warning waits for a person to review it.
  5. Earthquake cards leave every feed 72 hours after the earthquake; weather cards leave when the alert ends. A held card whose event has ended is closed and can never be published late.
  6. Each card is labelled "Automated card from … data" and carries the source's credit line.

3. Corrections

4. Withdrawals

A card that is wrong, unsafe to keep up or no longer covered by a rights basis is withdrawn. It leaves every feed, its link stops working, and the app deletes copies on readers' phones. A source can be suspended at once, which removes all of its cards; every feed can also be switched off by an emergency switch without an app update.

5. Reader reports

Readers can report a card as inaccurate, not related to their interests, broken, or something else. Reports are reviewed daily during the test programme. A "not related to my interests" report is checked against the reader's chosen topics on our server; a confirmed mismatch is treated as a critical fault.

6. Standards