RegDelta

What changed, does it apply to us, and what is the real deadline — with a citation on every claim.

FDA food-labeling corpus · SPEC/04 demo

configured tier: checking…

tier that answered

—

from the response, not /health

response cache

—

hit · miss · bypass · disabled

retrieval latency

—

server, router.retrieve — reported, not a claim

round trip

—

client stopwatch, incl. generation

Canned scenarios

loading…

One button per entry in evals/scenarios.json, fetched — not transcribed.

Question

company profile: none

bypass the response cache sends no_cache: true

Cross-tier comparison

Tier B is the same retrieval algorithm on different infrastructure — not hybrid, and not faster (ADR-0009 Ruling 3(a); ADR-0012). The latency numbers above are reported so a viewer can see them, not offered as a claim about either tier.