Omnigraph
Graph engine for context assembly. Object-storage native. Agents work with graph data the way engineers work with code: branched, typed, reviewed, merged, audited, and governed.
Explore NYC neighborhoods by oil heating share and other demographics
Translation pending
AI summary · website content
DataJavaScript · HTMLGitHub @VionyxaiOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Heat pump turf map for NY Clean Heat door-to-door sales. It scores census tracts in Queens, Nassau and Suffolk (then the rest of the turf area) by how many 1–4 family homes there are, how old they are, what they heat with, owner-occupancy and incentive eligibility. Every tract is tagged Con Edison or PSEG Long Island. Queens also gets address-level walk lists.
npm test # offline check, no network needed
npm run pipeline # pull live data + score + walk lists (a few minutes)
npm run dev # open http://localhost:3000
Requires Node 18.17+. No npm install needed — there are zero dependencies.
The pipeline needs a free Census API key (https://api.census.gov/data/key_signup.html). Put it in .env as CENSUS_API_KEY for local runs, and add it as a repository secret named CENSUS_API_KEY (Settings → Secrets and variables → Actions) for the GitHub refresh.
Reps sign in on their iPhones, claim turf (the map shows who has what), knock houses (No answer / Come back / Not interested / Interested / Booked), and leave notes and map pins for each other. Everything saves on the phone first (works with no signal), syncs to Supabase, and the whole team sees it. Setup: supabase/README.md. The team (Issac, Matt, Gio, Kai) lives in config/team.json.
Push to GitHub, import the repo in Vercel, and deploy. vercel.json serves m3-map/ as-is.
To refresh the data without running anything locally: GitHub → Actions → Refresh data → Run workflow. It runs the tests and the live pipeline, then commits m3-map/data/, and Vercel redeploys. The office CSV (walklists_all.csv) is attached to the run as a download. You can still run npm run pipeline locally and commit the result instead.
SPEC.md — what it does and whyCLAUDE.md — how to work on it (read this first if you're an agent)config/ — every tunable number, endpoint and the turf boundary