Case study · ALKN Security Token (registry-mirror of NODE-20)
NODE-21 mirrors NODE-20's ALKN Security Token case-study path for federation path parity. NODE-20 remains the single source of truth for the ClaimReview rendering and the seven sealed-claim SHA-256 digests; those digests are pinned by NODE-6 R2 (EL-CASE-ALKN-GI-2026-09).
Registry-mirror claim
NODE-21 mirrors NODE-20's ALKN Security Token case-study path (/case-studies/alkn-security-token/) as a registry-mirror role. NODE-20 (evidence-economy.com) remains the single source of truth for the ClaimReview rendering and the seven sealed-claim SHA-256 digests; those digests are pinned by NODE-6 R2 (EL-CASE-ALKN-GI-2026-09). NODE-21 does not duplicate the canonical content.
NODE-6 evidence publishedWhat NODE-21 does not host
- The seven sealed-claim SHA-256 digests (canonical on NODE-20; pinned by NODE-6 R2).
- The ClaimReview JSON-LD payload (canonical on NODE-20).
- The categorical material-figures block (USD 1.64B / 200M / 50M — canonical on NODE-20).
- The regulatory disclaimer verbatim (canonical on NODE-20).
- The source-article snapshot (canonical on NODE-6 R2).
NODE-21's role is executive briefing translation, not evidence archival. The registry-mirror pattern preserves NODE-20's single-source-of-truth for case-study evidence while making the path resolvable federation-wide.