Candidate tokens
Derived from source slugs, remote ids, names, domains, and websites.
Dry-run first
Route probing reports matches and unknowns without persistence by default.
Apply deliberately
Add --apply only after inspecting matched route metadata.
```bash
uv run openopps admin providers probe-routes --source a16z --provider any --limit 25 --json
```
By default, probing only checks routes missing token or URL metadata and does not persist results. Use `--include-existing` to recheck existing routes and `--apply` to persist matched metadata.
## Provider Health [#provider-health]
Provider health samples source adapters and job-capable routes, then reports status counts:
```bash
uv run openopps providers health --source a16z --provider any --limit 25 --json
```
Health checks report `active`, `empty`, `error`, `missing_route`, `not_covered`, and duplicate route skips. Add `--apply` to persist source health under `raw_metadata.health` and board-provider route health under `last_status`.
Use provider health for live sampled HTTP status. Use provider coverage for offline persisted route coverage and enrichment quality. Use provider audit for candidate-provider adoption evidence.
## Board Route Registry [#board-route-registry]
The `board_providers` registry is the executable route layer between discovered boards and job sync. Use it before large syncs to confirm which routes are ready:
```bash
uv run openopps admin providers registry --provider any
uv run openopps admin providers registry --provider any --passed-probe-only --json
uv run openopps admin providers registry --provider any --include-missing --limit 50
```
Without `--include-missing`, `admin providers registry` skips job-capable hints that still lack executable metadata, such as an Ashby board token or complete Workday CXS route. `--passed-probe-only` narrows output to routes verified by a persisted `admin providers probe-routes --apply` result.
Use [Explorer](/explorer) to inspect the generated static snapshot of persisted boards, board-provider routes, latest job rows, source/provider coverage, and data-quality signals.
## Provider Limits [#provider-limits]
* Workday support is limited to public postings visible through careers sites; it is not official tenant API access.
* Ashby sync excludes `isListed: false` direct-link-only postings from normal output.
* Overlapping board records from multiple sources are merged by company domain. Board JSON includes `source_keys` and `source_board_keys` for every source currently represented by the canonical board, and provider requests are deduped before route probes and job syncs.
* Installed Python plugins are not sandboxed and run in the same process as OpenOpps.
* Use `OPENOPPS_PLUGIN_ALLOWED` to opt in trusted entry-point names before plugin code executes.
* Use `OPENOPPS_PLUGIN_AUTOLOAD=true` only in controlled environments where every installed `openopps.plugins` entry point is trusted.
# Public Data Releases (/docs/public-data-releases)
OpenOpps can build a version 7 public-data publication without changing the legacy version 6 tree. Version 7 is content-addressed: a small mutable channel pointer selects one immutable release, and every consumer verifies that release before reading its assets.
This is an operator and governance contract, not a deployment announcement. The repository contains local generation, verification, staging, rollout-plan, remote-readback, and recovery-archive tooling. A successful live Workers rollout, production-snapshot rights approval, and a GitHub Release attestation for the public-data archive have **not** been established by those local tools or by the current CI workflow.
## Publication layout [#publication-layout]
```text
publication-root/
├── channels/
│ └── production.json
└── releases/
├──