chore(naming): estate-wide VQL → VCL + VCL-DT/dt++ → VCL-UT rename sweep

Complete rename across 93 files in nextgen-databases. All stale naming now
replaced with the canonical forms: VCL (VeriSim Consonance Language) and
VCL-UT (VCL Usage-Tracked types).

Changes:
- VQL → VCL throughout docs, source, tests, examples, data files
- VCL-DT / VCL-dt / VCL-dt++ / VQL-dt++ → VCL-UT everywhere
- "VeriSim Query Language" → "VeriSim Consonance Language"
- "Verisimilitude Query Language" → "VeriSim Consonance Language"
- typeql-experimental/docs/vcl-dtpp-grammar.ebnf → vcl-ut-grammar.ebnf
- VCL-SPEC.adoc: two residuals fixed (line 2879 "dt++ clause", line 3027 "vcl-dt++" API string)
- Naming note boxes added to VCL-SPEC.adoc and typeql-experimental/README.adoc

Deliberate exceptions (preserved as historical context):
- verisimdb/docs/vcl-vs-vcl-dt.adoc: "VCL-DT" retained only in explicit
  historical-note section explaining the old name's origin
- Database.res.mjs: generated build artifact; source (Database.res) already correct

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: hyperpolymath

EXPLAINME.adoc

@@ -70,7 +70,7 @@ bridge between Rust and Elixir. The capability registry at
 
 VeriSimDB is at beta. The drift detection loop works (demo is live). The VCL
 query language is approximately 40% complete — basic entity CRUD and
-cross-modal consistency queries work; advanced dependent-type queries (VCL-DT)
+cross-modal consistency queries work; advanced dependent-type queries (VCL-UT)
 are planned. The "formally verified queries" claim in the README refers to
 the Idris2 ABI proofs, not end-to-end query verification (which is roadmap).
 

TOOLING-STATUS.adoc

@@ -109,7 +109,7 @@ Each query language has the same two tiers:
 2. **The safety pipeline** — TypeLL's 10 levels applied progressively behind the
    language. Simple queries exit early at L1-L2. Proof-carrying queries go to L9-L10.
 
-There is no "VCL-DT", "KQL-DT", or "GQL-DT" as separate products. Dependent type
+There is no "VCL-UT", "KQL-DT", or "GQL-DT" as separate products. Dependent type
 features are part of the safety pipeline at the appropriate levels.
 
 === The 10 Safety Levels

lithoglyph/README.adoc

@@ -25,7 +25,7 @@ toc::[]
 ====
 **Project status: Active, secondary priority.** LithoGlyph is working towards production for specialist use in **journalism, narrative arts, and media/communications**. It is not the primary priority project right now — that is https://github.com/hyperpolymath/verisimdb[VeriSimDB], which is a substantial undertaking in cross-modal database consistency. Lessons learned from VeriSimDB (drift detection, formal verification, federation architecture) will directly improve LithoGlyph when development focus returns here.
 
-**For most journalism, storytelling, and media workflows, LithoGlyph and its query language GQL are likely the database you want.** The narrative-first, reversible, audit-grade design is built specifically for this domain. https://github.com/hyperpolymath/verisimdb[VeriSimDB] and https://github.com/hyperpolymath/gql-dt[VCL/VCL-DT] become more relevant when your work involves cross-source investigative verification, large-scale entity tracking across multiple systems, long-term identity consistency, or situations where you need to prove that data across different databases has not drifted apart. For everything else — the story you want to write, the sources you want to cite, the narrative you want to build — LithoGlyph is designed to be your storage layer.
+**For most journalism, storytelling, and media workflows, LithoGlyph and its query language GQL are likely the database you want.** The narrative-first, reversible, audit-grade design is built specifically for this domain. https://github.com/hyperpolymath/verisimdb[VeriSimDB] and https://github.com/hyperpolymath/gql-dt[VCL/VCL-UT] become more relevant when your work involves cross-source investigative verification, large-scale entity tracking across multiple systems, long-term identity consistency, or situations where you need to prove that data across different databases has not drifted apart. For everything else — the story you want to write, the sources you want to cite, the narrative you want to build — LithoGlyph is designed to be your storage layer.
 
 In the long run, LithoGlyph is intended to work intimately with tools like bofig in the portfolio and serve as a database for journalism and PR applications more broadly.
 ====

