HTTP responses as declarative data

http-request resolves a URL in its declaration scope, performs an authorized GET or HEAD, and publishes a lifecycle resource envelope under datadom.slices.<slice>. Templates can render its lifecycle, request and response metadata, and a retained CEM document without receiving live Request or Response objects.

These examples use same-origin JSON fixtures. Browser hosts still enforce Fetch, CORS, credentials, content-type, response-size, and timeout policy; cross-origin requests require explicit host authorization.

See also

Pokémon images through a matched table-cell override

Retained document trees and branch selection

Rendering imported CEM nodes with for-each

Scoped URL and module-map resolution

HTTP request resource design