02 / The developer’s desk.

A readable contract.
A place to build.

Build with standard HTTP, readable paths, and documentation that gets to the point. Keep your workflow portable. Keep the details in view.

Graphite protocol cards joined by a cobalt paper path over a drafting sheet. — Study 004 / Request. Policy. Response.

Examples, not live endpointsThe proposed API is in development. Reserved example domains, tokens, responses, and headers below are illustrative. No requests are made automatically.

A predictable asset path

curl https://assets.example/releases/site-v1/styles.css

A useful object shape

{
  "key": "site-v1/card.8ac420.webp",
  "contentType": "image/webp",
  "deliveryPath": "/releases/site-v1/card.8ac420.webp"
}

HTTP, without surprises.

For a versioned file, the cache policy is part of the interface. Use content fingerprints for immutable resources; revalidate documents that can change.

HTTP/2 200
Content-Type: image/webp
Cache-Control: public, max-age=31536000, immutable
ETag: "content-fingerprint"
Vary: Accept-Encoding

Try a real reference file.

This installation includes a small static JSON fixture. It is public, requires no authentication, and is available independently of any application backend.

Open the reference manifest →

Go deeper in the documentation.

Understand release paths, cache semantics, planned image workflows, and the proposed API surface.

Browse the documentation →