Public correction record

Runic script is not cryptography

Correction

Runic notation can be part of a protocol, but confidentiality, integrity, authentication, authorization, freshness, and replay protection require modern cryptographic and systems controls.

Stable record: COR-K08-001
Claim status: CORRECTED
Last reviewed: 2026-08-16
Research cutoff: 2026-08-16
Source type: PUBLIC CORRECTION
Currentness: Current for release 2.1.0; external sources require periodic revalidation.
Correction state: No unresolved public correction recorded for this release.
Machine record: Static JSON record

Prior record

Source language sometimes treats historical ciphers, unusual glyphs, or bounded symbols as inherently secure.

Reason for correction

A writing system and historical cipher tradition do not satisfy modern security definitions.

Affected record

REP-K08-057, REP-K08-060. Correction date: 2026-08-15.

Supporting sources

Unicode 17.0 Runic Code Chart — Unicode Consortium; Unicode 17.0; OFFICIAL CHARACTER CODE CHART. Exact claim-support entries: 1. Revalidated 2026-08-15T23:55:00Z.
FIPS 204 — Module-Lattice-Based Digital Signature Standard — NIST; FIPS 204; FINAL. Exact claim-support entries: 1. Revalidated 2026-08-15T23:55:00Z.

Correction semantics

The prior record remains preserved for history. The corrected record is active for K02. Correction does not erase provenance, create retroactive authority, or prove every adjacent proposition.