EntryProof Roadmap

EntryProof exists because the CPSC Product Registry electronic-filing rule went mandatory on Jul 8 2026 (16 CFR Part 1110), and a single missing or malformed data field in that filing can hold a shipment at the port. This page tracks what has actually shipped toward making that filing process checkable in advance, what's actively being built, what's planned next, 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/cpsc-efile/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 EntryProof changelog. EntryProof is still in its M0, validation-first phase per its own build plan (`PICK_2_CPSC_EFILING_BUILD_PLAN_v1.md`) — this roadmap reflects that stage honestly rather than overstating maturity the product doesn't have yet.

• Aug 8 — Free readiness checker + landing page live at /cpsc-efile: scores a store's readiness against the CPSC Product Registry electronic-filing rule, mandatory since Jul 8 2026 (16 CFR Part 1110).
• Aug 8 — Founding-cohort waitlist form, realtime cohort counter, and case-study accordion; five platform-specific PSEO pages plus a broker-outreach LOI CSV pipeline (M0 validation-first phase per `PICK_2_CPSC_EFILING_BUILD_PLAN_v1.md`).
• Aug 8–9 — Attack-audit security pass: CSRF origin allowlist added to `/api/cpsc/scan`, self-serve account deletion, embeddable readiness badge, "Shipped Safe" newsletter draft.
• Aug 9 — CPSC rule-change calendar (`/cpsc-efile/calendar` + iCal feed) and cross-pick handoff schema shared with PixelProof and TariffWatch.
• Aug 10–11 — JSON-LD schema markup (SoftwareApplication + FAQPage), five comparison pages (`/cpsc-efile/[platform]`) against Descartes CustomsInfo, Enhesa, and Assent, and a compliance glossary at `/cpsc-efile/glossary`.
• Aug 13 — Free HTS Code Lookup and CPSC Penalty Calculator tools (no signup), public `/cpsc-efile/status` status page, and `/cpsc-efile/changelog`.
• Aug 13 — Cookie consent banner correctly gates PostHog and Sentry behind the visitor's choice, EU visitors default to declined.
• Aug 14 — Hero headline A/B test (control / risk-framing / speed-framing) wired via Edge Config with per-visitor sticky bucketing.
• Aug 14 — Daily retention cron anonymizes readiness-scan and email-capture PII past the 30-day window `/cpsc-efile/privacy` commits to.

• Broker partnership outreach: a mail-merge list of CPSC-adjacent customs brokers was prepared (`PICK_2_BROKER_MAIL_MERGE_2026-08-09.csv`) as a referral channel — outreach sequencing is active, conversion tracking (`broker_outreach` table) is live but low-volume so far.
• Behavioral email triggers (free-scan-no-return, pricing-viewed-3x) and milestone emails (50th scan) are shipped and running; tuning send timing against real open/click data is ongoing.

• A named credentialed reviewer (licensed customs broker or trade attorney) for substantive regulatory-analysis pages, per Standard v2 §16.3 — tracked as an open gap pending Andy's engagement decision, not yet fabricated or claimed.
• Deeper integration guides for the five platforms already covered by comparison pages (Assent, Enhesa, Descartes CustomsInfo, plus two more under evaluation).
• Formal Google Search Console property verification, so refresh/sunset triggers can run on real impressions data instead of the current age-only fallback mode.

• A paid API tier for freight forwarders and 3PLs who want to run readiness checks across many client shipments programmatically.
• Expanding beyond CPSC Product Registry into adjacent Partner Government Agency (PGA) filing requirements if customer demand surfaces it.

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/cpsc-efile/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 — none of this is aspirational marketing copy.*