GrantPipe

The decision

One test failed the build if a retired federal dollar threshold appeared anywhere in the repository. The federal single-audit threshold changed under a 2024 OMB revision. Compliance software’s worst failure mode is a number that used to be right, and a compiler has no opinion about prose.

apps/site/src/audit-threshold-amount.test.ts shelled out to git grep across every tracked file, hunting for the retired figure and failing the build if it reappeared in code, docs, or any of the 1,526 marketing content entries.

The retired figure was never written in the test’s own source; it was reassembled from string fragments at runtime specifically so the test could not match itself, and an allowlist covered the two explainer videos that legitimately taught the before-and-after contrast.

The other half of the same practice was that federal thresholds were stored as data with a citation and an effective date rather than inlined as literals, so a value and its provenance moved together instead of drifting apart.

The same instinct guarded the marketing copy. A test in apps/site reads the product page’s own source and fails the build if strings like “Trusted by,” “customer logo,” or “testimonial” show up anywhere in it, the same build-fails-on-a-false-claim discipline applied to the copy a reader sees first rather than to a compliance figure buried in the product.

Architecture

Three deployables shared one type system: an Astro 6 marketing site, a React 19 SPA, and a Hono API on Cloudflare Workers. The API exported its router type, so the client’s hc<AppType>() call failed to compile the moment a route’s shape changed: no OpenAPI document, no generated SDK, no sync step that could drift. Each of the 37 API domains owned its own routes.ts and service.ts, so a change to how grants worked stayed inside the grants domain.

Beyond request and response, the platform used Cloudflare Queues for async award-letter intake, Durable Objects for coordination, R2 for documents, D1 for marketing data, KV for auth rate limiting, Hyperdrive for Postgres pooling with query caching explicitly disabled, Browser Rendering for server-side PDF generation, and cron triggers for 17 scheduled jobs.