Sunday, December 14, 2025

Template No.: T-TK005 Template Title: Public Correction Procedure (Fake Lab-Testing Claim in Public)

 THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM

FOR INTERNAL USE ONLY

Template No.: T-TK005

Template Title: Public Correction Procedure (Fake Lab-Testing Claim in Public)

Related Research Case IDs / Cluster: TK-005 / Cluster E (Science, Testing, Misinformation)

Linked Templates / Policies: T-TK001 ID Verification Checklist; T-TK002 High-Risk Visitor Protocol; T-TK003 Credential Check SOP; T-TK004 External-Claim Verification SOP; Media & Public Statement SOP; Data Protection & Confidentiality Policy; Conflict Resolution & Security SOP; Incident Reporting Form; No-Gift Policy

Date of form: ____ / ____ / ______

Prepared by / Role: _______________________

Office / Unit: ____________________________

Country / Location: _______________________

Confidentiality Level:
Internal only [ ] Restricted [ ] Sacred-Restricted / Sensitive [ ]

Use of this form (tick):
New case / action [ ] Follow-up [ ] Annual review [ ] Archive only [ ]


1) Purpose

This procedure is used when a public post claims a relic was “lab-tested” (or “CT scanned”, “DNA tested”, “government certified”) but the claim is false, unverified, or misleading.

Goal:

  • Protect truth and public trust.

  • Reduce conflict and harm.

  • Correct misinformation with calm, respectful language.

Key rule: We correct claims. We do not attack people.


2) When to activate this procedure

Activate if any of these appear online or in media:

  • “Lab confirmed authenticity” (no proof)

  • Edited “test report” images

  • Misuse of lab logo, hospital name, university name

  • Fake signatures or reference numbers

  • HSWAGATA name used to support a claim without approval


3) Step 1 — Capture evidence (do immediately)

Tick all done:

Screenshot the post (show date/time and account name) [ ]
Copy the post URL / link (if available) [ ]
Save images/videos attached to the claim [ ]
Record where it appeared: Facebook [ ] YouTube [ ] TikTok [ ] X [ ] News [ ] Other: _______
Estimate spread: Low [ ] Medium [ ] High [ ] Viral [ ]
Save comments that show harm/risk (threats, panic, conflict) [ ]

Evidence file name (standard): TK005_YYYYMMDD_Platform_Account
Stored at secure location: __________________________________
Access level: Internal [ ] Restricted [ ] Sacred-Restricted [ ]


4) Step 2 — Safety and access controls

If a person is linked to the claim and requests access:
Apply T-TK002 High-Risk Visitor Protocol [ ]
Apply T-TK001 ID verification [ ]
Do not allow relic handling/testing based on public claims [ ]

If staff are threatened or harassed:
Notify Security / Duty Manager [ ]
File Incident Report [ ]
Keep staff private data protected [ ]


5) Step 3 — Verify the claim (truth check)

Use T-TK004 External-Claim Verification SOP if a letter/report is shown. [ ]
If a lab/hospital is named:

  • Contact lab/hospital using public official contact [ ]

  • Ask for written confirmation (yes/no) [ ]

  • Ask: “Did you issue this report? Is this document genuine?” [ ]

Verification status (choose one):
Unverified (no proof) [ ]
False (confirmed fake) [ ]
Misleading (true facts used wrongly) [ ]
True (confirmed) [ ]

Short verification notes (1–2 lines):



6) Step 4 — Decide the correction level

Decision made by (Comms Lead / Head / Board delegate): __________________
Date: ____ / ____ / ______

Choose ONE level:

Level A: Quiet correction (low spread)

  • Reply once with a short correction [ ]

  • Send a private message requesting edit/removal [ ]

  • Monitor for 7 days [ ]

Level B: Public correction (medium/high spread)

  • Post an official correction on HSWAGATA channels [ ]

  • Pin the correction for visibility [ ]

  • Request platform takedown (if fake documents) [ ]

Level C: Formal statement + legal/security action (viral / high risk)

  • Formal statement approved by Board [ ]

  • Legal notice or official complaint (if needed) [ ]

  • Strong staff safety plan [ ]


7) Step 5 — Write the correction (Right Speech rules)

The correction must be:

  • True (only what we can confirm)

  • Calm (no anger)

  • Clear (simple words)

  • Respectful (no shaming)

  • Peaceful (reduce conflict)

Do NOT:

  • Reveal personal data (phone, ID, address)

  • Share sacred-restricted images

  • Share unverified rumours

  • Argue in long comment fights


8) Official correction statement template (copy and fill)

Title: Correction Notice about Lab Testing Claim

Message (short, B1 level):
“HSWAGATA shares this notice to protect truth and public trust.
A public post says: ‘__________________________’ (describe the claim).
At this time, HSWAGATA has no verified record that this test was done by __________________ (lab/hospital), or that the report shown is genuine.
We ask the public to wait for confirmed information.
If any testing is approved in the future, HSWAGATA will announce it through our official channels.
Thank you for supporting peace, respect, and careful speech.”

If the claim is confirmed fake, add one line:
“Our verification indicates the document/report is not genuine.”

Approved by (name/role): __________________ Date: ____ / ____ / ______


9) Step 6 — Publish and respond (controlled communication)

Publish on official channels:
Website [ ] Facebook [ ] Page/Group [ ] Press release [ ] Other: _______

Actions (tick):
Pin correction post [ ]
Turn on comment moderation (if policy allows) [ ]
Reply once with the same key message [ ]
Do not debate repeated hostile comments [ ]
Hide/remove abusive comments (per policy) [ ]
Report impersonation/fake documents to platform [ ]


10) Step 7 — Follow-up tracking (monitor and close)

Monitoring period: ___ days (default 7–14 days)

Track results:
Post removed by author [ ]
Platform removed content [ ]
False claim continues [ ]
New rumor versions appear [ ]
Conflict risk reduced [ ]
Conflict risk increased [ ]

If “continues” or “increased”:
Escalate to Level B/C [ ]
Board notified [ ]
Security notified [ ]

Closure note (1–2 lines):



11) Recordkeeping

Attachments:
Screenshots [ ] URLs list [ ] Verification emails/calls [ ] Final statement text [ ] Incident report (if any) [ ]

Filed by: _______________________ Date: ____ / ____ / ______
Reviewed by (Head/Board delegate): ______________ Date: ____ / ____ / ______

No comments:

Post a Comment

Template No.: T-TK007 Template Title: Origin-Story Recording Protocol (Conflicting Relic Origin Stories)

 THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM FOR INTERNAL USE ONLY Template No.: T-TK007 Template Title: Origin-Story Recording Prot...