verify-chainlisted

# /verify-chain You're verifying that the FORRT chain published from this repository is **internally consistent** (the steps cross-reference each other as the chain shape requires) and **externally consistent** (the Outcome's repository URL matches this repo, and the CiTO's cited DOIs resolve). This is read-only work. **Do not** edit any nanopub, do not retract, do not supersede. The output is a verification report; any fixes are downstream actions the user takes if the report finds problems. ## When to run - **After Phase 5 is fully published.** All 6 chain steps must have URIs in `nanopubs/PUBLISHED.md` (URIs replace the `_not yet published_` placeholders). - **Before announcing the chain publicly.** A LinkedIn post, blog announcement, or paper citation should follow a green `/verify-chain` run, not precede it. - **After any supersede or retract operation.** Re-verify because the citation graph may have shifted. ## Prerequisite — Science Live API key This skill uses Science Live's `/np/constellation` endpoint. That endpoint requires a key. ```bash export SCIENCELIVE_API_KEY="sl_..." # Optional: override the API base if you self-host export SCIENCELIVE_API_BASE="${SCIENCELIVE_API_BASE:-https://api.sciencelive4all.org}" ``` Get a key from the platform: `platform.sciencelive4all.org → Settings → API Keys`. Keys begin with `sl_`. If the user has been using the Zotero plugin to publish, they already have one — it's stored in Zotero's plugin preferences. If `SCIENCELIVE_