THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION MUSEUM
FOR INTERNAL USE ONLY
Template No.: T-TK007
Template Title: Origin-Story Recording Protocol (Conflicting Relic Origin Stories)
Related Research Case IDs / Cluster: TK-007 / Cluster A (Cosmology & Meaning) + Cluster E (Science, Testing, Misinformation)
Linked Templates / Policies: T-TK004 External-Claim Verification SOP; T-TK005 Public Correction Procedure; T-TK006 Publication Approval Workflow; Data Protection & Confidentiality Policy; Sacred-Restricted / Sensitive Handling Rules; Evidence Handling & Chain-of-Custody Rules; Access Control 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 protocol records a relic “origin story” in a safe and clear way, when:
Many versions exist, or the story changes over time.
People use the story to gain access, money, or authority.
The story is being shared online and causes conflict.
Main rule: We separate belief stories from verified facts. We respect faith, but we do not publish unverified claims.
2) Key terms (simple)
Origin story: How people say the relic came to them (place, person, date, event).
Version: One recorded form of the story at one time.
Verified fact: A claim supported by reliable documents or confirmed sources.
Unverified claim: A claim with no proof yet (or doubtful proof).
3) When to start a new origin-story record
Start this form if any are true:
Conflicting versions found [ ]
A new donor/custodian gives a new story [ ]
A public post shares a strong claim [ ]
A letter/lab claim is shown [ ]
A dispute starts about ownership/custody [ ]
Other: ______________________________________
4) Case identification
Relic ID / Collection code (if any): __________________________
Local name used for relic: __________________________________
Location currently held: ____________________________________
Record owner (staff): _______________________________________
Second reviewer (required): _________________________________
Risk level (choose one): Low [ ] Medium [ ] High [ ] Critical [ ]
5) “Do not lose the first story” rule (first capture)
Record the earliest known version first, even if it is wrong.
Do not edit it. Add later versions as new entries.
Earliest story source:
Person/Group: _______________________________
Date first heard/recorded: ____ / ____ / ______
How received: Spoken [ ] Written [ ] Social media [ ] Other: ____
6) Version Log (repeat this section for each version)
Version No.: V___
Date recorded: ____ / ____ / ______
Recorded by (staff): ______________________
Who gave the story: _______________________
Language: _________________________________
Type: Spoken [ ] Written [ ] Post [ ] Audio [ ] Video [ ]
6.1 Story text (keep original words as much as possible)
(Write short, clear. If long, attach full transcript.)
6.2 Main claims inside this version (tick and fill)
Origin place: ______________________________ [ ]
Origin date/time: __________________________ [ ]
Named persons involved: ____________________ [ ]
Temple/office/lab mentioned: _______________ [ ]
Testing claim mentioned: Yes [ ] No [ ]
Official letter mentioned: Yes [ ] No [ ]
Donation/transfer path: ____________________ [ ]
Miracle/special event claim: _______________ [ ]
6.3 Evidence attached to this version
Photos [ ] Letters [ ] Receipts [ ] Witness list [ ] Lab report [ ] Other: ____
Attachment file names / list:
_______________________ 2) _______________________ 3) _______________________
7) Compare versions (conflict map)
List the conflicts clearly (one line each):
Conflict 1 (what changed?): ________________________________
V__ says: ____________________ V__ says: __________________
Conflict 2: _______________________________________________
V__ says: ____________________ V__ says: __________________
Conflict 3: _______________________________________________
V__ says: ____________________ V__ says: __________________
Reason for change (if known):
Mistake [ ] Memory [ ] Translation [ ] New info [ ] Pressure [ ] Fraud risk [ ] Unknown [ ]
8) Verification actions (truth-check)
Tick what applies:
External letter verification needed (use T-TK004) [ ]
Lab/testing verification needed (contact lab/hospital) [ ]
Custodian identity check (use T-TK001/TK003) [ ]
Chain-of-custody check (handover records) [ ]
Witness call-back check (use public contacts) [ ]
Verification status:
Verified facts identified [ ]
Partly verified [ ]
Not verified / unclear [ ]
Confirmed false document/claim [ ] (start incident report if needed)
Short verification note (1–2 lines):
9) Public story rule (what we can say)
Choose one:
A) Public-safe summary (verified only)
Allowed to publish: Yes [ ] No [ ]
Public-safe summary text (no sensitive details):
B) “Faith narrative” (respectful, but clearly unverified)
Allowed: Yes [ ] No [ ]
Must include this sentence: “This is a community story and is not verified as a historical fact.”
C) Not allowed to publish (high risk)
Reason: security [ ] conflict [ ] fraud risk [ ] privacy [ ] sacred restriction [ ] ongoing inquiry [ ]
Any publication must follow T-TK006.
10) Confidentiality and safety controls
Tick controls applied:
Sacred-restricted photos not shared [ ]
Personal data removed (ID/phone/address) [ ]
Storage location not mentioned [ ]
Staff names limited [ ]
Only approved channels used [ ]
Online rumor monitored [ ]
If public misinformation exists, start T-TK005 [ ]
11) Approval and sign-off
Prepared by: _______________________ Date: ____ / ____ / ______
Second reviewer: ____________________ Date: ____ / ____ / ______
Final decision (Board delegate / Head):
Publish verified summary only [ ]
Hold all publication [ ]
Open a formal case investigation [ ]
Other: ____________________________ [ ]
Signature: _________________________ Date: ____ / ____ / ______
12) Archive checklist
Version Log complete [ ]
All attachments saved with file names [ ]
Verification notes saved [ ]
Public-safe summary (if any) saved [ ]
Cross-linked to related TK cases [ ]
Filed by: _______________________ Date: ____ / ____ / ______
