refactor(rename): VQL → VCL + verisimdb → verisim

Mechanical rename across all source, docs, and configuration:
  - VQL / vql / vql_* → VCL / vcl / vcl_*
  - VeriSim Query Language → VeriSim Consonance Language
  - verisimdb → verisim (repo, module, DB name, Prometheus metrics)
  - .vql extension → .vcl
  - vql-bridge/, src/vql/, examples/vql-queries/ → vcl-equivalents
  - Rust module vql_bridge/vql_fmt → vcl_bridge/vcl_fmt

Schema impact:
  - ClickHouse database renamed: verisimdb.* → verisim.*
  - All 1108 proof_attempts rows migrated via TSV backup/restore
  - 7 PROVEN + 2 SANCTIFIED certificates regenerate identically
    against the new schema (verified live)
  - Prover Enum8 now includes all 42 variants (cadical, kissat, spass, etc.)

Terminology framing (from migration instructions):
  VeriSim operations are **propositions to a consonance engine**, not queries
  against a passive store. Operations split into propositional (DECLARE,
  ASSERT, RETRACT) and epistemic (INSPECT, VERIFY).

Preserved unchanged:
  - github.com/hyperpolymath/verisimdb URLs (GitHub repo rename pending)
  - "query" in general English prose (context-sensitive Step 3 work)
  - Operation names (SELECT/INSERT/DELETE → INSPECT/ASSERT/RETRACT) — Step 4
    requires per-occurrence judgement, not automated
  - -ut type suffixes — Step 5 per-occurrence total-vs-sound decision

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.claude/CLAUDE.md

@@ -61,8 +61,8 @@ The following files in `.machine_readable/` contain structured project metadata:
 ### ALLOWED
 - **Rust** - Core database engine, modality stores
 - **Elixir** - OTP orchestration layer
-- **ReScript** - VQL parser, federation registry
-- **VQL** - VeriSim Query Language (native query interface, NOT SQL)
+- **ReScript** - VCL parser, federation registry
+- **VCL** - VeriSim Consonance Language (native query interface, NOT SQL)
 
 ### BANNED
 - Python - Use Rust instead
@@ -101,12 +101,12 @@ cd elixir-orchestration && mix compile
 Use Podman (NOT Docker):
 ```bash
 # In-memory (default)
-podman build -t verisimdb:latest -f container/Containerfile .
-podman run -p 8080:8080 verisimdb:latest
+podman build -t verisim:latest -f container/Containerfile .
+podman run -p 8080:8080 verisim:latest
 
 # Persistent storage (redb graph + file-backed Tantivy + WAL)
-podman build -t verisimdb:persistent --build-arg FEATURES=persistent -f container/Containerfile .
-podman run -p 8080:8080 -v verisimdb-data:/data verisimdb:persistent
+podman build -t verisim:persistent --build-arg FEATURES=persistent -f container/Containerfile .
+podman run -p 8080:8080 -v verisim-data:/data verisim:persistent
 ```
 
 ### Verified Container Deployment (stapeln)
@@ -230,13 +230,13 @@ VeriSimDB needs to service all ~290 hyperpolymath repos from GitHub Actions CI.
 
 ### Architecture: Git-Backed Flat-File Store
 
