Maintenance

August 10, 2026 · View on GitHub

How this index is kept current, and the judgment calls already made so a later sweep does not re-litigate them.

Running a sweep

The index is built by sweeping public repos and filtering by material type. GitHub search is the practical tool; is:public matters because SCOPE.md forbids listing private repos in a public index.

user:danielrosehill is:public israel in:name,description
user:danielrosehill is:public shelters OR vocab OR numbering OR codes OR regulations in:name
user:danielrosehill is:public hebrew OR data OR reference OR ref in:name

The Israel filter on name and description alone misses repos whose Israel angle is in the README — jlm-shelters-data, Hebrew-Tech-Vocab, Miklat-MCP-Data and Pikud-Haoref-Guidelines-0326 all fail a naive israel name match. Run the second and third queries, or you will produce a sweep that looks complete and is not.

Confirm private: false on every candidate before listing it. A repo can be flipped to private after it was indexed.

The test, applied

The SCOPE test is is the repo's value the data or the documented rule itself? Two follow-ups settle most cases:

  1. Would you clone it to look something up, or point an agent at the raw file? If yes, it belongs here.
  2. Is there something to run? A helper script that regenerates or validates the data does not disqualify it. A server, bot, dashboard or app does.

Miklat-MCP-Data is the clean illustration of the split: the data pipeline is here, the MCP server that serves it is in Israeli AI.

Judgment calls on record

Decided during the 2026-08-04 sweep. Revisit if the reasoning stops holding, but do not re-argue them from scratch.

In:

  • Israel ADHD Medication Access — a first-person case record in form, which is not obviously reference material, but the payload is the regulatory position: Procedure 155's dispensing rules, the published travel route and its service standard, and תקנה 13(א)(8)(ב) collated with citations, Hebrew text and translation. Nothing else assembles those in one place, and the case is what makes the rules legible. Filed under Standards, Codes & Regulations. Do not drop it in a later sweep for being a narrative — check docs/what-the-rules-say.md first, which is the part that earns the listing.
  • Miklat MCP Data, JLM Shelters Data — datasets with pipelines that feed applications. The pipeline regenerates the data; the data is still the point.
  • Israel Red Alert Syntax Notes — not a dataset and not a feed, but field-level documentation of an undocumented feed. Filed under Feeds & Data Formats: it is the documented rule you need before the feed is usable.
  • Hebrew Tech Vocab — WIP and personal, but a controlled vocabulary, which SCOPE names explicitly. Also listed in Israeli AI's Hebrew page; overlap is fine.
  • Pikud HaOref Guidelines (03/26) — official guidance restructured for retrieval, stated by the repo itself to be ground truth for agents.

Out:

  • Israel First Aid — derived from MDA/Hatzalah procedures, which reads as translated official guidance, but the repo tags itself sops and procedures, and SCOPE excludes SOPs. Borderline; belongs to Israel Preparedness Index.
  • Retailer Recommendations — a directory in shape, but the content is subjective recommendation rather than reference data.
  • Iran-Israel-War-2026-OSINT-Data — genuinely a structured dataset, so it passes the literal test, but SCOPE excludes OSINT material and the repo's purpose is conflict research rather than grounding context. Left with the OSINT indexes. Reconsider if this index ever grows a research-corpus section.
  • Israel Spam Callers — no description and unclear content. Not excluded on the merits; excluded pending a look at what is actually in it.
  • Awesome Red Alerts, Awesome Israeli Jewish Home Assistant, Epic Fury Projects — index repos, not reference material. Indexes of indexes go in the master index.

Blocked by the privacy rule — these are reference material by any reading, and would be listed the moment they go public:

  • Israel Telephone Numbering — numbering plan, star codes and shadow numbers, line types, SMS capability.
  • Israel SIP Providers — Israeli SIP trunk / VoIP provider research.
  • Israel Procurement Morsels — conventions, units and vocabulary for buying things in Israel.

Renames keep links alive via GitHub redirects, so a stale link will not 404 and will not announce itself. Check the resolved URL, not the status code — a redirect means the entry's name is out of date even though the link works.

Shields.io badges are the more brittle half: they are keyed on owner/repo and break silently on a rename, showing "invalid" rather than failing. This index uses static "View Repository" badges rather than live star counts precisely to reduce that surface.

Freshness

Entries should say when they were compiled and from what. A stale snapshot that is clearly labelled is useful; an undated one is not. When adding an entry, copy the repo's own dating rather than inventing one — and if the repo carries no date, that is worth fixing in the repo before listing it here.