This HTML page is provided for reader navigation and stable HTML routing. The corresponding Markdown source is retained for text preservation, search discoverability, existing links, and source review.
External Visibility Tracking
This document defines how external visibility of LUMINA-30, PCR-C, related DOI records, Zenodo records, arXiv entries, and GitHub repositories should be monitored.
It does not claim external adoption. It only defines what evidence should be collected to determine whether external visibility exists.
1. Purpose
LUMINA-30 requires observable external reference paths. This tracking layer avoids relying on impressions such as “it may have been seen,” “it is probably visible,” “the DOI exists,” or “the GitHub repository is public.” Visibility should be evaluated using recorded evidence.
2. Observation Categories
- GitHub traffic
- Zenodo views and downloads
- DOI / DataCite usage and linking events
- arXiv presence and external references
- search, citation, and referral evidence
3. GitHub Traffic
Track repository visibility using traffic data where available: repository, views, unique visitors, clones, unique cloners, popular paths, referrers, and observation date. GitHub traffic data is time-limited, so snapshots should be taken periodically.
4. Zenodo Visibility
Track each relevant Zenodo record and DOI: record title, Concept DOI, Version DOI, views, unique views, downloads, unique downloads, data volume, and observation date. When both Concept DOI and Version DOI exist, record both.
5. DOI and DataCite Evidence
Track DOI visibility through DataCite where available: DOI, metadata status, usage events, citation/reference events, related identifiers, and observation date. Absence of DataCite events should be recorded only as “no DataCite event observed.”
6. arXiv Evidence
Because arXiv does not provide paper-level download statistics, track proxy evidence such as arXiv ID, URL resolution, DOI or journal reference presence, external mentions, search visibility, citation evidence, and observation date.
7. External Search Evidence
Record conservative search evidence using exact queries such as “LUMINA-30,” “LUMINA-30 Boundary Check,” “Pre-Critical Recursive Cutoff,” “PCR-C irreversibility risk,” exact DOI strings, and exact arXiv IDs where available.
8. Interpretation Rules
| Evidence | Interpretation |
|---|---|
| GitHub views / clones | Visibility or technical access, not adoption |
| Zenodo views | Record-level interest, not endorsement |
| Zenodo downloads | Stronger than views, but not adoption |
| DOI events | Traceable scholarly or metadata interaction |
| External citation | Strong evidence of scholarly reference |
| External discussion | Evidence of attention, not adoption |
| Incident-review usage | Strongest evidence of practical uptake |
9. Status Labels
Use conservative labels: Not observed, Observable, Visited, Downloaded, Referenced, Cited, and Used.
10. Non-Overclaim Rule
Visibility is not adoption. Do not describe LUMINA-30, PCR-C, or related documents as adopted, recognized, cited, or used unless the corresponding evidence is recorded.