Delivery
Digest
Setting it up
The Digest tab in the dashboard → channel and cadence. Three channels:
| Channel | Target |
|---|---|
| An address | |
| Slack | An incoming webhook URL (https:// required) |
| Webhook | Your own endpoint — the raw digest JSON is POSTed |
Delivery rules
- Never sent twice. One ledger entry per period. Receiving the same weekly summary twice is worse than not receiving it.
- A failed send is never lost. Network errors are not written to the ledger, so the next tick retries. Writing them would let one blip erase that week permanently.
- Empty periods stay silent. No "0 visitors" notification for a week with no traffic.
- Periods come from the calendar. The weekly period starts Monday 00:00 UTC — a late restart never drifts the send time.
Where the numbers come from
The digest first runs deterministic queries and builds an evidence bundle. If an LLM is enabled, it only rephrases that bundle; producing new numbers is forbidden. On the way out every number is matched against the evidence set, and any sentence that fails is dropped before publishing. If something was dropped, the digest is marked incomplete and tells you.
With no LLM configured the digest is still produced — just less fluently.