Cache assembled service for offline resilience #100

New issue

Open

opened 2026-07-01 01:04:17 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:04:17 +00:00

(Migrated from github.com)

Problem

Connectivity in chapels can be poor. Once loaded, a service should remain usable if the connection drops.

Acceptance criteria

An assembled service is cached client-side so it remains readable offline after first load
Cached content is scoped to the day/service and refreshed when data version changes
Offline state is indicated without blocking reading
Caching uses no tracking identifiers and respects privacy rules

## Problem Connectivity in chapels can be poor. Once loaded, a service should remain usable if the connection drops. ## Acceptance criteria - [ ] An assembled service is cached client-side so it remains readable offline after first load - [ ] Cached content is scoped to the day/service and refreshed when data version changes - [ ] Offline state is indicated without blocking reading - [ ] Caching uses no tracking identifiers and respects privacy rules

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Site#100

No description provided.

Rows
Columns