typeql-experimental/0-AI-MANIFEST.a2ml

@@ -5,7 +5,7 @@
 
 ## WHAT IS THIS?
 
-This is the AI manifest for **typeql-experimental** (VCL-dt++ / TypeQL-experimental).
+This is the AI manifest for **typeql-experimental** (VCL-UT / TypeQL-experimental).
 An experimental exploration of six advanced type-theoretic extensions to VCL:
 
 1. **Linear types** — resource-counted connections via Idris2 QTT
@@ -101,7 +101,7 @@ grep -rn 'believe_me\|assert_total\|assert_smaller' src/abi/
 ## KEY RELATIONSHIPS
 
 - **Parent**: `nextgen-databases` monorepo
-- **Sibling**: `verisimdb` (VCL v3.0 base grammar, VCL-dt ~35% wired)
+- **Sibling**: `verisimdb` (VCL v3.0 base grammar, VCL-UT ~35% wired)
 - **Sibling**: `lithoglyph` (GQL-dt, Idris2 ABI patterns)
 - **Reference**: `proven` (formal verification library)
 
@@ -119,7 +119,7 @@ grep -rn 'believe_me\|assert_total\|assert_smaller' src/abi/
 - Read `.machine_readable/STATE.scm` for current status
 - Understand the dual-language split (Idris2 + ReScript)
 - Know the banned patterns (believe_me, assert_total, assert_smaller)
-- Check `docs/vcl-dtpp-grammar.ebnf` for the grammar delta
+- Check `docs/vcl-ut-grammar.ebnf` for the grammar delta
 
 ## META
 

typeql-experimental/DESIGN-2026-03-01-typeql-experimental.adoc

@@ -1,5 +1,5 @@
 // SPDX-License-Identifier: PMPL-1.0-or-later
-= Design Document: typeql-experimental (VCL-dt++)
+= Design Document: typeql-experimental (VCL-UT)
 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 :date: 2026-03-01
 :repo: nextgen-databases/typeql-experimental
@@ -8,18 +8,18 @@ Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 == Summary
 
 Create an experimental exploration space for six advanced type-theoretic
-extensions to VCL (VeriSim Query Language). These extensions leverage Idris2's
+extensions to VCL (VeriSim Consonance Language). These extensions leverage Idris2's
 native quantitative type theory (QTT) to provide compiler-enforced resource
 safety, session protocols, and effect tracking for database queries.
 
 == Motivation
 
-VCL-dt (dependently-typed VCL) is ~35% wired end-to-end in VeriSimDB, covering
+VCL-UT (dependently-typed VCL) is ~35% wired end-to-end in VeriSimDB, covering
 Pi/Sigma types, proof clauses, and basic type checking. The next frontier is
 type-level resource management — ensuring connections aren't leaked, transactions
 follow protocols, and effects are tracked statically.
 
-These features are too experimental for the production VCL-dt codebase. A
+These features are too experimental for the production VCL-UT codebase. A
 standalone exploration space allows rapid iteration without destabilising the
 existing type checker.
 

typeql-experimental/Justfile

@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: PMPL-1.0-or-later
-# typeql-experimental — Build recipes for VCL-dt++ experimental type system
+# typeql-experimental — Build recipes for VCL-UT experimental type system
 
 # Default recipe: type-check all Idris2 modules
 default: check

typeql-experimental/README.adoc

@@ -1,14 +1,29 @@
 // SPDX-License-Identifier: PMPL-1.0-or-later
-= typeql-experimental (VCL-dt++)
+= typeql-experimental (VCL-UT)
 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 :description: Experimental type-theoretic extensions to VCL
 :toc: macro
 :icons: font
 
+[NOTE]
+====
+**Naming.** This module is the **VCL-UT** extension tier.
+
+* *VCL* = VeriSim Consonance Language — the base query/type language.
+  _Consonance_ = cross-modal harmony; VeriSimDB keeps eight modality representations
+  in agreement with each other.
+* *VCL-UT* = VCL with Usage-Tracked types.
+  _Usage-Tracked_ = these extensions track resource consumption: linear consumption
+  counts, session state, side-effects, and usage limits.
+  File extension: `.vclut`.
+
+Prior names *VCL-UT* and *VCL-UT* are retired. Use **VCL-UT** exclusively.
+====
+
 == Overview
 
 **typeql-experimental** explores six advanced type-theoretic extensions to the
