Skip to content

Latest commit

 

History

History
93 lines (73 loc) · 4.46 KB

File metadata and controls

93 lines (73 loc) · 4.46 KB

Database & Query-Language Registry — where each thing lives

This is the authoritative map of the Next-Gen Databases portfolio to the standalone repositories that own each database and each query language. nextgen-databases is a coordination repo: implementation content belongs in the repos below, not here.

Registered in the estate clade registry: https://github.com/hyperpolymath/gv-clade-index (see .machine_readable/CLADE.a2ml).

Resite: decisions finalised; execution per docs/migration/RESITE-DATABASES-TO-OWN-REPOS.adoc (plan) and docs/migration/RESITE-CODEX-HANDOFF.adoc (step-by-step agent command sheet).

Databases

Database Repository Status Query language (repo)

VeriSimDB (cross-modal consistency)

hyperpolymath/verisimdb

exists (canonical)

VCL — nested in verisimdb

Lithoglyph (narrative-first)

hyperpolymath/lithoglyph

to create

GNPL (narration/projection, over GQLdt) — hyperpolymath/gnpl (exists)

Glyphbase (Lithoglyph web UI)

hyperpolymath/glyphbase

to create

QuandleDB (knot-theory)

hyperpolymath/quandledb

exists (canonical)

KRL — hyperpolymath/krl

Query languages

Language Repository Status Notes

VCL (Verified Consonance Language)

(in hyperpolymath/verisimdb)

exists

Production; stays nested in verisimdb

VCL-UT (usage-tracked extension)

hyperpolymath/vcl-ut

exists (canonical)

Maps to typeql-experimental/; reconcile + delete copy

GQLdt (dependently-typed Glyph query language)

(in hyperpolymath/gnpl)

exists (canonical)

Extracted from lithoglyph/gql-dt/; lake build green. Stays nested in gnpl as GNPL’s lowering target

GNPL (narration/projection language)

hyperpolymath/gnpl

exists (canonical)

Not a query language — see note below

KRL (Knot query language)

hyperpolymath/krl

exists (canonical)

No KRL content in this monorepo

NQC (Nested Query Calculus)

hyperpolymath/nqc

to create

Already standalone in nqc/ (Gleam)

Note

GNPL was re-scoped, 2026-07-21. This registry previously recorded it as "GNPL / GQL (Glyph query language)" — i.e. a rename of GQL/GQL-dt, sourced from lithoglyph/gql-dt/ plus lithoglyph/core-factor/gql/. That reading is superseded.

GNPL is a narration/projection language: it answers "what account does this evidence support, told from whose stance, with what warrant", not "what is true in the store". It is being built as a layer on top of GQLdt in the gnpl repo and lowers to it:

GNPL --lowers to--> GQLdt --FFI--> Lithoglyph

Consequences for this registry:

  • lithoglyph/gql-dt/ was extracted to gnpl and is no longer canonical here.

  • lithoglyph/core-factor/gql/ (5 Factor files) was never migrated and will not be. It was the runtime/dynamic counterpart to GQLdt’s compile-time proofs, and a typed narration layer lowering to GQLdt supersedes it. It stays here as legacy.

  • docs/migration/RESITE-DATABASES-TO-OWN-REPOS.adoc is amended accordingly; see lithoglyph/MOVED.md.

Rationale: https://github.com/hyperpolymath/gnpl/blob/main/docs/THEORY.adoc (the general case) and docs/LITHOGLYPH.adoc (what it gives Lithoglyph specifically).

VeriSim satellites

Component Disposition

verisim-core/ (slim Julia identity-core)

→ own repo hyperpolymath/VerisimCore.jl (Julia-package pattern); create + push

verisim-modular-experiment/

folded into hyperpolymath/verisimdb as a standard feature (no longer an experiment)

Reference strategy (after extraction)

Hybrid: verisimdb and lithoglyph are git submodules of this coordination repo; every other repo is referenced by link from this registry.

What belongs in this (coordination) repo

  • Portfolio docs: README.adoc, TOPOLOGY.md, ROADMAP.adoc, EXPLAINME.adoc

  • This registry (REGISTRY.adoc)

  • Cross-database integration tests (tests/)

  • Shared infra & environment (flake.nix, guix.scm, Justfile, stapeln.toml, opsm.toml)

  • Governance & metadata (.github/, .machine_readable/, .well-known/, LICENSES/, CONTRIBUTING.md, SECURITY.md, 0-AI-MANIFEST.a2ml)

Note

The per-database directories currently in this repo are legacy and are being extracted — see docs/migration/RESITE-DATABASES-TO-OWN-REPOS.adoc. Do not add new content to them.