Selected work / Professional Record
Career documentation · Portfolio engineering · AI-assisted authorship Working system
Turning a résumé into a governed record
The same career facts, held once, rendered seven different ways for seven different readers.
One record. Seven ways to read it.
A recruiter skimming for five minutes and a hiring committee reading closely need different documents. Usually that means two documents, drifting apart the moment one gets edited. This doesn't.
The problem
A career resume is usually one document trying to serve every reader at once, which means it serves the average reader well and everyone else poorly. A recruiter wants to scan in under a minute. A hiring committee wants the arc — what led to what. Someone deciding whether to trust a claim wants to know exactly how it's substantiated. Building three separate documents solves this once and breaks it on the next edit, when only one of the three gets updated.
My contribution
Content architecture and information design: separating the facts of the career (one file) from how each view presents them (seven independent renderers), so a single correction propagates everywhere automatically. Directed the AI-assisted build through iterative review, including the evidence-tier system described below.
Deliverables
- Seven independent, deep-linkable views over one data file
- An evidence-tier system replacing adjectives with provenance
- A retrieval-only Q&A panel — answers only from what's on the page, cites its source, invents nothing
- A résumé & cover-letter generator with live preview
- Static-first rendering — the default view is real HTML in the page source, readable without JavaScript
Process
Decisions that shaped it
One file of facts, seven renderers.
Every date, number and bullet lives in a single data file. Each view — Dossier, Narrative, Atlas, Flow, Map, Ledger, Studio — is a separate, independent way of rendering that same file. Correct a number once; all seven reflect it. Nothing is retyped per view, so nothing can drift out of sync with the others.
Replace adjectives with provenance.
Instead of describing an achievement as "significant" or "major," every substantive claim carries one of three tags: verified (a confirmed outcome), on record (an official appointment or documented responsibility), or in progress (ongoing work). A senior reader responds to provenance, not adjectives — this makes the distinction visible on every line rather than asserted once in an introduction.
Static first, so the record reads without a script.
The default Dossier view is pre-rendered into real HTML inside the page itself — a search engine, an AI crawler, or a browser with JavaScript disabled all see the complete record. The other six views build on top of that same page once JavaScript loads; nothing about the base document depends on script execution succeeding.
What the seven views actually are
The names are unfamiliar on purpose — each is doing something a plain resume can't. Here's what each one is for.
- Dossier — the default
- The complete governed record: numbered sections, dated appointments, and every claim carrying its evidence tier. Read this first if you're deciding whether to trust the rest.
- Narrative
- The same record read as a continuous story rather than a numbered document — for a reader who wants the arc of how one role led to the next, not a reference to consult.
- Atlas
- Linked notes, in the style of a personal knowledge base — for exploring how capabilities, roles and outcomes connect to each other, rather than reading top to bottom.
- Flow
- The career redrawn as a process diagram: what capability was carried forward from each role into the next, made visible as a shape rather than a paragraph.
- Map
- A radial diagram of how the different domains of work — governance, engineering, public administration, teaching — relate to and reinforce each other.
- Ledger
- Dense, scannable tables. Built for a reader who wants to compare figures quickly, or print a reference copy.
- Studio
- A working résumé and cover-letter generator — choose emphasis, length and register, get a formatted document with a live preview, ready to print or download. This is the one view meant to produce a takeaway document, not just be read.
Outcome
A single career record that a recruiter can skim in the Ledger, a hiring committee can read in full in the Dossier, and a candidate can turn into a tailored résumé in the Studio — all from one maintained source, with claims that state their own evidence tier instead of asking to be taken on faith.
Takeaway
The same discipline this whole site applies to institutional evidence — separate the fact from its presentation, and mark what's proven versus what's claimed — applied to a single career record instead of an accreditation return.
Honest limits
The Ask panel inside this record is retrieval-only — it answers strictly from the data file already on the page, with no external AI call and no cost. That's a deliberate, different design from the "Ask about my work" assistant on the main site, which does call a live language model. Both refuse to invent facts; they get there by different means.
What would come next
- Bring its evidence-tier vocabulary and this record fully into alignment with the main site's own honesty framing
- Cross-link specific Dossier sections directly from the case studies that reference the same facts