# רשת הטעינה בישראל

> תיעוד מקור. מקור: docs/data-system/israel-network.md · 6a466bf.
> בגרסה הציבורית הושמטו מזהים תפעוליים ופרטי חשבון אישיים. קובץ המקור נשמר במאגר.

Baseline: bcf3ad4. Branch: feature/israel-data-network. Authorized scope: all available Israeli locality/model/operator/location data and license-plate technical lookup. This is an eMSP product between drivers/fleets and CPOs, not ownership of each network's chargers.

## Actual coverage

- Population Authority locality resource: 1,316 records, including source classification entries. Source updated 2026-11-01. `other-open` license as returned by the official metadata.
- Ministry of Transport charging resource: all 2,261 CSV records, with 2,261 SHP geometry matches by OBJECTID and normalized name. Israel TM geometry is transformed to WGS84 using the source projection. Forty CSV names have doubled escaped quotes; comparison normalizes that quoting only. The published KMZ is empty and was not used.
- This charging source was updated 2026-03-19, is partial national coverage and is not live status. Reported point counts are source totals, not connector identities or available sockets. Original operator aliases are retained. Source `cc-by` attribution appears in the UI.
- 26 operator/directory records: source operators plus requested networks missing in the source. ON-EV/Afcon, Scala, SONOL EVI, EV Edge, Zen, ViMore and Paz Charge identities were checked against their official websites. EV Energy is flagged for clarification because the matching website currently identifies itself as an information/marketing site. ZenEvCEP remains separate until its identity is confirmed. No operator is labelled integrated, and no customer relationships with these companies are asserted.
- Vehicle models are queried live from the official WLTP dataset (private from 1996, commercial from 1998), with bounded pagination. Variants/model years are not collapsed into an invented list of currently sold cars. This full catalog is accessible through the app but is not bulk copied into the database. Battery capacity and connector compatibility are not inferred from fuel type or battery voltage.
- Plate lookup queries one exact number from the official active private/light-commercial resource. It requires Clerk authentication, same-origin POST, strict 7/8-digit input and an atomic database quota of 30/day/user. No full national plate registry is copied. Only make/model/year/fuel/trim are returned; no VIN or owner data, no ownership claim, no implicit assignment to a tenant. Request/result bodies are not logged by the application or stored; responses are private/no-store. The quota stores only user/day/count. Operations must schedule retention cleanup of quota rows older than 30 days.

## Source registry

- <https://data.gov.il/dataset/3fc54b81-25b3-4ac7-87db-248c3e1602de>
- <https://data.gov.il/dataset/6910f861-4a90-4c40-a2c6-09dbc4bcd4a7>
- <https://data.gov.il/dataset/45e317cf-7bb1-4535-b8cf-be5e79ea341f>
- <https://data.gov.il/dataset/7a338622-63bb-4cfd-b3f7-0d2e8cf71033>
- Operator primary sources are in `lib/reference/operators.json`; there are no scraped commercial station inventories or guessed tariffs.

## Reproducible publication

Install `scripts/reference-requirements.txt` in an isolated Python environment. Run `scripts/import-israel-reference.py --input /private/work-directory --fetch`. Downloaded inputs and generated SQL batches remain outside the repository. The script validates pagination, total counts, duplicate keys, source changes, projection bounds and matching CSV/geometry identity; it fails on incomplete data. Review the manifest and compare record changes before publishing. It is not an unattended sync job and does not claim automatic freshness.

Apply the schema through normal migration review. Publish *all* prepared SQL batches inside one database transaction. Reruns upsert reference facts, do not silently delete missing sites, and preserve integration state/capabilities on existing operators. Absent records and re-used source IDs require review; a source OBJECTID is not a provider EVSE ID. Reconcile full snapshot differences before future updates. No end-user can write reference records or quota rows.

## Integration gates per CPO

1. Verify legal operator, brand aliases, sites and country/party identifiers.
2. Obtain a roaming/commercial agreement, API documentation and authorized sandbox credentials; choose OCPI, a roaming hub, or a proprietary adapter based on evidence.
3. Normalize locations → EVSEs → connectors and provider identifiers; never route commands by public-map OBJECTID.
4. Synchronize timestamped availability and versioned tariffs, including taxes/fees. Stale data remains unknown.
5. Certify token authorization, idempotent remote start/stop, delayed/out-of-order sessions, CDRs and reconciliation.
6. Agree PSP/merchant responsibility, fleet billing, refunds, settlement, incident ownership and support.
7. Enable only tested capabilities per operator/environment, then pilot with explicit limits.

The existing fleet financial records and charge credentials remain separate from the public directory. Loading directory data does not activate RFID tokens, billing, or remote charging. A provider's driver app is not an API permission, and LinkNodes does not collect users' passwords for other networks.

## Verification and release

The additive schema and all reference batches were applied to `dxeijkkmueuhvynvsgch`. Cloud migration versions are `20261107232907` (reference data) and `20261107233244` (private quota implementation). The MCP applies its own version timestamp; source filenames remain the CLI-generated migration identifiers. All 2,261 locations have matching coordinates. The Supabase security advisor reports no warnings/errors; six informational findings describe intentionally inaccessible private tables without client policies.

The existing unit suite passed 95 tests. Local PostgreSQL verification passed 26 tenant-isolation checks and 32 reference/permission/quota checks, with all test fixtures rolled back. `scripts/test-reference-db.mjs` requires an explicitly isolated local test database; it verifies anonymous/authenticated read-only access, quota isolation and the 30-call boundary. Browser tests cover source search, provider filtering, model lookup and 320/390px layouts. `scripts/check-reference-live.mjs` uses an explicitly prepared temporary Clerk identity for deployed plate-lookup verification; credentials, plates and results are never logged. Remove that identity with its `--cleanup` mode and remove its quota row after verification.

Rollback target before this release: product deployment `[operational-id-redacted]` (runtime commit `3ad255b`). Application rollback leaves these additive read-only catalogs in place; do not drop them or remove customer records as part of rollback.

Product deployment `[operational-id-redacted]` is READY at <https://product.linknodesenergy.com/network>, runtime commit `e0d2a0c`. All three browser scenarios passed against the deployed product. Eleven additional authenticated live checks passed, including the real official-source plate lookup and its UI, anonymous denial, foreign-origin denial, invalid input and the response whitelist. The temporary Clerk user was deleted (revoking its sessions), and its quota row was removed. No tenant, vehicle ownership record, payment or charging session was created by these tests. `/network` returns 404 on the separate company/admin surfaces. The execution environment requires its inspection proxy for browser/API verification; system-CA HTTPS requests independently succeeded.
