--- title: "Dependent Origination" description: "Reads phenomena as arising through conditions rather than from isolated causes or self-contained things." aiSummary: "Dependent Origination is Reality tool inside Reading What's Operating. It adapts a narrow Buddhist conditionality lens with strict source-lineage caution: phenomena arise depending on causes and conditions, not as isolated self-contained things. Mechanism: specific conditionality, multiple causes and conditions, trigger versus condition-field, upstream and downstream conditions, non-isolated phenomena, and the danger of turning interdependence into vague everything-is-connected language. Practice: name the phenomenon, identify supporting conditions, distinguish trigger from condition-field, test removal or alteration of conditions, trace downstream effects, and preserve agency without pretending independence. Lineage: Buddhist pratityasamutpada / paticca-samuppada, early Buddhist dependent arising, the twelve links in specific doctrinal contexts, Madhyamaka and Mahayana interdependence readings, Theravada conditionality analysis, and modern interpreters who warn against reducing the doctrine to generic systems thinking. Cross-references: Feedback Loops, Emergence, Action Situation Mapping, Tragedy of the Commons, Evolutionary Mismatch, and Foundation tools that prevent vague causal storytelling." discipline: reality category: reading-whats-operating disposition: living status: working-draft-v0-1 --- Descriptive *Reality ยท Reading What's Operating*
01 // Mechanism
## Mechanism Dependent Origination reads a thing by asking what conditions are making it arise. The ordinary habit is to isolate the object. This person is angry. This institution is corrupt. This movement is irrational. This policy failed. This model behaved badly. The sentence names something visible, and sometimes the visible thing is where the work begins. But the danger is treating the visible thing as self-contained. The anger has conditions. The corruption has conditions. The irrationality has conditions. The failure has conditions. The behavior has conditions. Dependent Origination reads the condition-field that lets a phenomenon appear. This does not mean everything causes everything. That sentence sounds wise until you try to use it. The useful reading is much more disciplined: this arises with these conditions; when these conditions change, the arising changes. A phenomenon is not independent, but neither is it an undifferentiated cloud of cosmic connection. It has traceable supports, triggers, constraints, dependencies, and downstream effects.
Dependent Origination: phenomenon and condition-field The visible thing is supported by conditions. Phenomenon what appears condition condition condition condition downstream effects Change the conditions, and the arising changes.
Inside Reading What's Operating, the tool is a conditionality lens. It asks you to stop explaining a system through a single cause when the phenomenon is being maintained by a field of conditions. A person lies because of fear, incentive, habit, prior punishment, lack of repair path, and a culture where truth is costly. An institution drifts toward Control because authority, metrics, fear, bad feedback, and status protection reinforce one another. An AI model's behavior arises through training data, architecture, system instructions, RLHF pressure, tool affordances, evaluation incentives, and user interaction. None of these alone is the whole cause. Together they make the phenomenon possible. Control misreads Dependent Origination by making the condition-field so total that agency disappears. If everything is conditioned, no one is responsible, no choice matters, and every action can be explained away. Decay misreads it by turning interdependence into vague softness: everything is connected, therefore analysis dissolves into atmosphere. The Range reading keeps conditionality sharp. Conditions shape action; they do not erase accountability. Interdependence expands the map; it does not excuse imprecision.
02 // Practice
## Practice The diagnostic question is: **"What conditions are making this arise?"** Use this when a phenomenon is being explained too narrowly by one cause, one person, one decision, one identity, one event, or one visible output.
**Name the phenomenon.** What is appearing: anger, silence, corruption, trust, defection, groupthink, innovation, collapse, safety behavior, institutional courage, or avoidance? **Separate trigger from condition-field.** The trigger may be real, but it rarely stands alone. Ask what made the trigger potent: prior history, incentives, fear, language, attention, fatigue, scarcity, norms, identity, or information. **Trace supporting conditions.** What has to be present for the phenomenon to keep arising? What resources, stories, rewards, permissions, absences, relationships, or feedback loops support it? **Test condition removal.** If this condition changed, would the phenomenon weaken, intensify, move elsewhere, or remain unchanged? This keeps the map from becoming vague. **Trace downstream effects.** What does the phenomenon make possible next? Conditions produce the thing, and the thing becomes a condition for something else.
The discipline is to keep the reading concrete. Dependent Origination should make the map more precise, not more mystical. If you cannot say which condition matters and how, you do not yet have the tool. You have a mood.
03 // In the Wild
## In the Wild A worker stops raising concerns. The lazy explanation is personality: they are disengaged. A conditionality reading asks what made silence arise. Past objections went nowhere. A manager praised candor but rewarded compliance. Meetings left no time for dissent. Risk was recorded against the speaker, not the decision. The silence is still the worker's behavior, but it is not self-contained. It is being produced. An institution becomes obsessed with metrics. The visible cause is leadership's dashboard. The condition-field includes investor pressure, weak qualitative feedback, audit culture, promotion incentives, legal defensibility, and the desire for clean comparability across messy situations. Remove the dashboard alone and another proxy may take its place. Change the condition-field and the behavior can change. An AI system gives a polished but empty answer. The visible output is one paragraph. The conditions include training data, reward pressure toward helpfulness, user prompt framing, system-level incentives, uncertainty handling, evaluation norms, and interface design. If you only blame the answer, you miss what produced it. If you only blame the conditions, you excuse the need to change the system. The useful reading holds both.
04 // Closing
When something appears, do not rush to isolate it. Ask what is feeding it, what it feeds in turn, and what would change if the conditions changed. That is where the reading starts to become useful.
**Why this tool is in the Inheritance.** Dependent Origination belongs here because Reading What's Operating needs a disciplined way to read condition-fields without collapsing into one-cause blame. It asks what supports a phenomenon, what triggered it, which conditions maintain it, and what changes when those conditions move. Triangulating Across Disciplines handles how multiple lenses can be held together. Checking Your Map Against Reality tests whether a causal story has warrant. This tool stays narrower: translate one Buddhist conditionality question into system diagnosis without turning it into general metaphysics or "everything is connected" haze.
ROOTS
Lineage
## Lineage The Codex did not invent Dependent Origination. It inherits the tool from Buddhist philosophy and practice, where it is far more than a general systems concept. The Sanskrit term is often rendered as pratityasamutpada; the Pali as paticca-samuppada. Common English translations include dependent origination, dependent arising, conditioned arising, and interdependent co-arising. In a general sense, the teaching says that phenomena arise in dependence upon causes and conditions rather than existing as independent, self-contained entities. In a more specific doctrinal sense, especially in early Buddhist and Theravada contexts, it refers to the twelve links that explain the arising of suffering and rebirth. Mahayana and Madhyamaka traditions carry the teaching into arguments about emptiness and the absence of independent essence. Theravada analytical traditions carry detailed conditionality analysis through Abhidhamma and commentarial work. Modern Buddhist teachers often warn against reducing dependent origination to a vague "everything is connected" slogan. That warning matters here. The Codex's translation is narrow: a Reality tool for reading condition-fields. It does not claim to reproduce the Buddhist doctrine, replace practice, or settle disputes among Buddhist traditions. It borrows one disciplined question: what conditions make this arise? The tool has limits and source risks. It can be flattened into generic systems thinking, stripped of its liberation context, or used as decorative non-Western authority. It can also become too broad to guide action. This page publishes under a strict translation rule: keep the source visible, preserve the doctrinal boundary, and use the tool only as a concrete conditionality question inside Reading What's Operating.
05 // Cross-references
## Cross-references **Within the category.** [Feedback Loops](/inheritance/reading-whats-operating/feedback-loops) reads recursive causality once outputs return as inputs. [Emergence](/inheritance/reading-whats-operating/emergence) reads system-level properties that arise from interaction. [Action Situation Mapping](/inheritance/reading-whats-operating/action-situation-mapping) gives institutional conditionality a concrete map. **Across the Inheritance.** Foundation tools keep the conditionality reading honest. [Confirmation Bias](/inheritance/watching-your-own-reasoning/confirmation-bias) catches the tendency to select conditions that support the preferred story. [Base Rate Neglect](/inheritance/watching-your-own-reasoning/base-rate-neglect) keeps the condition-field answerable to broader evidence. **Limitation.** Dependent Origination does not mean responsibility disappears into conditions. It means responsibility has to be read inside the conditions that make action more or less likely.