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. 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.

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.

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.

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.

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.

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.

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.

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