-Instead of running verisimdb as a persistent server in GitHub, use a **git-backed data repo**:
+Instead of running verisim as a persistent server in GitHub, use a **git-backed data repo**:
 
 ```
-hyperpolymath/verisimdb-data (new repo)
+hyperpolymath/verisim-data (new repo)
 ├── scans/                    # panic-attack scan results per repo
 │   ├── echidna.json
-│   ├── verisimdb.json
+│   ├── verisim.json
 │   └── ...
 ├── hardware/                 # hardware-crash-team findings
 │   └── latest-scan.json
@@ -249,28 +249,28 @@ hyperpolymath/verisimdb-data (new repo)
 
 ### How It Works
 
-1. **Each repo's CI** runs panic-attack, produces JSON, pushes to `verisimdb-data` via workflow dispatch
-2. **verisimdb-data ingest workflow** receives the JSON, stores it, updates the index
-3. **Query** by checking out verisimdb-data and reading JSON (no server needed)
+1. **Each repo's CI** runs panic-attack, produces JSON, pushes to `verisim-data` via workflow dispatch
+2. **verisim-data ingest workflow** receives the JSON, stores it, updates the index
+3. **Query** by checking out verisim-data and reading JSON (no server needed)
 4. **Local dev**: Run `verisim-api` server locally, load from the data repo
 
 ### Implementation Steps (for Sonnet)
 
-1. Create `verisimdb-data` repo from rsr-template-repo
+1. Create `verisim-data` repo from rsr-template-repo
 2. Add `ingest.yml` workflow that accepts repository_dispatch events with scan payloads
 3. Add a reusable workflow `scan-and-report.yml` that repos can call:
    - Runs `panic-attack assail` on the repo
-   - Sends results to verisimdb-data via repository_dispatch
+   - Sends results to verisim-data via repository_dispatch
 4. Add the reusable workflow to 2-3 pilot repos first (echidna, panic-attacker, ambientops)
-5. Add a `query.sh` script that clones verisimdb-data and searches the index
+5. Add a `query.sh` script that clones verisim-data and searches the index
 
 ### Future: Persistent Server
 
 When ready to scale beyond flat files:
 - Deploy verisim-api to **Fly.io free tier** (3 shared VMs, 1GB persistent volume)
 - Use the Containerfile already in `container/`
 - GitHub Actions calls the Fly.io endpoint instead of repository_dispatch
-- Keep verisimdb-data as backup/mirror
+- Keep verisim-data as backup/mirror
 
 ## Hypatia Integration Pipeline
 
@@ -294,15 +294,15 @@ panic-attack assail → ScanIngester → octad octads → PatternQuery → Dispa
      `category_distribution/0`, `temporal_trends/1`, `repos_by_severity/1`, `weakness_hotspots/0`
 
 3. **DispatchBridge** (`dispatch_bridge.ex`): Bridge to Hypatia dispatch pipeline
-   - Reads JSONL dispatch manifests from `verisimdb-data/dispatch/`
+   - Reads JSONL dispatch manifests from `verisim-data/dispatch/`
    - Tracks execution status and feeds outcomes back for drift tracking
    - API: `read_pending/1`, `read_dispatch_log/2`, `read_all_dispatch_logs/1`,
      `read_outcomes/1`, `summarize/1`, `feedback_to_drift/1`, `ingest_dispatch_summary/1`
 
 ### Remaining: Fleet Dispatch (Live Execution)
 
 Fleet dispatch is logged to JSONL but not yet executing live GraphQL mutations.
-Requires GitHub PAT with `repo` scope — see `verisimdb-data/INTEGRATION.md`.
+Requires GitHub PAT with `repo` scope — see `verisim-data/INTEGRATION.md`.
 
 ## Model Router (Future Tool - Sonnet Task)
 
@@ -334,7 +334,7 @@ User prompt → Haiku classifier → Route to:
 See `KNOWN-ISSUES.adoc` at repo root for all honest gaps. All 25 issues resolved.
 
 Resolved in recent sessions:
-- VQL-DT type checker wired end-to-end (Elixir-native + ReScript + Rust ZKP bridge)
+- VCL-DT type checker wired end-to-end (Elixir-native + ReScript + Rust ZKP bridge)
 - 11 proof types: EXISTENCE, INTEGRITY, CONSISTENCY, PROVENANCE, FRESHNESS, ACCESS, CITATION, CUSTOM, ZKP, PROVEN, SANCTIFY
 - Multi-proof parsing: PROOF A(x) AND B(y) splits correctly
 - Modality compatibility validation (INTEGRITY needs semantic, PROVENANCE needs provenance, etc.)
@@ -343,9 +343,9 @@ Resolved in recent sessions:
 - oxrocksdb-sys C++ dependency eliminated (Oxigraph feature-flagged, redb pure-Rust backend added)
 - protoc build dependency eliminated (proto code pre-generated)
 - stapeln container ecosystem integrated (compose.toml, .gatekeeper.yaml, manifest.toml, ct-build.sh)
-- VQL Playground wired to real backend (ApiClient.res, async execution, demo mode fallback, octad modalities)
+- VCL Playground wired to real backend (ApiClient.res, async execution, demo mode fallback, octad modalities)
 - PanLL database module protocol (DatabaseModule.res, DatabaseRegistry.res — VeriSimDB/QuandleDB/LithoGlyph)
-- Product telemetry: opt-in collector (ETS), reporter (JSON), 19 telemetry tests, VQL executor + drift monitor wired
+- Product telemetry: opt-in collector (ETS), reporter (JSON), 19 telemetry tests, VCL executor + drift monitor wired
 - PanLL telemetry dashboard panel with modality heatmap, query patterns, performance metrics
 
 ## Hypatia Integration Status
@@ -354,12 +354,12 @@ Resolved in recent sessions:
 - ScanIngester: panic-attack JSON → octad octads (Document, Graph, Temporal, Vector, Provenance, Semantic)
 - PatternQuery: cross-repo analytics (pipeline health, severity distribution, temporal trends, hotspots)
 - DispatchBridge: reads JSONL dispatch manifests, summarizes outcomes, feeds drift tracking
-- Hypatia VQL layer reads verisimdb-data flat files directly
-- Built-in Elixir VQL parser (no external Deno/Node needed)
+- Hypatia VCL layer reads verisim-data flat files directly
+- Built-in Elixir VCL parser (no external Deno/Node needed)
 - 954 canonical patterns tracked across 298 repos
 
 **Needs PAT:** Automated cross-repo dispatch requires a GitHub PAT with `repo` scope.
-See `verisimdb-data/INTEGRATION.md` for PAT setup instructions.
+See `verisim-data/INTEGRATION.md` for PAT setup instructions.
 
 ## User Preferences
 
@@ -371,7 +371,7 @@ See `verisimdb-data/INTEGRATION.md` for PAT setup instructions.
 ## Repository Structure
 
 ```
