They are exports from page.js, layout.js or route.js, read at build time, and they only exist in the default model.
dynamic decides static versus dynamic for the whole route:
'auto'(default): decided by what the render reads.'force-static': prerender anyway;cookies()andheaders()return empty values (the docs adduseSearchParams(), not run here).'force-dynamic': render every request; fetches without their owncacheoption aren't cached.'error': prerender, and fail the build if anything reads the request.
revalidate sets the route's lifetime in seconds: false (default) keeps a static route until redeploy or on-demand revalidation, a number makes it ISR, 0 makes it dynamic. Fetches without options inherit it; per the docs, a fetch's own lower next.revalidate lowers the whole route's interval (not run here). Per the docs, the value must be a literal (600, not 60 * 10).
fetchCache sets the default cache option for fetches in that segment. 'default-cache' caches option-less fetches even after a request-time read; 'default-no-store' stops caching them even before one; 'only-cache'/'only-no-store' fail on the opposite choice; 'force-cache'/'force-no-store' are documented to override it.
In 16.4.5 the explicit option wins more often than the docs say. Under force-dynamic, and under fetchCache = 'force-no-store', a fetch with cache: 'force-cache' stayed cached (fd=1 over five requests). The source sets revalidate: false for force-cache before it checks the segment's opt-out.
With cacheComponents: true, the build rejects each of them: Route segment config "revalidate" is not compatible with nextConfig.cacheComponents. Please remove it. 16.4.5 printed the same for dynamic, fetchCache, dynamicParams and runtime; maxDuration built. use cache, cacheLife and instant replace them.