Case Study · Registry Mirror

ALKN Security Token — Case Study

A regulated tokenised security whose issuance, custody and exchange listings are structured as a federation-verifiable evidence covering rather than a marketing surface.

Federation role of this page

Why the same URL exists here as on evidence-economy.com.

This page is a registry-mirror. It declares the same path — /case-studies/alkn-security-token/ — that NODE-20 (evidence-economy.com/case-studies/) uses, so that cross-node references resolve predictably across the federation. It does not re-host the material of the case study.

The role of this site here is definitional-origin, editorial and cross-referential. The applied source of truth for this case study — sealed digests, regulatory framing, institutional material figures — lives on the paired executive surface at NODE-20. The archival evidence lives on the segregated evidence anchor at NODE-6.

Where the material lives. Canonical applied surface: https://evidence-economy.com/case-studies/alkn-security-token/. Segregated evidence anchor: https://kosmos.evidence.ktsglobal.live/api/evidence/EL-CASE-ALKN-GI-2026-09/manifest (13 evidence objects under manifest EL-CASE-ALKN-GI-2026-09).
What this page hosts

Material on this page — deliberately minimal.

  • The case-study slug and human-readable title.
  • A one-sentence editorial abstract (the thesis above).
  • A plain narration of the registry-mirror role.
  • Outbound links to the canonical applied surface (NODE-20) and the segregated evidence anchor (NODE-6).
  • A machine-readable WebPage record whose mentions[] point at the canonical and the evidence anchor — no re-hosted claims.
What this page does not host

Material NOT on this page — by design.

NODE-18 (geometricintelligence.ai) is the definitional-origin surface for the field of Geometry Intelligence. It is not the applied-executive surface for regulated financial instruments, and it is not the segregated evidence anchor. By registry-mirror discipline, this page does not carry any of the following:

  • Sealed SHA-256 digests of case-study evidence artefacts.
  • The ClaimReview JSON-LD payload that anchors the case-study claims.
  • Categorical material figures — asset backing, wire lengths, exchange-listing figures — that are load-bearing on the canonical applied surface.
  • The regulatory disclaimer specific to the tokenised-security instrument.
  • The source-article body of the case study.

All of the above is served, canonically and unambiguously, from https://evidence-economy.com/case-studies/alkn-security-token/.

Editorial connection to the field

Why this case study appears on the field-reference site at all.

The ALKN case study is a concrete instance of a proposition made at the field level on this site: that better-structured evidence frequently outperforms more computation, and that authoritative claims about a regulated instrument can be organised as a federation-verifiable covering rather than a marketing surface. The relevant field-level notes are collected on the Field Notes page — see in particular the entries on What provenance is doing, The evidence economy, and Machine-readable authority.

The technical anchor conditions of the field — the sealed canonical definition, the fifteen DefinedTerm entries and the Node/Anchor/Edge model — are unchanged by anything on this page. This page is a registry reference; it is not a revision of any canonical material.

Status and boundaries

Boundary conditions for this registry entry.

Registry-mirror boundaries. Path parity across nodes is a federation convenience, not an endorsement of a particular claim about the instrument. NODE-18 (this site) does not mint, verify, seal, or re-publish the case-study evidence. Any dispute about the case-study contents is resolved on the canonical applied surface at https://evidence-economy.com/case-studies/alkn-security-token/, and any dispute about the archival evidence is resolved through the segregated evidence anchor at NODE-6 (manifest EL-CASE-ALKN-GI-2026-09). Publication of a registry-mirror reference on this site does not constitute a regulatory statement, a financial promotion, or a solicitation.

First published as a registry entry on 2026-09-01. Canonical claim reference on NODE-20: node-20-case-alkn-security-token.