You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ecosystem-consistency follow-on: matches the canonical rename landed
2026-04-05 in verisimdb, hypatia, gitbot-fleet, echidna, and vql-ut.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: EXPLAINME.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ The README makes claims. This file backs them up.
9
9
10
10
=== Claim 1: 10-Level Type Safety for Any Query Language Without Modifying the Database
11
11
12
-
*From README:* "TypedQLiser adds formal type safety to any query language — SQL, GraphQL, Cypher, SPARQL, KQL, VQL, or anything else — without modifying the database... Queries go in, TypedQLiser proves properties about them... and then passes the original query through unchanged. The database never knows it's there."
12
+
*From README:* "TypedQLiser adds formal type safety to any query language — SQL, GraphQL, Cypher, SPARQL, KQL, VCL, or anything else — without modifying the database... Queries go in, TypedQLiser proves properties about them... and then passes the original query through unchanged. The database never knows it's there."
13
13
14
14
*Evidence:* The core type system at `src/abi/` defines 10 levels of type safety as dependent types: Level 1 (Parse-time safety) proves syntactic validity; Level 2 (Schema-binding) proves table/field references exist; Level 3 (Type-compatible operations) proves no type mismatches; Level 4 (Null-safety) proves nullable paths are handled; Level 5 (Injection-proof) proves user input cannot alter query structure; Level 6 (Result-type safety) proves return type is known at compile time; Levels 7-10 (Cardinality, Effect-tracking, Temporal, Linearity) prove resource consumption and execution properties. The plugin architecture at `src/plugins/` allows each query language (SQL, GraphQL, Cypher, etc.) to provide its own parser and type rules. The critical property is that TypedQLiser is a compile-time tool, not a rewriter: the original query passes through unchanged to the database. See `docs/architecture.adoc` for proofs and type kernel design. **Caveat:** This is pre-alpha; only the architecture and Idris2 proof framework are designed. SQL and GraphQL plugins are priority but not yet implemented.
15
15
@@ -37,11 +37,11 @@ The README makes claims. This file backs them up.
37
37
TypedQLiser is the #1 priority in the -iser ecosystem (TypedQLiser → Chapeliser → VeriSimiser → Squeakwell). Uses:
38
38
- **Idris2 ABI + Zig FFI standard** — Same architecture as https://github.com/hyperpolymath/proven[proven], https://github.com/hyperpolymath/gossamer[gossamer], https://github.com/hyperpolymath/idaptik[idaptik]
39
39
- **TypeLL type theory** — Shared foundation for all query type checking
40
-
- **VQL-UT** — Can be deployed as a TypedQLiser plugin for VeriSimDB queries
40
+
- **VCL-total** — Can be deployed as a TypedQLiser plugin for VeriSimDB queries
41
41
42
42
Related projects:
43
43
- https://github.com/hyperpolymath/typell[TypeLL] — Type theory foundation (10 levels)
44
-
- https://github.com/hyperpolymath/vql-ut[VQL-UT] — VQL-specific type safety (VeriSimDB queries)
44
+
- https://github.com/hyperpolymath/vql-ut[VCL-total] — VCL-specific type safety (VeriSimDB queries)
45
45
- https://github.com/hyperpolymath/iseriser[-iser ecosystem] — Meta-framework for domain-specific query tools
46
46
47
47
== File Map
@@ -61,7 +61,7 @@ Related projects:
61
61
| `src/plugins/graphql.rs` | GraphQL plugin — Level 6 support
Copy file name to clipboardExpand all lines: PROOF-NEEDS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@
35
35
36
36
## Priority
37
37
38
-
**MEDIUM** — Code generator correctness is important but downstream of VQL-UT and TypeLL. Focus proofs on SQL generation first as it directly affects data integrity.
38
+
**MEDIUM** — Code generator correctness is important but downstream of VCL-total and TypeLL. Focus proofs on SQL generation first as it directly affects data integrity.
0 commit comments