← Back to catalogue
Published

Hebrew calendar

vr.tr.hebrew-calendar · thing-q44722

Enable an AI agent to identify a Hebrew calendar regime, assess whether a date or calendar calculation is valid and sufficiently specified, and determine which conversions or scheduling actions are justified.

Thing Registry Information and virtual systems INF.KNW

Bundle → Layer → Finding → Questions Filled

5 bundles · 9 layers · 16 findings · 24 questions

Calendar Regime and Authority Identify which Hebrew calendar rules a representation or calculation claims to follow.

Fixed and Historical Reckoning

Separate the standard fixed calendar from historical or otherwise distinct methods of establishing dates.

Applicable Hebrew Calendar Regime

Record the intended regime and distinguish reconstruction of an attested date from retrospective application of fixed rules.

  1. Does this use the standard fixed rabbinic calendar, an identified observational practice, or another specified Hebrew calendar tradition? definition
  2. What evidence supports applying that regime to the community and period being represented? provenance

Rule Sources and Calculation Authority

Establish which sources and implementations support the calendar's operational rules.

Traceable Calendar Rules

Associate leap-year, molad, postponement, and month-length rules with identifiable sources and implementation conventions.

  1. Which source specifies the leap-year cycle, molad arithmetic, and postponement rules used here? provenance
  2. When a calendar table and an implementation disagree, what evidence or designated authority determines which result the agent may use? action
Hebrew Year and Month Structure Represent the interdependent rules that determine year identity, intercalation, month order, and valid dates.

Year Numbering and Intercalation

Resolve year expressions and establish the applicable leap-year status.

Resolved Year and Cycle Position

Record the era, full year number, Tishrei transition, and cycle convention needed to determine intercalation.

  1. What full year and era does the expression denote, particularly when thousands are omitted? definition
  2. Under the selected fixed-calendar convention, what is the year's position in the 19-year cycle and is it common or leap? measurement

Month Identity and Year Shape

Resolve month names and derive the valid sequence and lengths for a particular year.

Valid Month and Day Combination

Distinguish Nisan-based numbering from Tishrei-based ordering, resolve Adar identity, and check dates against year-specific month lengths.

  1. Which named month does the supplied label or number identify, and does an unqualified Adar require clarification in this year? definition
  2. Do the calculated year length and Cheshvan and Kislev lengths permit this month-and-day combination? measurement
Day Boundaries and Date Conversion Control how Hebrew dates relate to local evenings, civil dates, and precise instants.

Local Evening Boundary

Capture the geographic and interpretive context required near the transition between Hebrew dates.

Resolved or Ambiguous Day Assignment

Record location and boundary conventions, including whether twilight leaves a date assignment unresolved for the intended use.

  1. Which location, time zone, and solar-boundary calculation apply to this instant? measurement
  2. Does the instant fall in a twilight interval or exceptional geographic situation for which the intended use requires a specified convention? boundary

Conversion Semantics

Distinguish conversion of date labels from conversion of timed events and historical date assertions.

Explicit Conversion Contract

Record the input's precision, the other calendar's identity, and whether the result denotes a conventional date correspondence or an interval of instants.

  1. Is the input a Hebrew date label, a local civil date, or a timestamp, and is the other calendar Gregorian, Julian, or explicitly something else? definition
  2. May the agent return one corresponding date, or must it return an interval or alternatives because time, location, or historical convention is missing? action
Hebrew-Date Scheduling and Observance Interfaces Support recurring dates and calendar-derived observance schedules while identifying conventions that require external authority.

Adar and Missing-Day Recurrence

Make recurrence policies explicit when the target year differs structurally from the original year.

Authorized Hebrew Anniversary Policy

Record the purpose and governing policy for moving an anniversary between common and leap years or into a month lacking the original day.

  1. For this recurrence's purpose, which Adar is used when moving between common and leap years, and who or what supplies that policy? provenance
  2. If the original day does not exist in the target month, should the agent apply a specified adjustment, omit the occurrence, or leave it unresolved? action

