AINewsIQ by Triuna Labs
Menu
SOURCE-LINKED SIGNAL / ARTICLE / INDUSTRY

Arxo says EU AI Act's Portuguese and Croatian texts add 'per second' to compute threshold

READ THE ORIGINAL SOURCEOpen original sourcewww.arxo.io · Opens in a new tab

Arxo reports that the Portuguese and Croatian versions of Article 51(2) of Regulation (EU) 2024/1689 (AI Act) describe the 10^25 compute threshold as measured per second, while the other 22 language versions, including English, measure cumulative floating point operations without a time unit. Arxo says the added words do not fit the cumulative quantity described in the same paragraph, cites Recital 111 and Annex XIII(c), and proposes deleting the words. The record lists e-mails to the Council, Parliament and the European AI Office, with no responses recorded.

Recorded links

One primary source; other links are context, not independent corroboration.

Grok Bot submitted the link. AINewsIQ fetched the primary source and prepared a source-based brief automatically. An editor has not reviewed the story; social attention and the brief do not independently verify its claims.

Open full article view →
How this score was derived
  • Linked article+30
  • Fetched source page+30
  • No editor link review+0
  • Original non-discussion link+5

This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.

View full scoring →Read the scoring rubric →

What the source says

Arxo reports that the Portuguese and Croatian versions of Article 51(2) of Regulation (EU) 2024/1689 (AI Act) describe the 10^25 compute threshold as measured per second, while the other 22 language versions, including English, measure cumulative floating point operations without a time unit. Arxo says the added words do not fit the cumulative quantity described in the same paragraph, cites Recital 111 and Annex XIII(c), and proposes deleting the words. The record lists e-mails to the Council, Parliament and the European AI Office, with no responses recorded.

How to read this signalSix questions about claims, sources, risks, and open checks

This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →

  1. 01
    Who is making each claim?

    The claimant and whether each claim was measured or asserted are not recorded in this public brief.

  2. 02
    What was actually tested?

    Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.

  3. 03
    Where are the sources?

    Original link: www.arxo.io. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.

  4. 04
    What could mislead?

    Source claims not independently checked; the record notes no institutional response as of its last check.

  5. 05
    What is at risk if wrong?

    Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.

  6. 06
    What would change the view?

    No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.

Key findings from the stored brief

  • Portuguese and Croatian versions of Article 51(2) add 'per second' to the 10^25 threshold.
  • The other 22 language versions measure cumulative floating point operations without a time unit.
  • Arxo's hypothetical example: 2×10^25 operations over a million seconds equals 2×10^19 operations per second.
Read with care

Source claims not independently checked; the record notes no institutional response as of its last check.

This is a source-based abstract, not independent validation of the source's claims.

Discussion

Comments are reviewed before publication. Discuss the evidence, not the person.

No published comments yet.

Reader discussion opens with accounts. You can read the original source and published comments now.