Projects

on-record

public record · live

What French deputies actually do, on the record, not what they say.

How French deputies actually vote, vote by vote. Every public vote of the Assemblée nationale, explained in plain French for readers who never followed a session, each figure traced back to the official record.

  • TypeScript
  • React
  • Zod
  • GitHub Actions
  • Cloudflare Pages
  • Vitest
Drawing: one figure about a deputy, wired to the single ballot it counts, on a stack of official vote sheets where each row is a vote and each square a ballotASSEMBLÉE NATIONALEPUBLIC VOTESONE FIGURE · ONE DEPUTYFORwith the group of the dayOFFICIAL RECORDevery page cites its sourceEVERY FIGURElinks to the votes it countsNO RANKING, NO SCORE
Coverage
28%
lines run by the ingest, web and protocol tests, read 2026-10-02
House packages
11 of 11
installed from npm

At a glance

  • Every public vote of every deputy, with the group they sat in on the day of the vote. No ranking and no score: every figure links to the votes it counts, and every page cites its official source.
  • No server and no database: a nightly GitHub Actions job asks the Assemblée’s open data whether anything changed, rebuilds only what did and deploys. A night without a new vote downloads nothing and deploys nothing.
  • The host publishes 20,000 files per deployment, and there are over 8,000 votes: they ship in blocks, one file per deputy, small indexes for lists and search, and the build checks its whole output against a budget.
  • About 750 pages prerendered by the very loaders the browser runs, a fake fetch answering their data during the build, each with its own head tags and a place in the sitemap.
  • Find your deputy from your commune or your address, in French, light and dark.

How it works

no server, a nightly job asks what changed

GitHub ActionsCloudflare PagesDiagram: every night a GitHub Actions job asks the Assemblée’s open data whether anything changed; a new vote rebuilds only what changed and deploys to Cloudflare Pages, a quiet night downloads and deploys nothingNightlyOpen dataanything changed?new voteRebuildonly what changedDeployno new voteQuiet nightno download, no deploy20,000 files per deployment,8,000+ votes shipped in blocks,the output checked against a budget.

As the compiler reads it

Set the way an editor shows it: a wavy line is a build that refuses, a violet line is what the compiler works out on its own.

  1. source-version.ts
    Compiles0 errors
    export const isNewerVersion = ({
      cached,
      downloaded
    }: {
      cached: SourceValidators | null
      downloaded: SourceValidators
    }): boolean => {
      if (cached?.lastModified == null || downloaded.lastModified === null) {
        return true
      }
      return (
        Date.parse(downloaded.lastModified) >
        Date.parse(cached.lastModified)
      )
    }
    

House packages

11 of the 11 house packages, from npm, down to the compiler and linter settings.

Your team, perhaps?

I am looking for my next job. Write to me, or take the CV: a designed one, and a plain one for applicant tracking systems.