Observance Date Conventions

Separate nominal Hebrew dates from scheduled observance dates and from religious instructions about those observances.

Calendar-Derived Observance Schedule

Associate observance-date calculations with the applicable community, Israel or diaspora convention, and any sourced date-adjustment rule.

  1. Which community and Israel or diaspora convention govern the requested observance schedule? definition
  2. Is the requested result a nominal calendar date or an adjusted observance date, and which sourced rule permits any adjustment? boundary
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.

Reported evidence

Findings from the breadth pass, kept separate from the structural claims.

Kinds and varieties

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these kinds and varieties hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Identifiers and schemes

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these identifiers and schemes hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Standards and regulation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these standards and regulation hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Real-world use

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these real-world use hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Typical measurements

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these typical measurements hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Failure modes and hazards

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these failure modes and hazards hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Regional variation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these regional variation hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these neighbouring kinds and how to tell them apart hold for the sense of Hebrew calendar this model covers, and on what evidence? provenance

Classifiers Filled

Family
Thing Registry
Category
Information and virtual systems
Entry kind
thing
Plane
INF
Domain
INF.KNW
Other names and narrower kinds
Rosh Chodesh

What it is Filled

The Hebrew calendar is the lunisolar calendar of rabbinic Judaism: months follow a conventional mean lunar conjunction (the molad), years are kept near the solar seasons by inserting a second Adar in seven years of a nineteen-year cycle, and 1 Tishrei is further constrained by weekday postponement rules (deḥiyyot), with years numbered from a conventional era of creation (Anno Mundi).

In scope

  • Identification of the calendar tradition, governing rules, and historical applicability
  • Year numbering, leap-year status, month sequence, and variable year lengths
  • Hebrew date expressions, month-name aliases, and date validity
  • Day boundaries and the location and time assumptions required to assign a date
  • Conversion to other calendars and scheduling of Hebrew-date recurrences
  • Calendar-derived observance dates and dependencies on community conventions

Out of scope

  • Religious obligations, permissions, and authoritative rulings about observance
  • Liturgical texts and synagogue service procedures
  • General astronomy, solar-position calculation, and lunar ephemerides
  • Civil time-zone administration and the internal rules of other calendars
  • Personal life events and historical events dated using the calendar

Why it exists Filled

Enable an AI agent to identify a Hebrew calendar regime, assess whether a date or calendar calculation is valid and sufficiently specified, and determine which conversions or scheduling actions are justified.

Distinguishing features Filled

  • Test whether the rules coordinate lunar months with the solar year through intercalation; a purely lunar calendar without this adjustment is a different system.
  • For the standard fixed Hebrew calendar, test whether leap years follow the specified seven positions in a 19-year cycle and introduce an additional Adar month.
  • Test whether the system distinguishes the Tishrei year-number transition from month numbering that begins with Nisan.
  • Test whether date assignment accounts for the Hebrew day's evening boundary rather than assuming a midnight rollover.
  • Test whether fixed-calendar calculations account for postponement rules and variable Cheshvan and Kislev lengths; alternating month lengths alone do not identify a valid Hebrew year.

What robots and AI may and may not do Filled

Must not

  • Give a festival or fast date from an unchecked calculation for religious observance.
  • Ignore differences between Israel and the diaspora for festival days.
  • Schedule events in ways that exclude observant people without saying so.
  • Present rabbinic calendar rules inaccurately.

Only with a human decision

  • Fixing dates for communal religious observance.

May

  • Convert dates between the Hebrew and civil calendars using the published rules.
  • Show festival and Sabbath dates with the location and conventions used.

Moral aspects Filled

  • The calendar orders religious life; mistakes can lead people to break observance.
  • Respecting it in scheduling is part of including Jewish people.

Who is affected

  • Jewish communities
  • Scheduling users

Owners Filled

Steward

Rabbinic tradition holds its rules; communities and their rabbis decide local practice.

Links to other meta-models Filled

