Lidarc
DE Sign in Request access code
Product Live demo Developers Templates Blog Sign in Request access code
←Logbook
Agents··1 min read

Why we don't generate code

Prompt-to-code is fast. But a website lives for years. Why Lidarc agents work with building blocks instead of code.

Author
Daniel
Version
Lidarc v0.4 · Pilot
Share
LinkRSS
Changes over time ModelGenerated code
Fig. 1 · Effort per change, schematicYear 1 → 5

AI can write a website in minutes today. That’s impressive, and often exactly right for a prototype. But a website isn’t a prototype. It lives for years, gets changed, extended, handed over.

The model first

In Lidarc a site grows from a model: pages consist of blocks, blocks have fields, a theme decides how everything looks. The agent fills this model; it doesn’t write code. People see the same model in the admin and the page builder.

That has three consequences:

  • Everything stays editable. What the agent built, you change with your mouse. No prompt, no developer.
  • Mistakes are caught early. Every block is checked against the theme’s schema. A missing required field becomes an error message, not a broken page.
  • Design keeps its quality. The agent picks from curated themes, sections and looks instead of inventing colors and spacing.

And why the Internet Computer?

Because “yours” should be more than a promise. Every Lidarc site is its own canister: no server, no shared data pool, every code swap publicly visible. And if you’d rather host classically, you take the same site with you.

Lidarc is in its pilot phase. If you want to build with us: request access.

Agents · Blocks · Internet ComputerLast changed