Initial public release

Knesset MK Tracking follows what Israeli Knesset members say on social
media and cross-references it against how they actually vote.

Released by The Public Knowledge Workshop under the MIT license.

Co-authored-by: yav02 <74302639+yav02@users.noreply.github.com>
Co-authored-by: gilpeled <101510239+gilpeled@users.noreply.github.com>
Co-authored-by: Savioor <25704274+Savioor@users.noreply.github.com>
Co-authored-by: inbararan <20068852+inbararan@users.noreply.github.com>
Co-authored-by: LuckyRonny <186024602+LuckyRonny@users.noreply.github.com>
Co-authored-by: danyaffe63 <226991234+danyaffe63@users.noreply.github.com>

Author: 6 people

.env.example

@@ -0,0 +1,25 @@
+# Copy this file to .env and fill in your actual values.
+# IMPORTANT: Never commit .env to version control.
+
+# Google Cloud Platform Project ID
+# This is the GCP project ID that hosts your BigQuery dataset.
+# Example: your-project-id
+GOOGLE_CLOUD_PROJECT=your-project-id
+
+# Path to a Google Cloud service account JSON key file
+# Create a service account in GCP with BigQuery and Gemini API permissions.
+# Download the key as JSON and point to its location.
+# Example: /path/to/service-account-key.json
+GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json
+
+# X (Twitter) API v2 Bearer Token
+# Obtain from https://developer.twitter.com/en/portal/dashboard
+# Requires Academic Research access or equivalent.
+# Example: AAAAABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnop
+X_BEARER_TOKEN=your-x-api-bearer-token
+
+# Google Gemini API Key
+# Obtain from https://aistudio.google.com/app/apikey
+# Used for embeddings and text summarization.
+# Example: AIzaSyDxxx...
+GEMINI_API_KEY=your-gemini-api-key

.github/workflows/ci.yml

@@ -0,0 +1,61 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  python:
+    name: Python
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync
+
+      # The repository currently has ~65 pre-existing ruff violations.
+      # Lint is reported but not enforced until that backlog is cleared;
+      # tests are the blocking gate. Contributions welcome — see CONTRIBUTING.md.
+      - name: Lint (ruff, advisory)
+        run: uv run ruff check .
+        continue-on-error: true
+
+      # Pure-Python tests. These need no cloud credentials and no built frontend.
+      - name: Run tests
+        run: uv run pytest -q tests/
+
+  frontend:
+    name: Frontend
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+          cache-dependency-path: ui/package-lock.json
+
+      - name: Install dependencies
+        working-directory: ui
+        run: npm ci
+
+      - name: Type-check and build
+        working-directory: ui
+        run: npm run build
+
+      # NOTE: ui/tests/ is deliberately not run here. Those tests need
+      # ui/data/analysis.json — pipeline output that is gitignored and never
+      # ships — and ui/tests/test_ui.py additionally needs Playwright browsers.
+      # Neither is available on a fresh clone. Run them locally after a full
+      # pipeline run: `uv run pytest ui/tests/`. Making these runnable in CI
+      # (via committed fixtures) would be a welcome contribution.

.gitignore

@@ -0,0 +1,37 @@
+# Python-generated files
+__pycache__/
+.pytest_cache/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Output data
+data/
+x_api_collect/data/
+ui/data/
+ui/raw/
+summary_creation/output/
+summary_creation/checkpoints/
+
+# Temporary files
+found_mks.*
+scratch/
+
+# Node / Frontend
+node_modules/
+*.tsbuildinfo
+
+# OS / System
+.DS_Store
+
+# Editor and agent config directories
+.obsidian/
+.gemini/
+.opencode/
+.claude/
+.agents/

.python-version

@@ -0,0 +1 @@
+3.13

CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [info@hasadna.org.il](mailto:info@hasadna.org.il). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,99 @@
+# Contributing
+
+Thanks for your interest in contributing to this project! We welcome contributions of all sizes — from bug reports and documentation improvements to feature work and code review.
+
+## Getting Started
+
+We follow [conventional commits](https://www.conventionalcommits.org/) in this project. Commit types include:
+- `feat:` — new feature
+- `fix:` — bug fix
+- `docs:` — documentation
+- `test:` — test additions or updates
+- `chore:` — dependencies, config, tooling
+- `refactor:` — code restructuring without behavioral change
+
+Example: `feat: add voting comparison view` or `fix: handle missing profile data`.
+
+## Development Setup
+
+### Backend (Python)
+
+Install dependencies with `uv`:
+
+```bash
+uv sync
+uv run pytest -q
+```
+
+Code quality is enforced with `ruff`:
+
+```bash
+uv run ruff check .
+uv run ruff format .
+```
+
+### Frontend (React/TypeScript)
+
+Install and run the dev server:
+
+```bash
+cd ui
+npm install
+npm run dev
+npm run build
+```
+
+Frontend code is linted with ESLint and formatted with Prettier (configured via your editor or pre-commit hooks). You should see any issues when you build or start the dev server.
+
+## Running Tests
+
+```bash
+# Python
+uv run pytest -q
+
+# Frontend (build validation)
+cd ui && npm run build
+```
+
+## Important: Cloud Infrastructure Requirement
+
+**This project requires a Google Cloud Platform project with BigQuery access to run the full pipeline.** The application will not function without:
+- A GCP project ID
+- A BigQuery dataset
+- A service account with BigQuery permissions
+- Google Gemini API credentials
+- X/Twitter API v2 bearer token
+
+There is currently **no offline demo mode**. If you'd like to contribute but don't have cloud access, here are great entry points:
+
+- **Frontend-only issues**: UI improvements, mobile layout fixes, new components
+- **Documentation**: README, API docs, architecture guides, translations
+- **Data/testing**: issue reporting, feature requests, UX feedback
+
+See `.env.example` for all required environment variables.
+
+## Submitting a Contribution
+
+1. Fork the repository and create a feature branch: `git checkout -b feat/your-feature-name`
+2. Make your changes, following the code style guidelines above
+3. Write or update tests for your changes
+4. Commit with a conventional commit message
+5. Push and open a pull request against `main`
+
+## Code of Conduct
+
+Please review our [Code of Conduct](CODE_OF_CONDUCT.md). We're committed to providing a welcoming and inclusive environment for all contributors.
+
+## Community
+
+We're part of **The Public Knowledge Workshop** (hasadna), an Israeli NGO building civic tech and government transparency tools.
+
+- **Weekly meetups**: Mondays at Google Campus Tel Aviv (Hebrew and English welcome)
+- **Email**: [info@hasadna.org.il](mailto:info@hasadna.org.il)
+- **Website**: [hasadna.org.il](https://hasadna.org.il)
+
+Questions? Don't hesitate to reach out — we'd love to meet you and discuss ideas for the project.
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the MIT License.

CONTRIBUTORS.md

@@ -0,0 +1,22 @@
+# Contributors
+
+This project was built over 8 days (July 30 – August 7, 2026) by a focused team. The repository history was reset at open-sourcing, so this file is the authoritative record of contributions.
+
+## Core Contributors
+
+| Commits | Name | GitHub |
+|---|---|---|
+| 78 | Yonatan Vershkov | [@yav02](https://github.com/yav02) |
+| 49 | Gil Peled | [@gilpeled](https://github.com/gilpeled) |
+| 16 | Alexey Shapovalov | [@Savioor](https://github.com/Savioor) |
+| 15 | Inbar Aran | [@inbararan](https://github.com/inbararan) |
+| 14 | Ronny Getz | [@LuckyRonny](https://github.com/LuckyRonny) |
+| 1 | Dan Yaffe | [@danyaffe63](https://github.com/danyaffe63) |
+
+## Acknowledgements
+
+Special thanks to [@TalGetz](https://github.com/TalGetz) for contributing 12 of the project's 29 issues and shaping the roadmap. Though this represents no code commits, the work of defining scope, prioritizing features, and providing product direction was invaluable to the team's success.
+
+---
+
+**The Public Knowledge Workshop** (הסדנה לידע ציבורי) is an Israeli NGO advancing civic tech, government transparency, and digital rights. Learn more at [hasadna.org.il](https://hasadna.org.il).

Dockerfile

@@ -0,0 +1,42 @@
+# ---- Frontend build stage ----
+FROM node:20-slim AS ui-build
+WORKDIR /app/ui
+COPY ui/package.json ui/package-lock.json ./
+RUN npm ci
+COPY ui/ ./
+RUN npm run build
+
+# ---- Backend runtime stage ----
+FROM python:3.11-slim
+
+# Install system dependencies (curl for download_knesset_data and for uv)
+RUN apt-get update && apt-get install -y curl ca-certificates && rm -rf /var/lib/apt/lists/*
+
+# Install uv
+COPY --from=ghcr.io/astral-sh/uv:0.12.0 /uv /bin/uv
+
+# Set working directory
+WORKDIR /app
+
+# Copy the entire project
+COPY . /app
+
+# Bring in the frontend built in the ui-build stage (ui/dist is gitignored,
+# so it isn't present in the plain `COPY . /app` above).
+COPY --from=ui-build /app/ui/dist /app/ui/dist
+
+# Install dependencies for the main project
+RUN uv sync --frozen
+
+# Install dependencies for the x_api_collect sub-project
+RUN cd x_api_collect && uv sync --frozen
+
+# Install dependencies for the bill_issues sub-project
+RUN cd bill_issues && uv sync --frozen
+
+# Ensure scripts are executable
+RUN chmod +x /app/run_daily_pipeline.sh
+
+# The default command will be overridden by Cloud Run (for web) and Cloud Run Jobs (for daily tasks)
+# But we can set a sensible default, like running the web server
+CMD ["uv", "run", "mkwork", "--host", "0.0.0.0", "--port", "8080"]