parent

  • Q194235 - registry parent class

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.hebrew-calendar
  • Wikidata: Q44722 (https://www.wikidata.org/wiki/Q44722)

Direct properties not applicable Not applicable

  • Calendar regime: Standard fixed rabbinic calendar; historically attested observational regime; other explicitly identified tradition; unresolved
  • Rule authority and applicability: Relationship to an identified rule source, community or authority, and period of applicability
  • Hebrew year and era: Integer year with an explicit era and policy for omitted thousands
  • Metonic cycle position: Position 1-19 under an explicitly stated fixed-calendar indexing convention
  • Year structure: Common or leap; deficient, regular, or complete; unresolved
  • Month identity: Named Hebrew month, distinguishing Adar in a common year from Adar I and Adar II in a leap year
  • Day-boundary context: Relationship to location, time zone, solar-boundary method, and treatment of twilight
  • Date resolution state: Valid and resolved; invalid; incomplete; convention-dependent; boundary-ambiguous

Plane INF: no invented physical properties.

Recognition not applicable Not applicable

Not applicable

The calendar is an abstract system of date rules and has no intrinsic visual appearance.

Capabilities and actions required Filled

  • Validate a Hebrew date against its identified calendar regime and year structure.
  • Normalize Hebrew-script and transliterated date expressions while retaining unresolved ambiguity.
  • Convert dates or instants with explicit calendar, location, and day-boundary assumptions.
  • Compute month sequences and calendar-derived dates using an identified rule set.
  • Schedule Hebrew-date recurrences using an explicit Adar and missing-day policy.
  • Compare competing date assignments and explain which assumptions cause the difference.

Hazards and failure modes required Filled

  • Ignoring the sunset boundary or location can assign an event to the wrong Hebrew date.
  • Mishandling leap months or postponement rules can produce incorrect conversions and recurring anniversaries.
  • Assuming identical holiday schedules in Israel and the diaspora can cause missed observances or scheduling conflicts.

Standards and interfaces not applicable Not applicable

Not applicable

No single technical standard, law or official classification universally governs the Hebrew calendar in this general sense.

Context of use required Filled

  • The Hebrew calendar is used to determine Jewish holidays, religious observances and commemorative dates.
  • It appears in religious communities, historical records and scheduling systems that display or convert Hebrew dates.
  • Scheduling observances requires attention to the local sunset boundary and differences between observance in Israel and the diaspora.

Sources Filled

  1. Hebrew calendar - Wikipedia (Wikimedia Foundation) - Structure of the lunisolar year, month names, 19-year intercalary cycle, postponement rules, Anno Mundi epoch, and the distinction between calculated and observational practice.
  2. Calendrical Calculations - Nachum Dershowitz and Edward M. Reingold, Cambridge University Press - Canonical computational statement of molad arithmetic, year-length classes, conversion to and from the Gregorian calendar, and the mean lunation of 29 days 12 hours 793 chalakim.
  3. Mishneh Torah, Hilchot Kiddush HaChodesh - Moses Maimonides (standard printed and Sefaria texts) - Classical rabbinic formulation of sanctification of the month, intercalation, and the calculated calendar's mean-motion parameters.
  4. Unicode Technical Standard #35 (LDML) - Unicode Consortium - Machine identifier hebrew / BCP 47 u-ca-hebrew used in locale data, ICU, and software calendars.
  5. Wikidata item Q44722: Hebrew calendar - identity and sense of the item

Open questions

  • Does the registry intend this entry to own only the standard fixed rabbinic calendar or also historical and other Hebrew calendar regimes?
  • Which authoritative sources and independent reference calculations should establish the supported fixed-calendar rules and conversion range?
  • For which historical periods can date assignments be supported as attested practice, and where must results be labeled retrospective or uncertain?
  • Which conventions should govern twilight, high-latitude conditions, and geographic date-boundary disputes for the intended applications?
  • Which recurrence and observance-date policies may this model apply directly, and which require a linked community or religious-authority model?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q44722/spec.json