Parserlex · parse · validate
3 items●shipped2 ○planned1
Build log · v0.1.0 · canonical
What's shipped, what's in flight, what's next.
This page is the canonical record. Updated when commits land — not before, not after. The animation below is Zanith's actual schema graph at 1,000 models, gently rotating. The amber nodes are the load-bearing models; the grey ones are their relations. None of it ships at build time.
version
0.1.0
models in graph
1,000
tests passing
191 / 192
ESM bundle
88.97 KB
days · since first commit
—
last build · 47s ago
02 — Right nowall systems · green
The state of the engine, at the moment you opened this page.
ci · main · run #1247passed
Test breakdown
191 / 192 · 1.03s
- ✓test/compiler/select.test.ts8 tests
- ✓test/compiler/insert.test.ts5 tests
- ✓test/expression/where.test.ts18 tests
- ✓test/schema/parser.test.ts15 tests
- ✓test/benchmark/scale.test.ts6 tests
- ⚠test/benchmark/execution.test.ts1 test
Build artifact
88.97 KB · ESM
Type defs
35.44 KB · .d.ts
Coverage
94.2% lines
vitest · v0.34.6next run · on push
recent commits · main5 shown
- 8fa12e02h
compiler: cache parameter index across joins
● head · ci passed
- 3c7b91a5h
graph: precompute relation reverse-lookup map
- 11f482d1d
test(scale): add 5k-model benchmark suite
- 9a02d351d
adapter/pg: wire onQuery debug hook
- bbc3e172d
expression: collapse nested AND blocks
streaming from · main
03 — The map
The roadmap, laid out by the engine's own architecture.
Six lanes — the four engine layers plus tooling and site/docs. Each feature sits at the intersection of its layer and its status. On phones, tap a feature to inspect; on desktop, hover.
●shipped· 19◐in flight· 6○planned· 4·horizon· 332 features · 6 lanes
Graphruntime structure
3 items●shipped3
CompilerAST → SQL
7 items●shipped2 ◐in flight4 ·horizon1
Adapterwire driver
7 items●shipped5 ○planned1 ·horizon1
Toolingcli · devx
7 items●shipped4 ◐in flight1 ○planned1 ·horizon1
Site & docsthe public surface
5 items●shipped3 ◐in flight1 ○planned1
04 — Release tracks
Same map, sliced by version.
What ships in each release, in one place. The map above answers where in the engine? This row answers when?
shipped· 2in flight· 1planned· 1horizon· 1◐v0.3 · 49%5 tracks · v0.1 → v1.0
shippedv0.1
Foundation
shipped April 2026
The runtime engine, end to end.
Schema parser
Chevrotain + validator
Runtime graph
1k models, 3.4MB
Query compiler
Parameterized SQL on every path
ModelAPI · CRUD
find / create / update / delete
WHERE operators
14 operators, 5 groups
Transactions
Auto-rollback on throw
Adapters · pg + postgres.js
5-method interface
TypeScript inference
Compile-time field safety
shippedv0.2
Productionisation
shipped April 2026
The engine grows the surfaces a team actually adopts.
Migrations
generate · plan · verify · up · down · risk-scored
Recovery (Phase 2)
soft-drop · archive · restore · cleanup
Studio · web UI
8 tabs across workspace + database levels
SQLite adapter
better-sqlite3 · file or :memory:
SSL · SSH tunnels
TLS modes + bastion-tunneled Postgres
CLI
zanith migrate · recover · studio · db
in flightv0.3
Query API
target · Q3 2026
The model API gets its missing 30%.
progress49%
include · joins72%
eager fetch in one statement
Aggregates55%
groupBy/having on ModelAPI
Window functions40%
rank, partition, OVER
Subquery operators30%
exists, in
Schema introspection · CLI
pg_catalog → .zanith emitter
plannedv0.4
Beyond Postgres
target · Q4 2026
Multi-database, properly.
MySQL · MariaDB
Dialect-aware compiler path
Source maps · errors
Map AST nodes to source positions
Sourced benchmarks
Matched workloads vs Prisma/Drizzle
Docs · all 23 routes filled
Reference complete
horizonv1.0
Production
target · Speculative
What signals the engine is enterprise-ready.
Stable public API
SemVer commitments, deprecation policy
EXPLAIN integration · ModelAPI
Query plans in the typed client (Studio already has it)
Edge adapters
D1 · Neon serverless, exploratory
Long-running stability
Memory churn, leak budgets