Grama (halacha)¶

A Jewish-law category for an indirect causal contribution whose prohibited or harmful outcome is not guaranteed by the actor's immediate deed.

Version: v2 · 2026-09-19 · History
Domain-specific #: 4762
Domain group: Humanities
Origin domain: Religious Studies & Theology
Subdomain: Jewish Law → Religious Studies & Theology

Core Idea¶

Grama distinguishes mediated, contingent causation from direct action in Sabbath and damages analysis, while moral obligation, exceptions, and closely related stronger causation categories remain doctrine-specific.^[1] An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of jewish law. It is the domain-specific identity determined by the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

How would you explain it like I'm…

Setting It Up, Not Doing It

Jewish law has rules about what you may do on the day of rest and about causing damage. Sometimes you do something directly, like knocking over a tower yourself. Other times you only set things up, and something else that happens later is what knocks it over. Grama is the name for that second, indirect kind of causing, and the rules may treat it differently from doing it directly.

Indirect Causing Rule

In halacha (Jewish law), Grama means causing a result indirectly rather than directly. You change something, and later a separate event or an uncertain chain of events brings about the outcome. This matters when deciding whether an action is allowed on the Sabbath, or whether someone has to pay for damage. Teachers of the law look at how much time passes, whether the result was sure to happen, what the person intended, and which area of law applies. Grama doesn't automatically make something okay. The answer depends on the specific rules.

Indirect Causation in Halacha

Grama is a halakhic category for mediated, contingent causation, as opposed to direct action. It is used in Sabbath law and in the law of damages. An actor changes a condition, and the outcome only follows when that condition interacts with an independent event or an uncertain causal chain. To classify a case, authorities weigh temporal separation, how inevitable the outcome was, the actor's intention, emergency status, and which legal domain governs. Labeling something grama does not settle whether it is permitted or whether there is liability. Those results, the exceptions, and the boundaries with stronger indirect-causation categories differ by doctrine.

Grama in halacha designates indirect, mediated causation, distinguished from direct action. It matters in two main areas: whether a Sabbath act is permitted, and whether liability attaches in damages. Structurally, an actor's initial act alters a condition, and the outcome arises only through an intervening independent event or uncertain chain. Analysis must make explicit the governing halakhic domain, the initial act, the intervening mechanism, the probability and timing of the outcome, the intent, emergency status, and which direct-versus-indirect category is in play. Authorities weigh these factors before assigning permissibility or liability. Moral obligation, exceptions, and neighboring stronger forms of causation are handled differently in different doctrines. So the grama label alone does not determine a ruling. The broad topic of Jewish law, or a surface resemblance to indirect action, is not enough to identify a genuine case.

Structural Signature¶

Carrier: the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets
Inputs or antecedent state: the exact jewish law carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Grama (halacha)
Constitutive operation: An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability.
Invariant: the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit
Recognition test: type the carrier, state every parameter and convention in the definition, test that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
Failure boundary: the carrier is mistyped, the condition that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not¶

It is not the whole field of jewish law. The field contains many questions and methods that do not instantiate Grama (halacha).
It is not its most familiar example. A canonical instance directly demonstrates that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Garmi. Garmi is often treated as a more proximate or certain indirect-damage category with stronger liability; boundaries vary among authorities and cannot be collapsed into grama.
It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Grama (halacha) must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside jewish law, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Grama (halacha) belongs to jewish law and is useful where the analyst can specify the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. The scope is broad within that domain but bounded by the need for the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. Descriptive religious-law identity only; practical Sabbath, damages, healthcare, electrical-device, or security questions require a competent halakhic authority and applicable secular law.^[2]

Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
Construction or evolution. Track how the exact jewish law carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Grama (halacha) are converted, constrained, or organized by An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability..
Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Grama (halacha) must control the decision and state which convention or theorem controls the decision.
Downstream reasoning. Use the established identity to support recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Grama (halacha) can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact jewish law carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Grama (halacha), the structure counts as Grama (halacha) exactly when the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Grama (halacha). Grama (halacha) compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of Grama (halacha). Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit, infer recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Grama (halacha) must control the decision and an object that resembles Grama (halacha) in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of jewish law because they reuse the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability., and type the carrier, state every parameter and convention in the definition, test that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from A canonical instance directly demonstrates that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. to An applied instance preserves the same invariant under a changed scale, notation, jurisdiction, dataset, or implementation..^[3]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Grama (halacha), preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples¶

Canonical¶

A canonical instance directly demonstrates that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit. The example exposes the carrier and directly tests that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets; the operative rule is An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability.; the invariant is the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit; and the result supports recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.^[1] Changing incidental notation or scale leaves the structure intact, while removing the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit destroys the classification.

Mapped back: the typed jewish law carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets → An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability. → the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit → recognizing and comparing instances of Grama (halacha), deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

An applied instance preserves the same invariant under a changed scale, notation, jurisdiction, dataset, or implementation. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.^[2] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions¶

T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character¶

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of Grama (halacha), preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Grama (halacha), carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from jewish law and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent¶

The structural core consists of a carrier, An actor changes a condition that later interacts with an independent event or uncertain chain; authorities classify temporal separation, inevitability, intention, and domain before assigning permissibility or liability., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Grama (halacha), preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Grama (halacha), carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in jewish law.

This entry is a kind of Causality.

It remains its own entry because its identity is fixed by the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category.

Relationships to Other Abstractions¶

Current abstraction Grama (halacha) Domain-specific

Parents (1) — outgoing typed relations

Grama (halacha) is a kind of Causality Prime

It remains its own entry because its identity is fixed by the governing halakhic domain, initial act, intervening mechanism, probability and timing of outcome, intent, emergency status, and relevant direct-versus-indirect category.

Hierarchy path (1) — routes to 1 parentless root

Grama (halacha) → is a kind of Causality → is a kind of Dependency

Neighborhood in Abstraction Space¶

Grama (halacha) sits in a moderately populated region (46^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With¶

Garmi. Garmi is often treated as a more proximate or certain indirect-damage category with stronger liability; boundaries vary among authorities and cannot be collapsed into grama.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Grama (halacha). A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Grama (halacha). An extension qualifies only when its changed axioms and retained invariant are stated.

References¶

[1] Source cited in the frozen article, 'ט – גרמא – פניני הלכה', 9 March 2000.not authoritative registry ↩a ↩b

[2] Source cited in the frozen article, 'Shabbat 120b'.not authoritative registry ↩a ↩b

[3] Source cited in the frozen article, 'Gramma'. registry ↩