How ion7 works

ion7 pairs a Pascal-native build agent with a deterministic publish pipeline.

The loop

1. You describe an app in the chat panel.
2. PasClaw writes Object Pascal source into a Horse project with HTMX views.
3. Free Pascal (Delphi mode) compiles. Green build ⇒ commit. Red build ⇒ agent iterates.
4. You click Publish. The static binary ships to a Cloudflare Worker-fronted container.

Runtimes

A RuntimeAdapter is a tiny interface: scaffoldPrompt, starterFiles(), compile(), publish(). Registering a new engine (Rust, Go, Lua) is one file. Today: FPC · Horse · HTMX (GA) and PHP · HTMX (beta).

Hosting

Cloudflare Worker + Container is the default. The Worker fronts each request; the container runs your compiled binary. Cold starts are measured in single-digit milliseconds because the artifact is a static executable, not a language VM.

Why not JS?

Because compiling is a first-class debugging signal. The agent gets a hard yes/no every iteration and repairs faster than any linter loop. HTMX gives you dynamic UI without a JS build step. Everything you ship is code you can read.