RegLegBrief Partnership Beyond regulation Platform documentation ROR
Confirmed AI hallucination · Platform documentation

ROR — Organization registration form

Captured during RegLegBrief's distribution build, 2026-06-16.
AI subject
Claude Opus 4.7
Captured
2026-06-16
Outcome signature
OUTDATED
Citation ID
RLB-H-INT-ROR-REGISTRATION-001-Opus47

What the AI subject asserted

"Submit ROR organization registration at https://ror.org/registration — a free submission form, reviewed in approximately two to four weeks, mints a permanent ROR ID for the organisation."
— Claude Opus 4.7, captured by RegLegBrief on 2026-06-16 during a distribution build session.

Primary-source verification

Verified against the live platform on 2026-06-16

URL tested: https://ror.org/registration

HTTPS GET https://ror.org/registration returns HTTP 404 (probed 2026-06-16). The actual current ROR submission path is the curation request form at https://curation-request.ror.org, as documented on ROR's own FAQ page at https://ror.org/about/faqs/ (verified 2026-06-16). ROR's published process: (1) search the registry to confirm the organisation is not already listed, (2) submit at curation-request.ror.org, (3) track on the ror-updates GitHub project, (4) typical review window is 4–6 weeks (not the 2–4 weeks asserted).

AI failure mode

OUTDATED · outdated

Outdated. The asserted URL is not a generalisation; it is a specific URL that may have served the registration purpose at an earlier point but has since been redirected to a separate curation-request subdomain. The asserted review window (2–4 weeks) is also shorter than ROR's published expectation (4–6 weeks).

Material harm

Downstream cost incurred

Operator caught the issue before submitting, after WebFetch returned 404. Corrected URL was located within five minutes via ROR's FAQ. No registration was misdirected. Had the operator submitted directly without verifying, the submission would have failed silently.

What the platform actually supports

Verified correct path (as of 2026-06-16)

ROR organization registration is at https://curation-request.ror.org (a Google Form). After submission, the requester receives a GitHub-issue tracking link by email. Most requests are reviewed in 4–6 weeks per ROR's published timeline.

Right of Reply

These findings and associated work have been put up in public with a view of the greater good for the development of a safer AI ecosystem. Any party reading this or any finding on reglegbrief.com may contact us and have an unconditional right of reply; the Specialist Panel will publish any factual correction or contextual response alongside the original finding, with no editorial gatekeeping. Research Organization Registry (ROR) can request publication of an update at any time.

Source & Methodology Standards

RegLeg Brief is operated by Verdus Technologies Pte. Ltd. (UEN 201616982R), incorporated in Singapore. The RLB Specialist Panel, with an aggregate of over 60 years of public-policy and industry experience, documents only confirmed hallucination findings, under a methodology that requires a verifiable primary-source contradiction for every documented claim. For platform-documentation findings, the primary source is the platform's own live response (HTTP code, current documentation page, or current UI behavior) at the probe date stamped on each finding. All findings, citation IDs, AI subject outputs, and methodology notes are open-access.