Data sources
Supported source paths, configured collection cadence, and the product surfaces they can feed.
Beta coverage status. A configured connector or schedule does not mean a source is currently healthy, complete, or accepted for production. Check the source-health view for the latest collection and coverage in your workspace. The forecast registry counts source definitions; each adapter has its own review and provider evidence. The source-only registry currently records 17 connector families: 13 real-depth paths with fixture tests and 4 thin generic or mixed-adapter paths.
| Source | Cadence | What it can feed |
|---|---|---|
SAM.gov opportunities | hourly | Solicitations, presolicitations, sources-sought, award notices — plus points of contact (Contact Intelligence). |
USAspending awards | nightly | Contract awards: incumbents, values, periods of performance → recompete detection, agency landscape, the graph. |
Historical NAICS ↔ PSC pairings | scheduled | Repeated USAspending, SAM.gov, and historical-award co-occurrence seeds the governed many-to-many capability crosswalk. One pairing cannot activate an inference. |
Simpler.Grants.gov | nightly | Federal funding opportunities for the Grants view. |
GAO bid protests | daily | Protest decisions (RSS/JSON) → Protest Intelligence and re-opportunities. |
Federal Register | daily | Procurement-relevant notices, proposed rules, and policy changes → early market-intent signals. |
Agency forecasts / OSDBU | weekly | The generated registry contains 4 definitions: 4 source-specific real-depth adapters and 0 generic HTML adapters rated thin. Static configuration declares 4 active and 0 degraded definitions; those labels are not runtime health. |
Congressional Budget Justifications | monthly | LLM-extracted budget lines → candidate predicted opportunities. Actual lead time remains an evaluation measure. |
SAM Entity + SBA DSBS | on demand | Teaming-partner search: registered small businesses by NAICS with certifications, enriched with DSBS capability profiles. |
Every signal keeps its provenance: source, authority rank, observation time, content hash, revision, changed fields, parser version, source-record citations, attachment manifests, and a content-addressed raw-snapshot reference. Lower-authority conflicts remain evidence without replacing the canonical signal. Ambiguous correlations enter a governed human-review queue, and admins can watch connector freshness, acceptance, retries, and dead letters on the source-health panel.