Vog |>
Why Vog Footguns Glimpse Blog
|> WHY VOG

Correctness is the scarce resource.

For most of programming's history, writing code was the expensive act. AI codegen inverted that overnight — and made an old imbalance impossible to ignore.

|> 01   THE ECONOMY OF CODE HAS INVERTED

Producing code is no longer the bottleneck.

For decades the expensive act was writing code, so languages optimised the writer: brevity, sugar, keystrokes saved. When agents generate code faster than anyone can read it, that whole economy flips on its head.

What stays scarce — and grows scarcer as volume rises — is knowing the code is correct: the review, the verification, the trust a reader must establish before it ships. Catch a mistake at the source and the saving compounds with every line generated after it.

|> 02   THE COST LADDER, IN FULL

Three kinds of wrong, in ascending order of cost.

The gap between the second rung and the third is the entire argument for Vog.

PAY ONCE
Correct code
You pay when it's written, and never again. The baseline you're measuring the others against.
BOUNDED
Loud failure
It breaks on the spot. You learn it's wrong at once, right where it happened, and you pay there. The bill is annoying but it is bounded — a crash, a red test, a rejected compile.
UNBOUNDED
Silent failure
It ships looking correct and bills you later — in production, detached from the cause, compounding the entire way there. The cost is unbounded because you don't even know you're paying it. The most expensive line of code is the one that looks fine.

AI floods you with the silent rung specifically — plausible-looking wrong code, faster than review catches it. Vog's entire design converts silent failures into loud ones: unrepresentable where it can, caught at compile time where it must.

|> 03   WHO IT'S FOR

Readers before writers.

Code is read far more than it's written. Rank the audiences by that fact, with trust as the throughline, and every other decision falls out of the order.

01
Human readers
The most constrained audience, and the most important. Serve the human reader first and the rest largely follow — they are the one who must trust the code before it ships.
02
AI readers
Reviewers, maintainers, agents reasoning over the code. They want exactly what humans want: explicitness, locality, one obvious way.
03
AI writers
The high-volume authors, and the ones the language can most improve. Regularity and low optionality make their output predictable, and therefore reviewable.
04
Human writers
Last, and deliberately. The one thing unique to them — keystroke-saving sugar — is the one thing that erodes the regularity the other three depend on. It is the first cost Vog spends.
|> 04   WHAT VOG IS NOT

Deliberate choices, not gaps.

Some of the safety comes from active defense; some comes from simply not admitting the feature. Removing expressiveness is a real trade with a real cost — it is made on purpose, and it is worth naming.

No macros.
What you read is what executes. No metaprogramming layer to hide control flow, and diagnostics stay a finite bookkeeping task rather than a hygiene problem.
No reflection.
No runtime name-to-symbol resolution, no open-class redefinition. Introspection exists only over closed, statically-known sets, and only at the tooling boundary.
No magic.
No implicit dispatch, no operator overloading, no truthiness. No inheritance, so variance and substitution bugs cannot exist. Fewer ways to be surprised.

The honest caveat: this is a poor trade for a weekend MVP, and a good one for correctness-critical, long-lived, heavily-audited, agent-written systems. Vog knows which it is built for.

The repo isn't open yet. The work is out in the open.

Vog is still in design — the repository isn't open yet, but it will be under appropriate open source licenses. No mailing list, no launch date; just the thinking, shared in the open until the code and compiler are ready to share.

LANGUAGE SPEC 85%
COMPILER 60%
follow the build on bluesky |>
Vog |>
Blog
a statically typed, immutable language for the AI coding agent era · in design |> coming soon