-VeriSim Query Language (VCL), building on the VCL-dt dependent type system
+VeriSim Consonance Language (VCL), building on the VCL-UT dependent type system
 (~35% wired in VeriSimDB). Rather than bolting these onto the production
 codebase, this is a standalone exploration space within the `nextgen-databases`
 monorepo.
@@ -130,7 +145,7 @@ grep -rn 'believe_me\|assert_total\|assert_smaller' src/abi/
 == Grammar
 
 The query language extends VCL v3.0 with six new optional clauses appended
-after the standard query. See `docs/vcl-dtpp-grammar.ebnf` for the delta
+after the standard query. See `docs/vcl-ut-grammar.ebnf` for the delta
 grammar. No keyword conflicts — all new clause keywords are disjoint from
 VCL's 60+ reserved keywords.
 

typeql-experimental/WHITEPAPER.md

@@ -12,7 +12,7 @@
 
 ## Abstract
 
-TypeQL-Experimental (VCL-dt++) explores the application of Quantitative Type
+TypeQL-Experimental (VCL-UT) explores the application of Quantitative Type
 Theory (QTT) to database query languages, demonstrating that six categories of
 runtime database errors—connection leaks, protocol violations, effect misuse,
 scope leakage, missing postcondition guarantees, and resource over-consumption—
@@ -78,7 +78,7 @@ a native feature of the language, not an encoding.
 
 ### 1.3 Contributions
 
-1. **Six type-theoretic extensions** to VCL (VeriSim Query Language) that
+1. **Six type-theoretic extensions** to VCL (VeriSim Consonance Language) that
    eliminate the six bug categories above at compile time (Section 3).
 
 2. **A dual-language architecture** where Idris2 proves properties and ReScript
@@ -96,7 +96,7 @@ a native feature of the language, not an encoding.
 
 ### 2.1 VCL v3.0
 
-VeriSim Query Language (VCL) is the query language for VeriSimDB, a multi-modal
+VeriSim Consonance Language (VCL) is the query language for VeriSimDB, a multi-modal
 database with eight query modalities (GRAPH, DOCUMENT, VECTOR, TIME_SERIES,
 SPATIAL, STATISTICAL, SEMANTIC, RELATIONAL). VCL supports cross-modal queries
 via HEXAD references (content-addressed UUIDs).

typeql-experimental/docs/type-system-spec.adoc

@@ -1,13 +1,13 @@
 // SPDX-License-Identifier: PMPL-1.0-or-later
-= VCL-dt++ Type System Specification
+= VCL-UT Type System Specification
 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 :date: 2026-03-01
 :toc: macro
 :icons: font
 
 == Overview
 
-This document specifies the formal type system for the six VCL-dt++ extensions.
+This document specifies the formal type system for the six VCL-UT extensions.
 Each extension is defined by its Idris2 types, key judgements, and soundness
 properties. The implementation lives in `src/abi/`.
 

…-experimental/docs/vcl-dtpp-grammar.ebnf …ql-experimental/docs/vcl-ut-grammar.ebnftypeql-experimental/docs/vcl-dtpp-grammar.ebnf renamed to typeql-experimental/docs/vcl-ut-grammar.ebnf typeql-experimental/docs/vcl-dtpp-grammar.ebnf renamed to typeql-experimental/docs/vcl-ut-grammar.ebnf

@@ -1,5 +1,5 @@
 (* SPDX-License-Identifier: PMPL-1.0-or-later *)
-(* VCL-dt++ (TypeQL-experimental) Grammar Delta *)
+(* VCL-UT (TypeQL-experimental) Grammar Delta *)
 (* Extends: VCL v3.0 (verisimdb/docs/vcl-grammar.ebnf, 317 lines) *)
 (* Version: 0.1.0 *)
 (* Date: 2026-03-01 *)
@@ -176,7 +176,7 @@ usage_clause = 'USAGE', 'LIMIT', positive_integer ;
    8. EXTENDED RESERVED KEYWORDS
    ============================================================================
 
-   New keywords added by VCL-dt++ (disjoint from VCL v3.0's 60+ keywords):
+   New keywords added by VCL-UT (disjoint from VCL v3.0's 60+ keywords):
    ============================================================================ *)
 
 vcldtpp_keywords = 'CONSUME' | 'AFTER' | 'USE'