-verisimdb/
+verisim/
 ├── Cargo.toml                 # Workspace definition
 ├── rust-core/                 # Rust crates
 │   ├── verisim-graph/

ABI-FFI-README.md

@@ -25,7 +25,7 @@ This library follows the **Hyperpolymath RSR Standard** for ABI and FFI design:
                   ▼
 ┌─────────────────────────────────────────────┐
 │  C Headers (auto-generated)                 │
-│  generated/abi/verisimdb.h                │
+│  generated/abi/verisim.h                │
 └─────────────────┬───────────────────────────┘
                   │
                   │ imported by
@@ -49,7 +49,7 @@ This library follows the **Hyperpolymath RSR Standard** for ABI and FFI design:
 ## Directory Structure
 
 ```
-verisimdb/
+verisim/
 ├── src/
 │   ├── abi/                    # ABI definitions (Idris2)
 │   │   ├── Types.idr           # Core type definitions with proofs
@@ -66,11 +66,11 @@ verisimdb/
 │       ├── test/
 │       │   └── integration_test.zig
 │       └── include/
-│           └── verisimdb.h   # C header (optional, can be generated)
+│           └── verisim.h   # C header (optional, can be generated)
 │
 ├── generated/                  # Auto-generated files
 │   └── abi/
-│       └── verisimdb.h       # Generated from Idris2 ABI
+│       └── verisim.h       # Generated from Idris2 ABI
 │
 └── bindings/                   # Language-specific wrappers (optional)
     ├── rust/
@@ -198,7 +198,7 @@ zig build test                    # Run tests
 
 ```bash
 cd src/abi
