Skip to content

GRA · Fintech Nexus

Spatial financeWhere capital meets hazard, exposure and transition

Corrections, concerns and escalation

Fintech Nexus records each correction as a new version with the passage, source, reason and date. In digital finance the frequent errors concern status and description: an announced product described as operating, a proposed rule described as in force, or a provider’s marketing claim repeated as fact.

پرسیارێک بنێرە Back to Antitrust, independence and financial perimeter
01ناوەڕۆک

Corrections, concerns and escalation in five parts.

لەم دۆسیەیەدا5 parts
  1. 01ڕێڕەوەکانبۆ کوێ بنووسرێت
  2. 02Typical errorsWhat readers catch, and the fix
  3. 03ڕێڕەوRaising a correction or concern
  4. 04پرۆسەWhat happens next
  5. 05سەرچاوەکانWhere this page’s references lead
02ڕێڕەوەکان

Where to write.

Concernنووسین بۆ
An error or a challenge to a findingفۆرمی نیگەرانی ڕاستگۆیی
تایبەتمەندیفۆرمی داواکاریی تایبەتمەندی
A safeguarding concernفۆرمی ڕاپۆرتی پاراستن
03Typical errors

What readers catch, and the fix.

Errorبۆچی گرنگەFix
Announced service described as operatingOverstates what existsDescribe as announced and date the record
Proposed rule described as in forceMisleads compliance planningRestate status from the issuing body
Vendor claim repeated as factImports an unverified claimRemove or attribute and mark unverified
Incident figure without sourceUnverifiableCite the report or remove
04پرۆسە

چۆن پرۆسەکە کار دەکات.

Process explorer · Process

How a correction moves

12 steps5 قۆناغ

پرۆسە

How a correction moves

Anyone may request a correction without membership; an accepted one becomes a new version, and the earlier version stays on record with the reason.

  1. 01 Reporter

    1. 01Anyone may ask for a correctionActor · AnyoneAnyone may ask for a correction, without membership. No membership or Account is needed to report harm or correct public information.

  2. 02 Route and acknowledge

    1. 02Routed by kind of concernهەنگاوA scientific correction or integrity concern goes to the responsible editor or source owner.
    2. 03AcknowledgementتۆمارAnyone who raises a question, shares local knowledge or reports a concern gets an acknowledgement and an issue disposition.

  3. 03 Review

    1. 04Review by editor or source ownerStep · The responsible editor or source ownerA reviewer with a declared conflict never signs the relevant acceptance.
    2. 05Complaint about a decisionStep · A reviewer not responsible for the decisionA programme or decision complaint is reviewed by someone not responsible for the contested decision.
    3. 06Privacy, security and safeguarding queuesهەنگاوPrivacy and rights requests go to the Privacy Officer queue, security reports to the security disclosure queue.

  4. 04 Outcome

    1. 07Accepted correction becomes a new versionتۆمارAn accepted correction creates a new recorded version.
    2. 08Issue disposition recordedتۆمارThe reporter gets an issue disposition and, where appropriate, a remedy or referral. The docs name no appeal for a declined correction.

  5. 05 Carried into the record

    1. 09Affected analysis re-run with corrected inputsStep · Foundry pillarThe affected analysis is re-run with the corrected inputs.
    2. 10Change proposal to the standardsتۆمار · Nexus StandardsMethod and correction findings go to Nexus Standards as change proposals (F06). It records the correction as a change to the evidence.
    3. 11Courses that taught the finding updatedStep · Risk AcademyRisk Academy updates any course that taught the corrected finding.
    4. 12New version with correction and reasonتۆمار · ReportsReports publishes a new version with the correction and its reason. The earlier version stays on record with the correction history.

Status and service levels · Reports · The programme yearDesigned process, not a record of any case: no cycle has run and every programme is at service level R0, information and enquiries. A gate is a programme decision, never a public-authority approval, a certification or a deployment authorisation. The competent authority decides.

05ڕێڕەو

Raising a correction or concern.

Name the page, passage and source. A reviewer not involved assesses it. Conduct and competition concerns follow ڕاستکردنەوە و نیگەرانییەکان.

06What happens next

دواتر چی ڕوودەدات.

  1. 01

    Acknowledgement

    You receive a reference and the next step.

  2. 02

    پێداچوونەوە

    The concern is reviewed by someone not involved in the original work, where possible.

  3. 03

    دەرئەنجام

    A correction is published as a new version with its history; a declined challenge receives reasons.

07سەرچاوەکان

Where this page’s references lead.

ئەو لەش و بەڵگەنامانەی ئەم لاپەڕەیەیان لەگەڵ دەخوێنرێتەوە. دۆخ و وەشانەکان دەگۆڕێن؛ هەر بەستەرێک دەچێتە لای لەشی دەرکەر.

08پرسیارەکان

پرسیار و وەڵام.

Can I raise a concern anonymously?
Yes, though we may not be able to follow up without a way to reach you.
Fintech Nexus

Bring an exposure or capital question to the Alliance.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.

Propose a readiness pilot بینینی هەموو ڕێگاکانی پەیوەندی
یاسایی

نەخشە، داتا و وێنەکانی ئەم ماڵپەڕە بۆ ناوەڕۆک و زانیاریی گشتی پیشان دراون. ئامۆژگاری، پێشبینی یان ئاگادارکردنەوە نین؛ سنوورەکانی زانیارییەکە لە ڕەتکردنەوەی بەرپرسیارێتی و ئاگاداریی داتادا دەستنیشان کراون.