Lines labelled “semantic pairing” describe design relationships; they do not assert a working integration or transferred proof guarantee.
flowchart LR
V[VeriSimDB] ---|semantic pairing| VCL[VCL-UT]
L[Lithoglyph] ---|semantic pairing| G[GNPL]
B[Glyphbase] ---|application surface| L
Q[QuandleDB] ---|semantic pairing| K[KRL]
VO[Vocarium] ---|semantic pairing| H[Hermeneia]
S[Skein.jl] -->|library used by| Q
KT[KnotTheory.jl] -->|library used by| Q
T[Tangle: independent Turing-complete language]
The four languages express different obligations: consonance/admissibility, narration/warrants, knot resolution, and use-relative sufficiency. Shared storage or retrieval mechanisms do not make their semantics interchangeable.
Skein.jl, KnotTheory.jl and Tangle have independent purposes. Their common knot subject matter does not turn them into successive compiler stages or assign each a single KRL operation.
Registry identifies canonical repositories. Evidence ledger states tested boundaries and remaining gaps. Roadmap identifies the next substantive implementation work.