TariffWatch Roadmap

TariffWatch exists because BIS Federal Register notice BIS-2026-15961 proposed 14 new Section 232 tariff categories with a public comment window (docket BIS-2026-0331) closing at 11:59 PM Eastern Time on Wednesday Aug 27, 2026, and a business's actual exposure across its HTS code portfolio is not something most import teams can calculate by hand before that window closes. This page tracks what has actually shipped toward solving that problem, what's actively being built, what's planned next once the comment window closes, and what's still just an idea. It is generated from a source file any future engineer or Andy himself can edit directly (`content/roadmap/tariffwatch/roadmap.mdx`), then rebuilt with `node scripts/build-roadmap.mjs` — nothing here is aspirational marketing copy. If a line is under "Shipped," it traces to a real commit in this repository's history, most of which are also visible in more granular form on the TariffWatch changelog.

• Aug 8 — Free Section 232 exposure checker + landing page live at /tariffwatch, built around Federal Register notice BIS-2026-15961 (14 new tariff categories, comment window BIS-2026-0331 closing 11:59 PM Eastern Time on Wednesday Aug 27, 2026).
• Aug 8 — Content features pass: countdown clock to the comment-window deadline, FAQ, sample-letters gallery, and Edge Config-gated pivot copy pre-staged for the day after the window closes.
• Aug 8–9 — BIS-14 dual-exposure rate-bug fix, five more BIS-14 sample comment letters, and a Playwright end-to-end test harness covering the exposure-checker flow.
• Aug 9 — Watch-list and attorney-match schema, identity-verification flow for comment-letter requests (domain-match check, free-email-provider flag, injection/suspicious-content flagging).
• Aug 9 — Comment-letter drafter cron (hourly) auto-drafts a regulations.gov-ready submission from a verified request's exposure data.
• Aug 9–10 — Hardening pass + Federal Register snapshot refresh cron (daily 5 AM UTC) keeping the exposure calculation current against the live docket.
• Aug 11 — JSON-LD schema, comparison pages against Descartes CustomsInfo and Gaia Dynamics, and a Section 232 glossary.
• Aug 13 — Public `/tariffwatch/status` status page, `/tariffwatch/changelog`, and the Meta Pixel Debugger/HTS Lookup/CPSC Penalty Calculator free-tool trio's TariffWatch-adjacent cross-links.
• Aug 13 — Cookie consent banner correctly gates PostHog/Sentry, EU visitors default to declined.
• Aug 14 — Hero headline A/B test wired via Edge Config — separate pre- and post-Aug-27 experiment ids so a copy variant chosen before the comment window closes can never accidentally render in the post-window state.
• Aug 14 — Daily retention cron anonymizes exposure-scan and comment-letter-request PII past the 30-day window `/tariffwatch/privacy` commits to (business name/context and letter body text specifically, not just the email).

• Post-Aug-27 pivot: the `pick3_post_aug27_pivot` Edge Config flag is pre-staged and tested; a scheduled task is set to flip it at Aug 28 2026 00:00 UTC, moving landing/checker copy from countdown urgency to ongoing-exposure framing.
• Weekly watch-list alert cron (`tariffwatch-watchlist-alert`, Tuesdays) notifying subscribers of docket changes — live, currently low-subscriber-volume while the checker itself is still the primary acquisition surface.

• A named credentialed reviewer (trade attorney or licensed customs broker) for substantive Section 232 analysis pages, per Standard v2 §16.3 — an open, tracked gap, not a fabricated claim.
• Formal regulations.gov API submission (currently one-click-assisted, not auto-submitted) once the identity-verification flow has enough real-world volume to justify the additional API integration risk.
• Formal GSC property verification for real impressions-based refresh/sunset triggers.

• Coverage of tariff categories beyond the current BIS-2026-15961 proposal if additional Section 232 actions follow the same pattern.
• A paid alert tier for customs brokers monitoring exposure across many client HTS code portfolios at once.

Every entry above is either a direct citation of a git commit in this repository, a currently-running scheduled job (verifiable in `vercel.json`'s `crons` array), or a plan explicitly labeled "Planned" or "Considering" so it can never be mistaken for something already live. There is no separate "roadmap team" maintaining a different source of truth than the code — the person or agent who ships a feature is the same one responsible for adding its line here, in the same pull request where practical. When that discipline slips (a shipped feature not yet reflected here), treat this page as lagging reality by at most a few days, not as authoritative marketing.

This page itself is not exempt from the honesty standard it describes: nothing under "Shipped" links to a feature that doesn't exist in production today, and nothing under "Planned" or "Considering" is described with more certainty than it deserves. If a competitor or a curious prospect is reading this specifically to gauge how seriously we take this product, that scrutiny is the point — a roadmap that only ever says "everything is great, more is coming" is not a roadmap, it's marketing copy wearing a roadmap's clothes, and this one is deliberately built not to be that.

*This roadmap is generated from `content/roadmap/tariffwatch/roadmap.mdx`, editable directly and rebuilt via `node scripts/build-roadmap.mjs`. Every "Shipped" line traces to a real commit in this repository's history.*