Skip to content

RFC 0000: Title

  • Issue: #
  • Author: @
  • Status: Draft

Summary

One paragraph: what changes, for whom.

Why

The problem, with a real site that needs this. What people do today instead, and why that isn't good enough.

Design

In site.yaml

# docs: no-validate
# the spec a user writes, before and after

What the page does

What a visitor sees and feels, on desktop and on a phone, and with reduced motion.

In the engine

Spec models, builder stages and their cache keys, runtime changes, CLI and MCP changes, models (local first; provider backends optional).

Compatibility

What happens to every existing spec, built site, command and tool. If anything changes, the deprecation plan (docs/compatibility.md) and the migration note.

Testing

How it is tested without a GPU (stand-ins, snapshots, contracts, browser tests), and what needs a GPU check.

Alternatives

Other designs considered, and why this one.

Open questions

What is not decided yet.