ARHCA tenders and what “more connectors” means

Reconn2 runs ARHCA Posted Today on the same Trigger → FastAPI path as ConstructConnect: Playwright login, tender list + detail scrape, raw JSON in Storage, and a source_runs row per run.

Same contract, new portals

Member portals rotate captchas, SSO flows, and HTML layouts. Each new source adds a Python callable, a Trigger task, and the same Storage + source_runs envelope. Graph projection follows once the extract shape is stable (ConstructConnect graph ingest is wired today).

Adding the next province or portal

New work is:

1. A Python automation callable with explicit settings in reconn2.config.Settings.
2. A Trigger.dev task + manual variant under trigger/src.
3. UI copy in the Automations hub and this marketing site — no new “data lake” or ETL silo.

Geography without gimmicks

We describe coverage by which portals you can operate, not by counting unrelated open-data programs. As more public agencies expose machine-readable procurement feeds, they can land in the same artifact + entity model — when they are actually connected.

Questions about a specific portal? Email us with the login URL and the fields you need extracted.