ISNI
Pairing an ISNI lets ~Alter recognise the broader public-records identity that libraries, archives, and rights-management systems already hold for you. T1 is the ISNI claim; T2 confirms ownership through a MusicBrainz annotation cross-resolve.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Write to, edit, or annotate your ISNI record. The ISNI database itself remains the registrant's system of record.
- •Modify your MusicBrainz profile, except by reading the single annotation field you write yourself for the T2 cross-resolve.
- •Claim or merge ISNI records on your behalf.
- •Surface your ISNI to rights-management systems, distributors, or licensors without a separate consent row scoped to that recipient.
- •Cross-link your ISNI to other authority files (VIAF, LCNAF) and publish that linkage. We hold the linkage locally, not externally.
The OAuth or attestation scope we request is the minimum required to recognise the pattern described in What we read. Anything beyond that is structurally refused at the connector boundary, not promised by trust. How pairing works.
What we read
- Your 16-digit ISNI as you enter it.
- Whether the public ISNI SRU record exists, and which source systems assigned it.
- The MusicBrainz artist ID cross-referenced against your ISNI, when one exists.
- When a T2 upgrade is requested, the MusicBrainz annotation is read once to check for your verification token.
What we don't read
~Alter explicitly refuses these fields even when the OAuth scope or API permits them. Every refusal is enforced at the connector boundary, not by trust.
- Private or unpublished ISNI fields not surfaced in the SRU response.
- Linked-data crosswalks to other authority files (VIAF, Library of Congress, etc.) beyond what is needed to resolve T2.
- Royalty, licensing, or rights-management metadata.
- Distribution platform data tied to the ISNI (Spotify, Apple Music, etc.).
Where it lives
The ISNI + tier badge sits in ~alter's pairing ledger keyed to your ~handle. Public-record snapshots are refreshed on demand, never proactively scraped. The MusicBrainz annotation is read once at T2 upgrade and not polled again.
How to revoke
You can pair ISNI today, and you cannot yet revoke it yourself. The disconnect path for this connector is not wired, so the command below will not work and neither will asking your AI client. Contact the admin to have the pairing removed. This is stated here rather than left for you to discover, because a way in without a way out is not a choice worth making blind.
One thing is kept on purpose. The connector retains a record that this account was paired and when it was disconnected, so the same account cannot be unpaired and re-paired in quick succession to churn your identity vector. That cooldown record holds the raw profile snapshot until the window passes. It is never read into a new signal while disconnected, and it is not shared with anyone.
Pairing this connector does not enrol you in any matching, ranking, or matching surface. Every downstream use requires its own consent row. See the consent model.