htxlang

A template language and resolution model for hypermedia-native web applications.

HTML in, pure HTML out. The bilateral boundary. Progressive layers. No client-side framework required.

Bilateral Boundary

The htx: namespace is server territory. HTML is client territory. Resolution strips the server affordances, producing pure HTML. The boundary is absolute.

Read the specification →

Progressive Layers

Code-on-demand is not binary. Layer 0 is pure HTML. Layer 6 is native-speed computation. Each layer is independently adoptable.

Understand the architecture →

The Resolver Model

Input: HTML. Output: HTML. Same medium. The engine adds capability without changing the medium. No framework tax.

Implementation guide →

Seven Engine Derivations

All derived from the same ~2,200-word prose seed. Different languages. Same constraints. Same induced properties. This is the derivation inversion — the seed determines the harvest.

TypeScript

1,555 lines · Reference

Bun runtime. Powers jaredfoy.com. Most complete derivation.

2,387 lines · Functional

Native HTTP server. Full pipeline with middleware.

⚡

Zig

2,516 lines · Functional

Comptime-optimized. HTTP server, CLI, conformance tests.

Elixir

26,764 lines · Functional

Phoenix-based. Comprehensive module system.

Rust

54,155 lines · In Progress

Most ambitious derivation. Ownership-driven safety.

4,209 lines · Proof of Concept

Minimal. Compiles on Raspberry Pi 5. Zero dependencies.

Python

1,631 lines · Functional

Simplest derivation. Readable reference.

Build Your Own Engine

Feed the PRESTO Seed to any frontier language model. Specify your target language. The model derives a conformant implementation. Validated across seven languages.

Get the Seed View All Engines Read the Spec