LandHunter Civil Awareness Scanner

Distributed corpus gathering for the LandHunter Strategic Assessment Atlas

0 Available Jobs

Chunks waiting for workers

0 Active Workers

Checked in last 12 hours

0 Completed & Verified

Jobs finished this cycle

2 Registered Workers

Total identities issued

What This Is

The LandHunter Civil Awareness Scanner is the public coordinator for the LandHunter Strategic Assessment Atlas β€” a research project mapping zoning, governance, and environmental factors across all 3,143 U.S. counties.

Volunteers contribute idle computer time to fetch, verify, and stage public data from county GIS servers, municipal code libraries, and election portals. All work is broken into small, auditable chunks. No judgment, no scraping of private data β€” only public records, fetched politely.

What Workers Do

πŸ” Examination

Re-run a parser over a staged data blob to verify measurements match exactly. Deterministic β€” two independent workers must agree.

πŸ“₯ Ingest

Download all pages of a county's GIS service (zoning layers, parcel data) following a frozen fetch plan. Byte-hash verified against a 5% sample re-fetch.

πŸ›°οΈ Alt-Source Probe

Mechanical probes of candidate GIS endpoints: enumerate services, count features, test pagination, check for null codes. No judgment β€” just structured reconnaissance.

πŸ—ΊοΈ State Walk

Walk a slice of a municipal code library (Municode, American Legal, etc.), extracting district titles and slug keys per a fixed recipe.

πŸ”Ž Search

Run fixed query plans against search APIs (Brave, Bing) to locate election results, zoning portals, or certified PDFs. Results graded by source class.

🧠 Classify (opt-in)

Grade a search-result set against a rubric with a small model running on YOUR machine. Output is proposal-grade only β€” it ranks hints for the operator and never enters verified data; only deterministic probes do that.

Privacy & Transparency

βœ… What We See

  • Your platform (OS/arch) and client version
  • Chunk type capabilities you offer
  • If you opt into local-model grading: the model family, quant and context size you declared β€” nothing else about your machine
  • Heartbeat timestamps while a lease is active
  • Structured results (manifests + blob hashes)

❌ What We Never See

  • Your files, browser history, or personal data
  • Any outbound connections except to the chunk's target host
  • Your IP beyond the coordinator's rate-limit bucket (hashed)
  • Executable code β€” chunks are declarative fetch plans only
  • πŸ” Your Control

    • Run only the chunk types you choose (--capabilities)
    • Limit concurrency (--concurrency 1..8)
    • Schedule windows via your OS (cron, Task Scheduler, launchd)
    • Dry-run mode (--dry-run) stages locally, submits nothing
    • Local grading is opt-in: run a small open-weights model on your machine, point at a server you already run, or connect your own API key β€” search-result snippets leave your machine only if you choose a cloud endpoint
    • Stop anytime β€” in-flight chunks requeue for others

    πŸ›‘οΈ Supply-Chain Safety

    • Single static binary (musl) β€” no runtime dependencies
    • Docker image: FROM scratch, non-root user
    • ed25519-signed contracts verified before execution
    • Outbound allowlist pinned per chunk (no open proxy)
    • Source code auditable on request; contracts are ed25519-signed at issuance (installer binaries currently ship unsigned)

    Get Started

    2

    Register

    ./lh-contributor register

    Creates a client identity (saved to credentials.json inside your work dir β€” default ./lh-work β€” with 0600 permissions).

    3

    Run

    ./lh-contributor run

    Polls for leases, executes chunks, heartbeats, uploads blobs, submits results. Add --once for a single chunk, --dry-run to test locally.

    4

    Configure (Optional)

    Environment variables:

    • LH_COORDINATOR_URL β€” tracker endpoint (default: production)
    • LH_PUBLIC_KEY_HEX β€” ed25519 public key for contract verification
    • LH_CONCURRENCY β€” parallel slots 1..8 (default: 2)
    • LH_WORK_DIR β€” work/staging directory (default: ./lh-work, relative to where you run the binary)
    • LH_R2_* / LH_UPLOAD_PRESIGN_TEMPLATE β€” blob upload target

    Requirements

    βœ… Minimum

    • 64-bit CPU (x86_64 or ARM64)
    • 512 MB RAM available
    • 1 GB free disk for staging
    • Outbound HTTPS (port 443)
    • Linux / macOS / Windows 10+

    🌐 Network

    • No inbound ports required
    • Outbound to coordinator + chunk target hosts
    • Politeness enforced: per-host request budgets signed into each contract (default ≀60 req/min)
    • No VPN/proxy needed (residential IP preferred for some GIS)