Repository navigation
id: design: offline & degraded operation for providers (from #5686) #5904
Description
Summary
Follow-on design ticket from #5686 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Buffering, backfill, cached grants, and per-class actuation rules when providers go offline or degrade.
Context from the parent
The parent design fixes the single capability-provider model — declaration, discovery, negotiation, least-privilege grants — instantiated by ESP32/MQTT, terminal, Bevy, smartphone, and web providers. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5686. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1587
dezren39 commentedon Nov 5, 2026
Field survey filed: #5931 (capability-provider research widening, per Drew's 2026-11-04 ruling) covers the current option space relevant to this issue in §6.3/§6.4 — the offline constraint that separates the field: live connection-scoped references (CapTP) vs persistent signed artefacts (UCAN/Biscuit, writer-set objects). It is an inventory, not a decision — the section ends with the open questions this design needs to answer.
dezren39 commentedon Nov 5, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 5, 2026
🤖 Agent note · triage complete
Triage of issue #5904 at current main (verified 2026-11-05):
04f78696abfbdf6567f58e623d80520436f002fa; a targeted search found no offline/degraded provider implementation or issue-specific decision. This is valid design work, not a reproducible code defect.Issue stays OPEN as the design work item; no code PR or separate follow-up task is needed for this triage.