This is the coordination repository for four database/language families. Canonical implementations live in their own repositories; the registry maps ownership. Remaining per-project directories here are extraction remnants.

These are not interchangeable record-selection syntaxes. Their value depends on what an operation means, what evidence authorises it, and what remains unresolved when that evidence is missing. Retrieval, filtering and storage remain useful supporting operations. They do not determine the public language designs, and no additional public reporting language is precommitted.

The evidence ledger distinguishes implemented components, executable tests, formal obligations and integration gaps. It reports concrete boundaries instead of whole-project completion percentages.

Current hardening includes rejection of unimplemented Lithoglyph proof verifiers, a runnable private typed substrate for GNPL, and KRL controls preventing index candidates from being advertised as checked equivalence results. These changes do not constitute full narration execution or a complete knot resolution engine.

Skein.jl and KnotTheory.jl are independent Julia libraries with their own storage and mathematical purposes. QuandleDB uses them. Tangle is a separate Turing-complete language for knot mathematics. Shared knot theory creates no KRL-to-Tangle compilation pipeline and transfers no proof guarantees.

See the relationship map and the engineering priorities. Cross-family integration should preserve each family’s semantic contract, including uncertainty, refusal and provenance.