Managed serving on Cloudflare

Managed serving means your conformance files — /llms.txt, /llms-full.txt, /.well-known/security.txt — are served through Sichta and refreshed automatically when they are regenerated. You deploy one small worker, once.

Setup

1. In the app, open your site → Channel and choose Managed. The app generates a cloudflare-worker.js for your site — the exact code, readable before you run it.
2. In the Cloudflare dashboard: Workers & Pages → Create Worker, paste the file, deploy.
3. Add a route for your zone: your-site.com/llms.txt, your-site.com/llms-full.txt and your-site.com/.well-known/security.txt → the worker.
4. Back in the app, press Verify. The checks run against your live site within five minutes; you get the result by email.

What the worker does

• Requests for the three managed paths are answered from Sichta, cached at Cloudflare's edge for an hour.
• Every other request passes through to your origin untouched.
• If Sichta is unreachable, the last good copy is served from cache. If there is no cached copy either, the request falls through to your origin. The worker never turns a working site into a broken one.

After a regeneration

Nothing to do. New files are picked up as the edge cache expires — within an hour, without a deploy.