Skip to content

chore(zenodo): PASS-7 fix invalid ORCID + wrong community slug in .zenodo.json#599

Merged
gHashTag merged 1 commit into
masterfrom
chore/zenodo-pass7-orcid-community
May 12, 2026
Merged

chore(zenodo): PASS-7 fix invalid ORCID + wrong community slug in .zenodo.json#599
gHashTag merged 1 commit into
masterfrom
chore/zenodo-pass7-orcid-community

Conversation

@gHashTag
Copy link
Copy Markdown
Owner

PASS-7 R5-honest fix: invalid ORCID + wrong community slug in .zenodo.json

Closes #598.

PASS-7 R5-honest deep-sweep across the 5-repo Trinity hive surfaced a
release-time deposit hazard in t27/.zenodo.json.

Anomaly A9 (HIGH/CRITICAL)

 "creators": [
   {
     "name": "Vasilev, Dmitrii",
     "affiliation": "Trinity Computing",
-    "orcid": "0000-0002-5135-5363"
+    "orcid": "0009-0008-4294-6159"
   }
 ],
-"communities": [{"identifier": "trinity"}],
+"communities": [{"identifier": "trinity-s3ai"}],

Verification

  • curl -s -H "Accept: application/vnd.orcid+json" https://pub.orcid.org/v3.0/0000-0002-5135-5363/record returns no person name (None None) — the ORCID does not resolve to any registered researcher.
  • The canonical Vasilev ORCID, present in CITATION.cff of all 5 Trinity repos (trinity, trinity-fpga, trios, t27, trios-trainer-igla) and on the community SOT records, is 0009-0008-4294-6159.
  • The community slug trinity does not exist on Zenodo.
  • The canonical SOT community per PASS-6 operator directive is trinity-s3ai (verified id 668f1264-2341-488a-bb14-351fa908ac64, public, owner Vasilev id 1570570, 12 records: B001–B008 = 19227865/67/69/71/73/75/77/79; D004–D007 = 19020270/75/80/82).

Impact

If .zenodo.json is ever fed to Zenodo's auto-deposit hook on a GitHub release, the deposit would be attributed to a non-existent ORCID and routed to a non-existent community — failing both attribution and discovery. This is a silent, latent hazard.

Anchor

φ² + φ⁻² = 3 — algebraic identity (Coq witness: gHashTag/t27/coq, 10 .v files, 48 statements, 35 Qed, 0 Admitted; audit 2026-05-12).

Files changed

  • .zenodo.json — both fields corrected
  • docs/NOW.md — PASS-7 audit narrative + freshness date 2026-05-12 UTC

Cross-refs

φ² + φ⁻² = 3 · TRINITY · R5-HONEST · PASS-7

…nodo.json

PASS-7 R5-honest deep-sweep across the 5-repo Trinity hive surfaced a
release-time deposit hazard in t27/.zenodo.json:

- "orcid": "0000-0002-5135-5363" attached to creator 'Vasilev, Dmitrii'.
  Public ORCID API returns no person record for this ID. The canonical
  Vasilev ORCID (confirmed in all 5 Trinity CITATION.cff files) is
  0009-0008-4294-6159.
- "communities": [{"identifier": "trinity"}]. This community does not
  exist on Zenodo. Canonical SOT per PASS-6 operator directive is
  community trinity-s3ai (id 668f1264-2341-488a-bb14-351fa908ac64,
  12 records: B001-B008 + D004-D007).

If .zenodo.json were ever fed to Zenodo's GitHub-release auto-deposit
hook the deposit would land on a non-existent ORCID and route to a
non-existent community — failing both attribution and discovery.

This PR replaces both fields with the canonical values verified during
PASS-6, and updates docs/NOW.md with the PASS-7 audit narrative.

Anchor: phi^2 + phi^-2 = 3 (algebraic identity, Coq witness in coq/).

Closes #598.
Refs: trios#264 (Trinity Hive Throne), #596 (PASS-6).
@github-actions
Copy link
Copy Markdown

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions
Copy link
Copy Markdown

PR Dashboard

Generated at: 2026-05-12 18:38:24 UTC

Summary

Status Count
READY 2
FAILING 12
PENDING 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🧹 PASS-7: fix invalid ORCID in .zenodo.json + align community to trinity-s3ai

1 participant