Corrections and provenance

Every mistake we have published, and what fixed it

This is the public corrections register for OpenBid HQ, mirrored from docs/CORRECTIONS.md in the repository. When we publish something wrong, it gets an entry here: what was wrong, where, and what replaced it. Entries are append-only; we never edit a published entry, we add a follow-up instead.

Silent fixes are a doctrine violation. If a page you relied on changed because it was wrong, you should be able to find that change here.

Corrections register

22 entries, newest last. The register started empty (no known published errors) and every entry since is listed below.

  1. 2026-08-13audit-cycle-1

    Post-audit corrections (adversarial audit cycle 1)

    What was wrongHome "Today's Board" showed a mock bid board with no demo label; FeatureStrip claimed "Filter live solicitations" plus unqualified award-history and forecasting features; the Methodology headline "Verified by hand" overstated the checking; REQ-10, RISK-04, and matrix R11 statuses were stale after the signup-disclosure fix.

    What fixed itDemoBadge added to the board; FeatureStrip reworded to Preview/planned with live feeds explicitly not connected; headline softened to "Checked against official sources"; the stale doc/code statuses reconciled. Site-wide honesty claim upgraded from "failed audit" to "corrected", re-audit pending.

  2. 2026-08-13C-002

    Fabricated intelligence and home-board data removed

    What was wrongThe Intelligence page shipped six fabricated datasets (mock bid board, award history, expiry timeline, set-aside filter, addendum drawer, vendor profile with fake UEI/CAGE and sparkline) and the Home "Today's Board" showed six invented bids with invented values and deadlines. Present since the initial demo build; labeled demo after the audit, but doctrine treats realistic fabrication as a standing risk even when labeled.

    What fixed itAll of it deleted and replaced with live USAspending.gov data (federal awards, FL place of performance): LiveAwardSearch, ExpiringContracts, VendorProfile (real UEI/DUNS only; CAGE is not returned by the API and is no longer shown), live Dashboard board. AddendumDrawer removed with no replacement; no real addenda source exists. Every live figure now routes through FigureValue and fetch failures render a loud error panel.

  3. 2026-08-13C-003

    Dead interactive elements, a fabricated ticker, and six broken/moved external links

    What was wrongThe Ticker still showed fabricated bids with no source and no click target (a leftover C-002 missed). Clickable-looking elements across Home, LevelsFunnel, FeatureStrip, and award search had no action. The Local county panel showed a dead "Profile coming" state for 62 of 67 counties. Six external URLs were broken or moved (SUBNet, DMS OSD, myflorida.com, census.gov GID, hcfl.gov, orangecountyfl.net). The FigureValue popover closed on blur, and Directory phone numbers and emails were plain text.

    What fixed itTicker rewritten to live USAspending lines linking the verified award page; dead controls now navigate or open real surfaces; the county panel shows a live trailing-12-month federal-obligations total per county plus a curl-verified Florida Association of Counties link; the six URLs replaced with verified equivalents; FigureValue closes on Escape and outside pointer-down; tel: and mailto: wired.

  4. 2026-08-13audit-cycle-2

    Post-audit corrections (clickability audit cycle 2)

    What was wrongThe directory High-Volume Agencies Index URL (myflorida.gov/myflorida/government/) returned HTTP 404, masked by an SPA catch-all, and UI_INVENTORY.md falsely claimed it was verified 200. A FeatureStrip decorative widget contained bid-like text ("AWARDED 2023 / EXPIRES Q2 2026").

    What fixed itURL repointed to https://www.myflorida.gov/ (curl-verified 200) and the false verification claim corrected. Widget text replaced with generic field labels "AWARD DATE / EXPIRY DATE". The "All external URLs verified" claim was downgraded to record per-host exceptions.

  5. 2026-08-14audit-cycle-3

    Live-data verification audit (cycle 3)

    What was wrongThe Transparency sample bid tabulation used fabricated bidder names, amounts, and a fabricated solicitation number ("ITB 25-041") under a "PUBLIC RECORD" stamp.

    What fixed itReplaced with generic placeholders, relabeled "SAMPLE BID TABULATION, ILLUSTRATIVE ONLY", and now carrying a DemoBadge. The audit otherwise confirmed all dynamic figures live or static/estimate-labeled with provenance, and all error paths loud with nothing substituted.

  6. 2026-08-15regression-2026-08-15

    Multi-state architecture: deliberate regression record

    What was wrongDuring the multi-state build, equivalentPath() in src/lib/states.ts was temporarily broken to drop the mirrored suffix (/tx/search became /tx).

    What fixed itsrc/test/multi-state.test.tsx caught it (2 failures, 12 passing). The function was restored and the full suite went green. The same entry records the TX verification: state filter curl-verified live on USAspending, 254 TX counties from the verified plotly GeoJSON, 5 county portal URLs re-verified 200 before publishing.

  7. 2026-08-17url-sweep-2026-08-17

    Full external URL re-verification sweep

    What was wrongExternal URLs that had never been curl-verified carried weaker verification states, and several were stale or dead: the NYC CROL feed pointed at a community-created view, and county portal links for Broome, Rensselaer, Dutchess, Albany, Orange, Schenectady, Columbia, and Indian River were 404 or moved.

    What fixed itEvery remaining URL re-checked with browser-UA curl, then a real browser where curl was blocked. NY sources (OGS, MTA, ESD, SUCF, CUNY) upgraded; the CROL feed re-pointed to the official City Record Online dataset dg92-zbpx; dead county links fixed; TX SmartBuy confirmed; FL reached zero unverified counties. URLs that still failed (Nassau, Onondaga, Rockland, St. Lawrence, Niagara, Jefferson, Oswego, Open Book NY, Checkbook NYC, Empire State Bid System) keep their honest blocked or unverified states.

  8. 2026-08-15url-sweep-2026-08-15

    URL re-verification sweep applied (CA/GA/VA/AZ/NC/NY registries)

    What was wrongDozens of registry links across CA, GA, VA, AZ, NC, and NY still carried weaker bot-blocked or unverified badges, and 16 entries were dead (404, mis-pointed, or a parked GoDaddy domain at lapazcountyaz.org) or stale redirects.

    What fixed itMass verification event with real browser egress (reverification_sweep.md). 58 entries upgraded to browser-verified on sweep evidence (CA 6, GA 15, VA 17, AZ 4, NC 13, NY 3); 7 URLs replaced with exact sweep-recorded redirect targets (longbeach.gov purchasing-division, sbsd.virginia.gov, fcva.us bids-rfps, buncombenc.gov, bidnetdirect.com, rocklandcountyny.gov, jeffersoncountyny.gov); 16 dead links without a verified replacement keep their old URL with an honest unverified badge and a not-found-in-the-2026-08-15-sweep note. Still-blocked and inconclusive entries keep their existing honest badges.

  9. 2026-08-14url-sweep-2026-08-14-b

    Browser sweep 2 applied (100-URL browser-egress re-verification)

    What was wrongLinks still badged bot-blocked or unverified after the prior sweep needed a second browser-egress pass; several URLs had silently gone dead or moved, including transportation.gov/osdbu/procurement-forecast and the SBA capability-statement guide (both newly dead), durhamnc.gov/202 now resolving to a police substation page (wrong content), SBA program pages 301ing from /federal-contracting/* to /certifications/*, calc.gsa.gov retired to buy.gsa.gov/calc.html with its API decommissioned, and the Census API now requiring a key (missing_key.html redirect) where allinone_research.md assumed keyless.

    What fixed itbrowser_sweep2.md applied: 19 upgrades to browser-verified on live-render evidence, 6 redirect-replacements to exact browser-landed URLs (DOJ OSDBU doing-business page, legacy.sba.gov SUBNet, sba.gov/certifications/#8a-program, sba.gov/certifications/contracting-assistance-programs/#mentor, buy.gsa.gov/calc.html, srpnet.com root), 18 dead entries kept listed with honest not-found notes (Durham flagged wrong-content), the 8(a)/WOSB/HUBZone/VetCert move to certifications.sba.gov added with a moved notice, and a dated correction note added to allinone_research.md for the Census-key and CALC-retirement changes. Still-blocked, inconclusive, and not-re-run entries keep their existing honest badges.

  10. 2026-08-14url-sweep-2026-08-14-c

    Browser sweep 2 addendum applied (second pass, 20 re-checks)

    What was wrongThe sweep-2 addendum re-ran the 11 inconclusive and 9 not-run URLs. Five links had moved to verified redirect targets (sba.gov HUBZone and WOSB program pages to /certifications/* anchors, www.sbsd.virginia.gov to sbsd.virginia.gov, osdbu.dot.gov to transportation.gov/osdbu, and the GSA per-diem page to /travel/plan-book/per-diem-rates), esd.ny.gov rendered live in a browser, and three links were confirmed dead (the Albemarle purchasing deep link after a Granicus redesign, fdot.gov/equalopportunity/dbe.shtm, and the SBA contracting officials directory).

    What fixed itThe five redirect targets were swapped in (including the VA toolkit pages and thresholds for sbsd.virginia.gov), esd.ny.gov was upgraded to browser-verified in the eligibility links registry, and the three dead links were kept listed with honest not-found notes rather than guessed replacements. Three resolved still-blocked and eight still inconclusive URLs keep their existing badges. Cumulative sweep-2 totals: 20 upgrades, 11 redirect-replaces, 21 dead, 40 still-blocked, 8 inconclusive, 0 not-run.

  11. 2026-08-15url-sweep-2026-08-15-b

    Browser sweep 3 applied (48 URLs re-checked)

    What was wrongThe 40 bot-blocked and 8 inconclusive URLs left after sweep 2 needed a third browser pass. Two blocks had lifted (cap-az.com doing-business page and the Dutchess County BidNet portal), the Chesterfield County purchasing URL was confirmed dead (Custom404 twice, resolving sweep 2's mixed reading), and niagaracounty.com/bids was found redirecting to niagaracounty.gov/bids.

    What fixed itBoth recovered links upgraded to browser-verified with dated evidence; the Chesterfield link kept listed and flagged with no guessed replacement; the Niagara stored URL updated to the .gov redirect target with the badge kept bot-blocked. 37 still-blocked entries confirmed with fresh evidence; the 8 inconclusive URLs failed again (3-4 consecutive failures) and are now recommended for production-network verification instead of more sandbox passes.

  12. 2026-08-15url-sweep-2026-08-15-c

    Browser sweep 3b applied (new-state registries)

    What was wrongThe new-state registries (AL, MD, OH, CO, WA, MA, IL, NJ, MO) still carried 89 bot-blocked or unverified URLs after sweep 3. Browser re-checks showed 37 links live (including all four mass.gov org pages, the BidNet Direct Colorado group with 391 open solicitations, 12 Ohio entries, and 9 Alabama entries), 5 links redirecting to live final URLs, 8 links dead (404s and a TLS cert mismatch at monmouthcountynj.gov), and 4 county domains migrated (ccgov.org, douglas.co.us, hudsoncountynj.org, plattecountymo.gov).

    What fixed itSweep-3b verdicts applied exactly: 37 upgrades to browser-verified with dated evidence notes, 5 redirect-replacements to the exact final URLs landed on, 8 dead entries kept listed with unverified badges and no guessed replacement (the Morgan County nav candidate noted as a candidate, not substituted), and 4 domain-migration URLs updated with badges kept bot-blocked per the niagaracounty.gov precedent. 17 still-blocked and 21 inconclusive entries keep their existing honest badges; 65 URLs (WA 25, IL 23, CO 9, MA 8) were not re-run and are the remainder for a future pass.

  13. 2026-08-19C-004

    Wrong Oregon statute figures and stale Missouri county counts in new-state sections

    What was wrongorThresholdsData.ts asserted ORS 279B.065 small procurement at $10,000 and the 279B.070 intermediate band at $10,000-$150,000 as kind official figures even though the statute text had never been read in-session (2023 c.127 raised both to $25,000 / $25,000-$250,000 effective 2024-01-01). Separately, the MI/TN/IN/WI/KS/NM/NE/ID sections carried stale Missouri template copy: "Open the 115-county local explorer", "Filter 115 county-equivalents", and header comments citing state "MO" / 115 county-equivalents.

    What fixed itOR figures updated to $25,000 (279B.065) and $25,000-$250,000 (279B.070), re-verified in-session against the oregon.public.law statute mirror (full text read, 2023 c.127 history line) and OAR 125-247 mirrors; the official host oregonlegislature.gov remains unreachable from the sandbox and the cards say so. Each state's correct county-equivalent count restored (MI 83, TN 95, IN 92, WI 72, KS 105, NM 33, NE 93, ID 44).

  14. 2026-08-16C-005

    Wave-4 audit fixes: shared checklist storage keys, Teton County WY badge, Maine waiver wording

    What was wrongFour final-wave checklist components (RI, MT, SD, ND) reused the Idaho localStorage key sunbid-toolkit-id-checklist, so checklist state bled across states. Separately, the Teton County WY portal entry carried a curl-200 badge from 2026-08-15, but re-verification on 2026-08-16 timed out twice (curl 000) and the browser check failed. The Maine thresholds prose implied procurement below $10,000 is categorically not required, when 5 MRS 1825-B section 2(G) makes it a waiver ground.

    What fixed itEach checklist now uses its own state key (sunbid-toolkit-ri/mt/sd/nd-checklist); no -id-checklist references remain outside src/pages/id/. The Teton County entry is downgraded to unverified with a dated note describing the 2026-08-16 timeout. The Maine copy now says competitive selection may be waived below $10,000 under 5 MRS 1825-B section 2(G), not categorically exempt; the figure citation is unchanged.

  15. 2026-08-16C-006

    Forsyth County NC portal URL pointed at Forsyth County Georgia

    What was wrongThe Forsyth County entry in the North Carolina county portal registry linked to forsythco.com/government/departments/procurement/, which is Forsyth County GEORGIA (the same host is correctly used in gaPortals.ts). Forsyth County NC purchasing is the joint City-County Purchasing office with Winston-Salem.

    What fixed itURL replaced with https://www.cityofws.org/672/Purchasing, badge browser-verified. The page states it buys for the City of Winston-Salem, the City/County Utilities Commission, Forsyth County, and the Winston-Salem Transit Authority; bids post at cityofws.org/bids.aspx. Curl returns 403 (bot protection); verified live via browser 2026-08-16.

  16. 2026-08-20C-007

    Stale Ohio county bidding line and Idaho local purchasing lines after 2023/2025 amendments

    What was wrongohThresholdsData.ts asserted the ORC 307.86 county competitive bidding line at $50,000 even though HB 33 (effective 2023-10-03) rewrote 307.86 to reference the ORC 9.17 indexed amount ($75,000 through 2024, $77,250 for 2025, +3%/yr thereafter). Separately, idThresholdsData.ts and the ID toolkit/home copy still showed the pre-2025 Idaho Code 67-2806 goods/services lines ($50,000-$100,000 informal, formal at $100,000) and the 67-2803(2) $50,000 exclusion even though SB 1118 (effective 2025-07-01) raised them to $100,000-$250,000 semi-formal, formal above $250,000, and a $100,000 exclusion.

    What fixed itOH figure updated to the ORC 9.17 indexed amount ($77,250 for 2025) with the indexing caveat stated in the figure description, body, and vendor copy; assertFigure structure and the honest codes.ohio.gov verification note kept. ID figures updated to $100,000-$250,000 semi-formal and formal at $250,000 or more (67-2806 as amended by SB 1118, eff. 2025-07-01), the 67-2803(2) exclusion to $100,000, and the toolkit/checklist/home copy aligned.

  17. 2026-09-04C-008

    Curated Florida figures and unsupported regional activity

    What was wrongRegional pages displayed unsupported activity counts and rankings, including "Statewide: 412". Directory copy claimed $1.6B+ in purchasing and timestamps its cards did not display. Vendor and threshold pages presented $7.5M as a current/general contract ceiling, construction base amounts as effective thresholds, and an unsupported 2026 IT explanation for Category Four. Wage copy incorrectly linked right-to-work to prevailing-wage rules and implied coverage of every federally funded project; drug-free workplace copy promised free, automatic tie wins. Vendor Path treated Lenis global metadata as a scroll-controller instance, causing an error after smooth-scroll initialization.

    What fixed itRegional panels count the buyers actually listed; unsupported activity estimates and rankings are removed. Directory counts derive from displayed lists, and unsupported purchasing-volume and timestamp promises are removed. Threshold and vendor-tier figures share provenance records. Construction amounts are labeled statutory bases requiring a project-year adjustment; the current CCNA annual project cap remains explicitly unverified. The MFMP fee carries its source and fiscal period. No current adjusted amount or retrieval date is invented; this correction is not a full legal review. Wage coverage and the drug-free workplace preference now state their applicable conditions and link to Department of Labor and Florida statute sources. Vendor Path no longer calls a controller method on Lenis metadata; the complete route is covered by a regression test.

  18. 2026-10-19C-009

    Stale Indiana public works lines, Idaho license line, Ohio county line, and wrong sources after the fact-drift bot flags

    What was wrongIndiana public works copy said competitive bids from $150,000, but IC 36-1-12-4 and 36-1-12-4.7 (as amended by P.L.86-2025) set bids at $300,000 or more and quotes from $50,000 to under $300,000. Idaho copy said a public works contractor license is required from $50,000, but Idaho Code 54-1903(9) exempts projects estimated under $100,000. Ohio showed the 2025 county amount ($77,250) instead of the 2026 amount ($79,568), stated that Ohio has no state prevailing wage law, and cited 122.71 for the 15% MBE set-aside. Hawaii showed its electronic small-purchase band from $25,000 instead of $50,000 (HRS 103D-305(c), amended 2025). Kentucky showed $40,000 for the KRS 424.260 local bid line, which is $50,000 from July 15, 2026. Several figures linked to pages that do not state them.

    What fixed itIndiana public works $300,000 bid line, $50,000 to under $300,000 quotes, own-workforce line described as $375,000 adjusted each year. Idaho license line $100,000; goods formal line over $250,000. Ohio county line $79,568 for 2026 sourced to the Department of Commerce page; prevailing wage sentence corrected; MBE set-aside cited to ORC 125.081. Alaska, Wyoming, West Virginia and Idaho figures link to the pages that state them. Hawaii HIePRO band corrected to $50,000. Kentucky local bid line corrected to $50,000. Vermont state simplified-bid line corrected to $250,000 (Bulletin 3.5).

  19. 2026-10-20C-010

    SBA size standards misread from eCFR footnotes, and certification size gates

    What was wrongThe size-standard checker showed NAICS 541715 at 11 employees; 13 CFR 121.201 sets 1,000, and "11" was a footnote number read as the value. The four banking codes were treated as $850 million in receipts instead of $850 million in assets, and the table's 14 exception entries were missing. The certification roadmap said HUBZone, WOSB/EDWOSB and VetCert require being small under the primary NAICS code.

    What fixed itAll 992 rows regenerated from the eCFR page with footnotes kept apart from values, the 14 exception entries kept and asset-based standards recorded; the checker asks which activity applies and asks for total assets for the banking codes. The certification checklists say any NAICS code listed in the SAM profile (13 CFR 126.200, 127.200, 128.200).

  20. 2026-10-20C-011

    Official-source corrections from the 20 October data accuracy audit

    What was wrongMichigan guidance ignored restored prevailing wages; four RFQ checklists copied Missouri rules. Oregon interactive bands and Texas local thresholds were stale, and Texas used the wrong city citation. California public-works copy conflated wage coverage, registration, apprenticeship and award reporting. HHI used the old DOJ/FTC bands without identifying their vintage.

    What fixed itOfficial sources support covered Michigan state-project wages, jurisdiction-specific RFQ rules, Oregon goods/services bands of $25,000/$250,000, Texas local triggers strictly over $100,000 under 262.023(a)/252.021(a), distinct DIR obligations and exemptions, and the 2023 HHI reference above 1,800. D5 (California school amount) and D7 (SB/DVBE Option) remain UNVERIFIED and unchanged because the official pages could not be opened.

  21. 2026-10-20C-012

    State fact-check follow-up: Ohio, West Virginia and Alaska

    What was wrongOhio repeated the old county line, required Controlling Board approval without the competitive-selection alternative, and described every bid guaranty as 10%. West Virginia omitted the subcontractor-list cure request and vendor fee exemptions. Alaska required written quotes above $25,000 instead of distinguishing the $50,000 writing boundary. Vermont presented an unsupported statewide town line, and Idaho public works was described as informal quotes.

    What fixed itOhio county bidding strictly above $79,568 for 2026, competitive selection or Controlling Board approval at the cumulative $50,000 line, and full-bid bond, 10% check/credit or qualifying electronic verification options. West Virginia disqualification follows failure within one business day of the required request; sole-source and small-purchase vendor fee exemptions are stated. Alaska requires three contacts above $25,000 and written solicitation and responses above $50,000. Vermont's $10,000 municipal line had no official source and was removed; town lines are set by each town (example: Barre charter, 24 App. V.S.A. ch. 101, § 31). Idaho 67-2805 public works between $100,000 and $250,000 requires written bid solicitations to at least three licensed public works contractors, not an informal quote process. Other unverified rows retain their existing dates.

  22. 2026-10-20C-013

    State facts d2b: Alabama bonds, Wisconsin simplified bidding, Georgia operating bands and Colorado rules

    What was wrongAlabama repeated a universal notice schedule and misstated bid-guaranty bases and payment bonds. Wisconsin used a $25,000 operating ceiling. Georgia treated $100,000 as the sealed-process entry point and excluded exactly $250,000 from its longer posting band. Colorado used a $100,000 state bond line, the wrong wage citation and a seven-working-day protest clock.

    What fixed itAlabama authority-specific notices, alternative guaranty bases and 100% performance/at least 50% payment bonds; Wisconsin simplified bidding over $5,000 through $50,000; Georgia open-market competition from $25,000 and 15-calendar-day posting from $250,000. Colorado state security over $150,000, correctly scoped wages and 10-business-day IFB/RFP protests (3 for small purchases unless extended to 10). Colorado state construction bonds and California school bidding remain unverified and unchanged; only opened figures received new dates.

Where every byte of production data comes from

Mirrored from docs/PRODUCTION_DATA_PATHS.md. OpenBid HQ is a React application served by a Cloudflare Worker, with browser-direct public-data calls and a separately gated D1-backed opportunity and alert service. This map lists how data enters, moves, or leaves the running product. Check the Status page for current service readiness and refresh outcomes.

Static curated content (info.md, page data files, prose)

ACTIVE, compile time

Bundled at build time. Provenance-carrying figures are validated by assertFigure at module load.

PRODUCTION_DATA_PATHS.md §1

Browser-local saved work (saved searches, pipeline, checklists, display preferences)

ACTIVE, client-only for these tools

These tools use local browser storage and are not uploaded. Opportunity-alert signup is a separate opt-in path: its form is sent to the Worker and the email address is encrypted in D1 after submission.

PRODUCTION_DATA_PATHS.md §2

Live USAspending connector (spending_by_award, awards/{id}, spending_by_category, spending_over_time)

ACTIVE since 2026-08-13

Browser direct to api.usaspending.gov. No proxy, no backend, no API key. Failure renders a loud ErrorPanel; nothing is substituted.

PRODUCTION_DATA_PATHS.md §2b

Search path (federated award search + static in-browser datasets)

ACTIVE since 2026-08-14

POST spending_by_award with only verified filters, plus bundled datasets searched locally. Nothing the user types goes anywhere except the USAspending API calls.

PRODUCTION_DATA_PATHS.md §2c

Static verified county portal dataset (67 FL counties, districts, municipalities)

ACTIVE since 2026-08-14, compile time

Copied verbatim from the research dataset; curl with browser UA, redirects followed, 403/000 bot-walls corroborated before "browser-ok". Statuses are data, never upgraded by UI.

PRODUCTION_DATA_PATHS.md §2d

Live Grants.gov connector (search2, fetchOpportunity)

ACTIVE since 2026-08-18

Browser direct to api.grants.gov, no key, CORS verified. Loud ErrorPanel on failure; typed error classes.

PRODUCTION_DATA_PATHS.md §2c grants

Multi-state live paths (all /tx/* surfaces, TX counties, TX portals and sources)

ACTIVE since 2026-08-15

api.usaspending.gov with place_of_performance state "TX", curl-verified 200. TX assets from the same Census 2010 GeoJSON source as FL.

PRODUCTION_DATA_PATHS.md §5

New York live paths (all /ny/* surfaces, NY counties, portals, sources, thresholds, regions)

ACTIVE since 2026-08-17

api.usaspending.gov with place_of_performance state "NY", curl-verified 200. 62 counties from the same GeoJSON source; statutes browser-verified from nysenate.gov.

PRODUCTION_DATA_PATHS.md §6

Hero state map assets (fl/tx/ny-points.json, hero-florida-coast.svg)

ACTIVE, static derived

Generated from the plotly geojson-counties-fips.json dataset (US Census 2010 county boundaries), curl-verified. Geometry used as published, no simplification.

PRODUCTION_DATA_PATHS.md hero assets

SAM.gov opportunities

See Status page

The Cloudflare Worker calls the SAM.gov Get Opportunities API with a server-side SAM_API_KEY, normalizes notices, and stores current and immutable version rows in D1. The Status page reports current readiness and the last completed scan; daily scans cover recently posted notices within source request limits.

PRODUCTION_DATA_PATHS.md §4

Opt-in opportunity email alerts

See Status page

The Worker stores encrypted subscriber addresses in D1 and requires email verification. Matching is scheduled hourly; subscribers choose daily or weekly delivery. Due messages are checked every five minutes and sent through an outbox when delivery is configured. The Status page reports current readiness and processing outcomes.

PRODUCTION_DATA_PATHS.md §4

Data freshness automation

PARTIAL

Worker crons refresh SAM opportunity data and alert matching when configured. Curated-content retrievedAt dates remain hand-maintained, and county snapshots refresh during a production release.

PRODUCTION_DATA_PATHS.md §4

User accounts / saved searches

BLOCKED

No auth infrastructure exists.

PRODUCTION_DATA_PATHS.md §4

SBIR.gov, Data.gov CKAN, Socrata connectors

REJECTED, not browser-accessible

403/404/WAF-blocked or missing CORS from a real browser (tested 2026-08-18). Surfaces are link-only with explicit notices.

PRODUCTION_DATA_PATHS.md §2d rejected

What does not exist

Found something on this site that looks wrong? Tell the developer directly on the data freshness page . Confirmed errors get an entry in the register above.