ISO 20022 ruleset is blocked — no reachable authoritative source

[kinlane]

Mirror of api-commons#10, tracked here because it is the one piece of planned coverage that is genuinely stuck.

An ISO 20022 Spectral ruleset cannot be built to the standard the other four are held to, because every authoritative source is unreachable from the working environment:

Source	Holds	Result
iso20022.org	the standard, message repository, external code sets	resolves via Akamai, times out
iso.org	ISO 20022 parts 1–8	403
swift.com	registrar for BIC (ISO 9362) and IBAN (ISO 13616)	times out
europeanpaymentscouncil.eu	SEPA rulebooks	403

Reachable and authoritative: GLEIF (LEI), SIX Group (ISO 4217), ECB (TARGET usage guidelines) — the component standards ISO 20022 carries, not ISO 20022 itself. GitHub mirrors of the XSDs exist but are low-star third-party redistributions; citing one as the standard is exactly the provenance failure the org exists to avoid.

There is also a scope question

ISO 20022 is a message standard; Spectral lints API descriptions. Two candidate scopes:

• A (preferred) — govern an API that carries ISO 20022 payloads: message identifier format (pain.001.001.09), BIC/IBAN/LEI/ISO 4217/ISO 3166 discipline, amount always paired with currency, Max{n}Text caps, ISO 8601 dates.
• B — validate message instances against their XSD. Not a Spectral job; duplicates existing tooling.

Unblocks

Either fetch the message definitions from a network that can reach iso20022.org (payments first: pain, pacs, camt) and drop them somewhere in the org — or narrow the scope to the identifier discipline GLEIF and SIX can ground today, shipped under a name that says so, not under "ISO 20022 conformance".