A catalog engineers can argue with.

A single typed catalog module holds every product — family, band, cooled or uncooled, spec groups, comparison tables, range-chart data, and application markets. The catalog page grouping, the statically generated detail routes, the featured lineup on the homepage and in the footer, the sitemap, and the Product JSON-LD all derive from it. Adding a product is a data change, and the structured data can never drift from the page it describes.

• A typed catalog module is the content model
• Detail routes prerendered from the same array
• Sitemap and featured lineup generated, not maintained
• Product JSON-LD emitted from the rows the table renders

Cross-product consistency is what engineers actually notice, so the rules sit at the top of the catalog file as a checklist the next editor has to read past. Sensitivity is always labelled NEdT and always expressed with a less-than-or-equal, never a strict less-than. Radiometry gets a row on every product, valued or explicitly marked unavailable. The long-wave band is always stated as 8-14 µm. Altitude is always 12 km. Digital zoom is always phrased the same way, and the one core that has none says so outright.

• Rules live in the source, not in someone’s memory
• Uniform labels, units, and comparison operators
• Every product carries the same required rows
• Named exceptions instead of silent omissions

Every ECCN was researched and then triaged as confirmed, pending, or missing. Confirmed means multi-source or datasheet-in-print. Pending means single-sourced, or in conflict between sources. Missing means no source states one at all. Only confirmed codes are eligible to render; everything else degrades to “contact sales to confirm.” Each pending item is named in the source alongside the specific conflict, so reconciling it with the manufacturer has a worklist rather than a memory.

• confirmed · pending · missing, tracked per product
• Conflicts recorded with their competing sources
• Public cell degrades to a sales conversation
• Classification page built and parked until the codes clear

Next.js 16 App Router on React 19 with strict TypeScript, every route prerendered. Tailwind CSS v4 with the design tokens declared in a single theme block, so the instrument palette and the type scale are one file rather than a scatter of hex codes. Motion drives an instrument boot-up on load and restrained scroll reveals, all safe under prefers-reduced-motion. The only dynamic surface is the contact Server Action: Zod-validated, honeypot-guarded, provider-agnostic, and it surfaces a real error rather than pretending a lost message was delivered.

• Next.js 16 · React 19 · strict TypeScript
• Tailwind v4 tokens in one theme block · Archivo + IBM Plex
• Server Action + Zod + honeypot · no database
• robots.ts explicitly welcomes six AI crawlers

An export classification on a public page is a legal claim someone may rely on. Where sources conflicted, or a code was single-sourced, we withheld it rather than publish the likeliest answer — and shipped the classification page parked, not guessed, until the codes are reconciled with the manufacturer.

A catalog count reads as a boast and goes stale the moment the lineup changes, so the site never states one — not in copy, not in a stat block. The rule is written into the catalog file so a future edit cannot reintroduce it by accident. We have held to it in this case study too.

The same cores that serve defense programs also track marine mammals from survey vessels, map wildfires and agricultural health from orbit, and keep drivers on a road in blinding dust. Leading with what infrared does, rather than with what it can be aimed at, is both more accurate and a wider door.

Work that comes out of the design gets kept where it can come back. The spectrum map was pulled off the catalog page because it delayed people reaching the products, not because it was wrong — it stays in the repo for a future education page, alongside the classification table, each behind a route the framework ignores.