Scope

What belongs here

Repositories whose primary content is Israel-related reference material — something you consult to get an answer, rather than software you run.

Include a repo if it is mainly:

• A standard, code list or taxonomy — tax authority classification codes, official code sets, controlled vocabularies
• A regulation written up as reference — spectrum rules, legal or compliance requirements, what is permitted and what is not
• A dataset or directory — station IDs, retailer indexes, catalogue translations, geographic or institutional listings
• A source list — RSS/OPML collections, feed inventories, lists of authoritative publishers
• A translation of official guidance — Home Front Command instructions, ministry publications rendered into usable English

The defining test: is the repo's value the data or the documented rule itself? If someone would clone it to look something up, or point an agent at the raw file, it belongs here.

Small helper scripts that regenerate or validate the data (a build.py that re-emits the JSON) do not disqualify a repo — the data is still the point.

Most of these repos were built to ground an agent — because the Israeli source was Hebrew-only, or a PDF, or an undocumented feed. That intent is the common thread, but it is not the admission test: a reference repo written purely for human lookup belongs here too. See docs/maintenance.md for the judgment calls already made.

What does NOT belong here

• Applications built on Israeli data — dashboards, bots, alerting stacks, PWAs, Home Assistant automations → Israel-Projects-Index or Israel-Preparedness-Index
• MCP servers and agents that serve Israeli data — the server is software, even when it wraps a dataset → Israeli-AI
• Prompt libraries, SOPs and planning documents — these are working material, not reference data
• Reference material with no Israel angle → Docs-And-Notes-Index
• Analysis and commentary — OSINT writeups, forecasts, situation reports — even when sourced from reference data

Overlap rules

Overlap with the other Israel indexes is expected and fine. This index is a cross-cut by material type, not a partition of subject matter:

• Israel-Projects-Index is the broad catch-all — most repos listed here also appear there, and should stay there.
• Israel-Preparedness-Index claims anything home-front. Shelter guidelines and news feeds sit in both: preparedness because of what they are for, here because of what they are.
• Israeli-AI requires a repo to be both AI-related and Israel-focused. A dataset built for agents to consume is not thereby an AI project — it belongs here, not there. This is the one place the overlap rule does not apply. The two indexes are a deliberate split rather than a cross-cut: that one covers the software, this one covers the structured context it reads. As of 2026-08-04 the boundary is stated in both directions — Israeli-AI's SCOPE.md excludes datasets and links here, and links here from its Contents nav. Keep both sides in step if the line moves.

When a repo could go in two places, list it in both rather than agonising. The question this index answers is "what Israeli reference data do I already have written down?"

Freshness

Almost everything here is a dated snapshot compiled from public sources, and unofficial. Entries should say so, and repos should carry the date they were verified and the source they came from. A stale snapshot that is clearly labelled is useful; an undated one is not.

Privacy

This index is public. Private repositories are not listed. Reference material that is private — anything household-specific, or carrying addresses, account details or unredacted personal data — stays out until the repo is made public.