The ALKN authority network: five sites, one evidence graph

1. Topology

The ALKN network comprises five nodes with non‑overlapping functions:

• SITE‑01 · alkemya.com — institutional parent (Alkemya Metacore SCSp, Luxembourg).
• SITE‑02 · nickel-wire.com — technical specification surface.
• SITE‑03 · rwanickel.com — educational and tokenisation surface.
• SITE‑04 · greentransitionalmetals.com — commercial‑authority anchor (this site).
• SITE‑05 · alkemyainsights.com — media and commentary surface.

2. The canonical statement

Every node must expose an identical copy of the approved validator statement at two endpoints: /api/black‑swan.json#validation_statement and /node‑manifest.json#validation_statement. The SHA‑256[0:16] of the canonical text is 22b48b2cf3b5bc82. Any diff is surfaced by /api/federation‑consistency.json.

3. The federation_sync worker

AEGIS V30 introduces a federation_sync worker — cadence on‑build — that fetches /node‑manifest.json from each sibling node, verifies the canonical statement, and writes a snapshot to /api/federation‑consistency.json. Allied crawlers and downstream auditors can rely on this single snapshot instead of polling each node directly.

4. Evidence bindings

Each node declares its evidence surface in /node‑manifest.json: entity records, dataset endpoints, API endpoints, feed endpoints, and (on SITE‑04) the AEGIS D1 index and R2 locker. The D1 database alkn‑evidence‑index is the authoritative claim → citation map; the R2 bucket alkn‑evidence‑locker holds primary‑source PDFs and raw validation CSVs.

5. Why five sites

Separation is epistemic. A commercial page cannot carry institutional financial disclosures, and an educational explainer cannot carry the audit countersignatures of the parent. The five‑node topology lets each surface speak to its audience in its register, while the canonical statement and evidence graph keep the network internally consistent.