weft
ir 2.6.0 · warp 1.8.0
Part four · Step 19 of 19

Every surface, and what may change

The same declarations answering a watch, a terminal and a feed reader — and the rules for changing any of it without breaking a client.

Goal

Serve the shop to something that is not a browser, then read what this framework promises about the formats you have been relying on.

A region is a rendered fragment addressed by name. Nothing in that sentence says HTML, and nothing in your route said it either — the form was negotiated per request all along.

1 · Ask for another surface

$ curl -H "Accept: application/json" localhost:4173/            # the value set$ curl -H "Accept: text/plain" localhost:4173/                  # for a terminal$ curl -H "Accept: application/warp" localhost:4173/            # frames, for a client

Same route, same fragments, same plan. A surface that cannot take one of the forms is served the one it can, which is the negotiation this framework is named for.

2 · What may change under you

Carries a versionWhat that buys
The template IRA client holding an old template is sent markup rather than a delta it cannot apply.
The warp framesA frame a client does not understand is skipped, not guessed at.
Every sealed templateA content address, so "the same template" is a fact rather than a claim.

Those are the three numbers in the pill at the top of this page, and they are stamped by the build rather than typed. Every surface at once and versions, and what may change are where this stops being a tutorial and starts being a contract.