GracefulDegradation

Serving a reduced experience instead of failing entirely when a dependency is down.

Why we need this / what value this brings

A dependency being down shouldn't mean the whole app breaks if that dependency isn't actually essential to every feature.

When to use this

Any feature built on an optional/non-critical dependency (e.g. the AI chat, a recommendation widget).

How to use or implement this

Explicitly decide and implement a fallback (hide the feature, show a cached/default result) rather than letting the failure propagate to an unrelated part of the UI.

Research questions

• If the AI chat provider is down, does the rest of the app degrade gracefully or does it break something unrelated?

---

Empty folder — drop notes, links, and findings here as you research.