THE CASE FOR COBOL ON THE WEB

COBOL was right.

Three trillion dollars move through COBOL every day. Not because nobody replaced it. Because it was designed for something nobody else figured out: encoding business intent so precisely that the machine understands it directly.

AI AND INTENT

AI was trained on intent.

When AI models learned to program, they learned on the most semantically dense language ever written. COBOL describes what the business needs — not how the machine works. Every PERFORM, every MOVE, every COMPUTE is a business decision encoded as a statement. AI reads intent. COBOL writes it.

THE END OF THE INTERMEDIARY

The programmer was always temporary.

For sixty years, programmers lived between the business and the machine — translating intent into syntax. The business said what it needed. The programmer figured out how to say it in a language the machine understood. AI removes the translator. The business speaks. The machine listens. The code is the requirement.

FOUR REASONS COBOL WAS RIGHT
ENTER RECALL

RECALL is that idea for the web.

A declarative web interface language with COBOL-inspired syntax. You describe the page — its identity, its data, its structure — and the compiler produces a self-contained HTML file. No framework. No intermediary. The source is the business requirement. The output is the artifact.

NOTE

RECALL is not a nostalgia project. It is a design argument: that intent-first, verbose, declarative syntax is exactly what the AI-native web needs.

DESIGNED TO LAST

Legacy forward.

COBOL systems from the 1960s still run payroll because they encoded business truth so precisely that replacement means rediscovering that truth from scratch. RECALL asks the same question for the web: what does a page look like if it is designed to last, to be read, and to remember where it came from?

GET STARTED

Start in 30 seconds.

bash
npm install -g @semanticintent/recall
READ THE DOCS