Case Study · JobFlow
The fail-closed pipeline, told end to end.
JobFlow is the studio's internal job-application engine. It has no public URL by design. This page is its record: what it does, what it refuses to do, and what it proves.
internal system
01 · The problem
Volume without overstatement
Applying for roles at volume creates pressure to inflate. JobFlow exists to remove that pressure structurally: every claim in every application package must survive a truth gate against a verified evidence map before it can ship.
02 · The constraint
Fail-closed by design
The system prefers producing nothing over producing something wrong. When a gate fails, the package stops. And it never auto-submits: a human reviews every package before anything leaves the pipeline.
03 · The pipeline
Seven stages, in order
Every run travels the same line, stop by stop. No stage is skipped, and the last stop is always a person.
Parse career sources
Roles come in from configured sources, not from guesses.
Crawl ATS boards
The pipeline reads the boards where the real postings live.
Score roles
Each role is scored for fit before any writing starts.
Snapshot JDs with content hashes
Every job description is frozen and hashed, so a package is always built against a verifiable copy.
Generate tailored packages
Materials are assembled per role from the canonical content bank.
Run machine QA gates
Deterministic checks catch overstatement, formatting failures, and claim drift.
Human review
Nothing is submitted by the machine. The final gate is a person.
04 · What shipped
An internal system in daily use
JobFlow runs on Python, Node, and SQLite, and it runs the studio's own applications. The role-specific builds on the projects page were produced through this pipeline; they are its living output.
05 · What it proves, and what it does not
The doctrine, in daily use
It proves the operating doctrine works when it matters: a deterministic core, explicit approval gates, and honest failure when a gate trips. It does not prove throughput, placement rates, or any other number. No metrics are published here because none are verified.
Next Stop
Where to from here
The rest of the work carries the same honest states.