# Define the system boundary before optimizing

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

---

## Define the system boundary before optimizing

ID: MHC-D-RESEARCH-9119 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/define-the-system-boundary-before-optimizing

Optimization starts by deciding what is inside the model.

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

### Use when

- When a local process looks inefficient but upstream causes and downstream consequences are unclear.

### Avoid when

- A causal map is a hypothesis, not proof. Keep evidence, time scale, boundary choices and alternative explanations visible before acting on a loop.

### Explanation

Name the outcome, time horizon, actors, stocks, flows and dependencies included in the analysis, plus important factors deliberately left outside. Revisit the boundary if the proposed fix pushes cost beyond it.

### Steps

1. State the outcome and time horizon.
2. List included actors, resources and dependencies.
3. List major exclusions.
4. Ask where cost or risk could be displaced.

### Example

A support team wants faster ticket closure; widening the boundary reveals that premature closure moves rework into customer escalations.

### Check

The boundary is explicit and the proposed improvement cannot succeed merely by exporting the problem.

### Limits

- A causal map is a hypothesis, not proof. Keep evidence, time scale, boundary choices and alternative explanations visible before acting on a loop.

### Evidence and sources

- supports: System dynamics work emphasizes that well-intended interventions can be defeated by feedback-driven system responses, a pattern described as policy resistance. — RS-592B2C21A3CDE468. A qualitative feedback story is not enough; links, delays and predicted behavior still need empirical or operational checking. (Abstract)
- RS-592B2C21A3CDE468: System Dynamics Modeling: Tools for Learning in a Complex World — https://cmr.berkeley.edu/2001/08/43-4-system-dynamics-modeling-tools-for-learning-in-a-complex-world/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/separate-stock-from-flow
