1 Daily journal usage totals

Backend deployed and verified on 12 October 2026 with user approval.

refreshJournalMetrics runs daily at 06:17 Asia/Kolkata. It loads the validated published article registry and sums the top-level articleMetrics documents. It does not read visitor or deduplication records. Only published article IDs are included, including future articles added through the rendered registry. No summary is overwritten if registry retrieval, metric validation, or the database read fails.

journalMetrics exposes only the stored summary through GET. It reads one summary document, caches it in each function instance for five minutes, and sets a five-minute public cache header. Homepage visitors do not trigger aggregation or write to Firestore. The homepage marks summaries over 48 hours old as delayed, and reports unavailable data without displaying false zeros.

These are recorded article views, engaged reads (at least 30 seconds after a recorded view), and PDF download clicks, not unique readers or confirmed file transfers. Historical activity before tracking began is unavailable.

For future approved deployments, deploy only refreshJournalMetrics and journalMetrics, run the generated Cloud Scheduler job if an initial summary is needed, verify its public endpoint, and publish the rendered homepage. Deployment creates a Cloud Scheduler job; its allowance and any charges are shared with the billing account. Firestore, function compute, network, and build usage remain subject to Firebase pricing.

This daily usage summary is independent of citation counts. The weekly citation automation is not implemented by this change.