# Define the cheaper mode that preserves the core function

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Define the cheaper mode that preserves the core function

ID: MHC-D-RESEARCH-0540 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/define-the-cheaper-mode-that-preserves-the-core-function

Degraded and useful beats complete and unavailable.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Demand spikes or a dependency fails and the full service cannot be delivered reliably.

### Avoid when

- A complex rarely tested fallback can be less reliable than the main path; keep degradation simple and exercise it.

### Explanation

Identify the smallest core outcome users still need under stress, then define a simpler mode that costs less or uses fewer dependencies. Test that path before an incident. Make degradation visible so users know which features or freshness they lost.

### Steps

1. The degraded mode continues to deliver the central value with measurably lower resource or dependency demand.

### Example

During model-provider overload, return cached reference data and disable expensive enrichment instead of failing the entire workflow.

### Check

The degraded mode continues to deliver the central value with measurably lower resource or dependency demand.

### Limits

- A complex rarely tested fallback can be less reliable than the main path; keep degradation simple and exercise it.

### Evidence and sources

- supports: Google and AWS overload guidance recommend load shedding or graceful degradation to preserve core useful work when total demand exceeds available capacity. — RS-C1BEE49CF0075A87. Which work may be dropped or degraded is a product and safety decision, not only a technical one. (Load shedding and graceful degradation)
- RS-C1BEE49CF0075A87: Addressing Cascading Failures — https://sre.google/sre-book/addressing-cascading-failures/

### Vedokrok editorial review

Test the simpler service mode before relying on it

Choose what users must still be able to do when a dependency fails or capacity runs short. Then test a simpler way to deliver that outcome.

#### Define the useful minimum

Name the core outcome, the optional work to remove, the condition that activates the mode and the condition for leaving it. Explain any lost features or freshness to users. For example, an internal reference tool could serve an allowed cached edition while enrichment is unavailable, with the edition date visible. Whether stale information is acceptable depends on the task.

#### Keep the recovery path simple

In a controlled test, make the dependency unavailable and verify both the remaining user task and the resource or dependency demand. Also test the return to normal service. A mode that uses fewer calls but breaks required consistency is not an acceptable result. Avoid elaborate fallback chains that receive little testing; the alternate path needs maintenance too.

**Editorial takeaway:** Write one failure scenario and one pass condition for the core task. Exercise it before treating the degraded mode as a recovery option.

#### Editorial evidence

- supports: Google SRE describes graceful degradation as reducing work and calls for explicit activation metrics and behavior. — RS-C1BEE49CF0075A87. Selected official passages read on 2026-10-04. The specific cached-reference example and exit check are editorial applications, not measured outcomes. (Load Shedding and Graceful Degradation)
- supports: AWS recommends identifying core functionality and testing it during dependency failure. — RS-D75F0CCD717B89FC. Selected official passages read on 2026-10-04. This supplies the previously unlinked AWS basis; business requirements determine acceptable degradation. (Desired outcome; Common anti-patterns; Implementation guidance)
- limits: AWS warns about inconsistent partial transactions and calls for simpler, tested failure paths. — RS-D75F0CCD717B89FC. Selected official passages read on 2026-10-04. No general permission to sacrifice consistency or serve stale data is implied; circuit-state terminology on this page was not used. (Common anti-patterns; Implementation guidance on core requirements and failure paths)
- RS-C1BEE49CF0075A87: Addressing Cascading Failures — https://sre.google/sre-book/addressing-cascading-failures/
- RS-D75F0CCD717B89FC: REL05-BP01 Implement graceful degradation to transform applicable hard dependencies into soft dependencies — https://docs.aws.amazon.com/wellarchitected/latest/framework/rel_mitigate_interaction_failure_graceful_degradation.html

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
