weft
ir 2.6.0 · warp 1.8.0
generatedextracted from the source that raises it

E_TTL_REQUIRED

A named refusal, raised in 3 places in kernel. What it refused, the sentence it prints, and the argument for it.

named refusal kernel packages/kernel/src/cache.ts·3 places
this fragment reads the clock, so a cache policy without a TTL would never expire

The message as the source writes it, with interpolations shown as an ellipsis. It is a reconstruction of the template, not a capture of a runtime string.

Specified in
spec/compiler/effects.md·spec/kernel/cache.md·spec/plan/plan.md
Introduced by
What a fragment reads decides everything·What a route declares

Raised in the same package, or specified in the same document. A refusal rarely stands on its own — the ones beside it are usually the same rule seen from another angle:

CodeWhat it saysRaised in
E_BAD_DURATION… is not a duration like '30s' or '250ms'plan
E_BAD_SIZE… is not a size like '40kb'plan
E_CACHE_POLICY_CONFLICT.cache('public') on a fragment the compiler classified private. The read that caused it: …plan
E_CONSISTENCY_MISMATCHdeclares strong consistency against '…', which is eventualplan
E_CTX_IN_MARKUPread ….…() into a value in the fragment body, so the compiler can record what it taintscompiler