-idris2 --cg c-header Types.idr -o ../../generated/abi/verisimdb.h
+idris2 --cg c-header Types.idr -o ../../generated/abi/verisim.h
 ```
 
 ### Cross-Compile
@@ -221,7 +221,7 @@ zig build -Dtarget=x86_64-windows
 ### From C
 
 ```c
-#include "verisimdb.h"
+#include "verisim.h"
 
 int main() {
     void* handle = verisimdb_init();
@@ -263,7 +263,7 @@ main = do
 ### From Rust
 
 ```rust
-#[link(name = "verisimdb")]
+#[link(name = "verisim")]
 extern "C" {
     fn verisimdb_init() -> *mut std::ffi::c_void;
     fn verisimdb_free(handle: *mut std::ffi::c_void);
@@ -354,7 +354,7 @@ When modifying the ABI/FFI:
 
 2. **Generate C header**
    ```bash
-   idris2 --cg c-header src/abi/Types.idr -o generated/abi/verisimdb.h
+   idris2 --cg c-header src/abi/Types.idr -o generated/abi/verisim.h
    ```
 
 3. **Update FFI implementation** (`ffi/zig/src/main.zig`)

BEST-IN-CLASS-ROADMAP.md

@@ -5,41 +5,41 @@ Criticality-ordered plan. Toolchain first, then infrastructure, then ecosystem.
 **Completed prerequisites** (this session):
 - [x] verisim-planner crate (cost-based query planning)
 - [x] Triple API (REST + GraphQL + gRPC)
-- [x] VQL AST → LogicalPlan bridge
+- [x] VCL AST → LogicalPlan bridge
 - [x] Proof obligation costing (per-type: existence→ZKP)
 - [x] Adaptive tuning (actual vs estimated latency feedback)
 - [x] Post-processing + cross-modal cost models
 - [x] ZKP scheme decision: PLONK (documented in Trustfile)
 
 ---
 
-## Phase 1: VQL Toolchain (HIGHEST PRIORITY)
+## Phase 1: VCL Toolchain (HIGHEST PRIORITY)
 
-### 1.1 VQL REPL — Rust CLI
+### 1.1 VCL REPL — Rust CLI
 **Criticality: CRITICAL** | Effort: Medium | Crate: `verisim-repl`
 
 Every database has an interactive shell. Without one, VeriSimDB is unusable
 for exploration and debugging.
 
-- Rust CLI binary (`vql` command)
+- Rust CLI binary (`vcl` command)
 - Readline/rustyline for input editing, history, multiline
 - HTTP client to verisim-api (configurable endpoint)
 - Commands: `\connect`, `\explain`, `\timing`, `\format json|table|csv`
-- Syntax highlighting for VQL keywords
+- Syntax highlighting for VCL keywords
 - Tab completion for modalities, proof types
 - Output formatters: table (default), JSON, CSV
 - `.vqlrc` config file support
 
-### 1.2 VQL REPL — Elixir IEx Extension
-**Criticality: HIGH** | Effort: Small | Module: `VeriSim.VQL.IEx`
+### 1.2 VCL REPL — Elixir IEx Extension
+**Criticality: HIGH** | Effort: Small | Module: `VeriSim.VCL.IEx`
 
-- `use VeriSim.VQL.IEx` in IEx sessions
-- `vql("SELECT GRAPH FROM OCTAD ...")` function
+- `use VeriSim.VCL.IEx` in IEx sessions
+- `vcl("SELECT GRAPH FROM OCTAD ...")` function
 - Pretty-printed results with modality indicators
-- `vql_explain/1` for EXPLAIN output
+- `vcl_explain/1` for EXPLAIN output
 - Direct in-process execution (no HTTP round-trip)
 
-### 1.3 VQL Language Server (LSP)
+### 1.3 VCL Language Server (LSP)
 **Criticality: HIGH** | Effort: Large | Crate: `verisim-lsp`
 
 - Diagnostics: parse errors, unknown modalities, type mismatches
@@ -49,11 +49,11 @@ for exploration and debugging.
 - VS Code extension + Neovim plugin
 - Uses existing ReScript parser via JSON bridge
 
-### 1.4 VQL Formatter
+### 1.4 VCL Formatter
 **Criticality: MEDIUM** | Effort: Small | Module in `verisim-repl`
 
-- `vql fmt` subcommand
-- Canonical formatting for VQL queries
+- `vcl fmt` subcommand
+- Canonical formatting for VCL queries
 - Keyword uppercasing, consistent indentation
 - Integrates with LSP `textDocument/formatting`
 
@@ -137,7 +137,7 @@ Configurable by admin, overridable by user, defaults to global.
 ### 3.4 ZKP Integration (PLONK)
 **Criticality: HIGH** | Effort: Large
 
-Real zero-knowledge proof verification for VQL-DT PROOF clause.
+Real zero-knowledge proof verification for VCL-DT PROOF clause.
 Scheme: PLONK (see contractiles/trust/Trustfile for rationale).
 
 - `ark-plonk` integration in verisim-semantic
@@ -202,7 +202,7 @@ Close the loop between estimated and actual costs.
 
 - Parse-once, execute-many for repeated queries
 - Plan caching (skip re-optimization for identical plans)
-- Parameterized queries (prevent VQL injection)
+- Parameterized queries (prevent VCL injection)
 - Cache invalidation on schema/config changes
 
 ### 5.3 Result Streaming
@@ -245,7 +245,7 @@ Close the loop between estimated and actual costs.
 **Criticality: MEDIUM** | Effort: Large
 
 - Federation resolver returns real results (currently empty)
-- Cross-instance VQL queries
+- Cross-instance VCL queries
 - Drift-aware federation (respect drift policies)
 - Federation discovery protocol
 
@@ -266,16 +266,16 @@ Can't claim best-in-class without numbers.
 ### 7.2 Client Libraries
 **Criticality: HIGH** | Effort: Medium
 
-- Rust SDK (typed, async, with VQL builder)
+- Rust SDK (typed, async, with VCL builder)
 - Elixir SDK (direct BEAM integration)
-- ReScript SDK (VQL builder + type-safe results)
+- ReScript SDK (VCL builder + type-safe results)
 - Each SDK: connection pooling, retry logic, auth
 
 ### 7.3 Documentation Site
 **Criticality: MEDIUM** | Effort: Medium
 
 - API reference (auto-generated from proto + GraphQL schema)
-- VQL language guide with examples
+- VCL language guide with examples
 - Architecture guide (Marr's three levels)
 - Tutorial: "Build a multimodal search in 10 minutes"
 - Deployment guide (Podman + Containerfile)
@@ -323,23 +323,23 @@ Can't claim best-in-class without numbers.
 
 | # | Item | Phase | Criticality |
 |---|------|-------|-------------|
-| 1 | VQL REPL (Rust CLI) | 1.1 | CRITICAL |
+| 1 | VCL REPL (Rust CLI) | 1.1 | CRITICAL |
 | 2 | Write-Ahead Log | 2.1 | CRITICAL |
 | 3 | Real normalizer regeneration | 4.1 | CRITICAL |
 | 4 | Authentication | 3.1 | CRITICAL |
 | 5 | ACID transactions | 2.2 | CRITICAL |
-| 6 | VQL REPL (Elixir IEx) | 1.2 | HIGH |
+| 6 | VCL REPL (Elixir IEx) | 1.2 | HIGH |
 | 7 | ZKP/PLONK integration | 3.4 | HIGH |
 | 8 | Authorization (RBAC) | 3.2 | HIGH |
 | 9 | Query profiling (EXPLAIN ANALYZE) | 5.1 | HIGH |
-| 10 | VQL LSP | 1.3 | HIGH |
+| 10 | VCL LSP | 1.3 | HIGH |
 | 11 | Persistence backends | 2.3 | HIGH |
 | 12 | Benchmarks vs ArangoDB/SurrealDB/Virtuoso | 7.1 | HIGH |
 | 13 | Client libraries | 7.2 | HIGH |
 | 14 | Snapshots & backup | 2.4 | HIGH |
 | 15 | Conflict resolution | 4.2 | HIGH |
 | 16 | Replication | 6.1 | HIGH |
-| 17 | VQL formatter | 1.4 | MEDIUM |
+| 17 | VCL formatter | 1.4 | MEDIUM |
 | 18 | Encryption at rest | 3.3 | MEDIUM |
 | 19 | Result streaming | 5.3 | MEDIUM |
 | 20 | Prepared statements | 5.2 | MEDIUM |

CHANGELOG.adoc

@@ -62,12 +62,12 @@ All notable changes to VeriSimDB are documented here. This project uses https://
 - **Circuit Registry** (`circuit_registry.rs`): In-memory registry mapping circuit names to compiled R1CS verification functions.
 - **Circuit Compiler** (`circuit_compiler.rs`): DSL gates (AND, OR, XOR, NOT, LinearCombination) compiled to R1CS constraints.
 - **Verification Key Store** (`verification_keys.rs`): Per-circuit keys with rotation, federation export/import as `KeyExportBundle`.
-- **VQL Circuit DSL** (`VQLCircuit.res`): ReScript types for circuit definition with `parseCustomProof` and `serializeCircuitDef`.
+- **VCL Circuit DSL** (`VQLCircuit.res`): ReScript types for circuit definition with `parseCustomProof` and `serializeCircuitDef`.
 
 ==== Homoiconicity — Queries as Octads (Phase 7)
-- **QueryOctadBuilder** (`query_octad.rs`): Stores VQL queries as octads across all 6 modalities (document=query text, graph=parse tree, vector=embedding, tensor=cost vector, semantic=proof obligations, temporal=execution history).
+- **QueryOctadBuilder** (`query_octad.rs`): Stores VCL queries as octads across all 6 modalities (document=query text, graph=parse tree, vector=embedding, tensor=cost vector, semantic=proof obligations, temporal=execution history).
 - **API endpoints**: `POST /queries` stores a query as octad. `POST /queries/similar` finds similar past queries by vector similarity. `PUT /queries/{id}/optimize` re-plans and updates cost vector.
-- **VQL REFLECT keyword**: `SELECT * FROM REFLECT WHERE FULLTEXT CONTAINS 'drift'` queries the query store itself. Meta-circular: REFLECT queries are themselves stored as octads.
+- **VCL REFLECT keyword**: `SELECT * FROM REFLECT WHERE FULLTEXT CONTAINS 'drift'` queries the query store itself. Meta-circular: REFLECT queries are themselves stored as octads.
 - **Elixir REFLECT executor**: Routes REFLECT source queries to the query store via text search.
 
 === Changed
@@ -90,16 +90,16 @@ All notable changes to VeriSimDB are documented here. This project uses https://
 
 === Added
 - Initial alpha release with 6 modality stores (Graph, Vector, Tensor, Semantic, Document, Temporal).
-- VQL parser (ReScript) with dependent-type and slipstream execution paths.
+- VCL parser (ReScript) with dependent-type and slipstream execution paths.
 - Elixir/OTP orchestration layer with GenServers.
 - Rust HTTP API server (verisim-api) with REST endpoints.
 - Octad entity management (create, read, update, delete, search).
 - Drift detection with 6 drift types and configurable thresholds.
 - Self-normalization with vector and document regeneration strategies.
 - Federation architecture with KRaft-inspired consensus.
-- GitHub CI integration via verisimdb-data git-backed repo.
+- GitHub CI integration via verisim-data git-backed repo.
 - Hypatia VeriSimDB connector for pattern detection.
 - Criterion benchmarks for all modality stores.
-- VQL grammar (ISO/IEC 14977 EBNF compliant).
-- VQL formal semantics (operational + type system).
+- VCL grammar (ISO/IEC 14977 EBNF compliant).
+- VCL formal semantics (operational + type system).
 - Comprehensive documentation (WHITEPAPER, consultation papers, deployment guide).