
Guide 05 · 106 pages · 19 chapters
The Portfolio Project Catalog
17 portfolio projects in three tiers, with specs, ship gates and interview stories.
By PixioLab
Included in the full program and the guide library. See the 45-day roadmap.
What's inside
- 01
How to choose your projects
Seventeen projects is a menu, not a to-do list. This chapter shows what makes a project count, how the projects depend on each other, which two or three fit the role you want, and how every project page is laid out.
What makes a project count · The catalog at a glance · How the projects connect · Suggested paths by target role · Pick two or three, and finish them · How each project page is laid out
- 02
Groundtruth
A retrieval evaluation harness that proves whether a change to a legal research assistant's search actually helped, measured on 150 human-reviewed queries and enforced in CI.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 03
Tripwire
A CI eval gate that fails any pull request whose prompt or model change makes a support-routing feature measurably worse, and stays quiet when nothing real changed.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 04
Warmstart
A three-layer cache (exact match, semantic match and the provider's prompt cache) for a support assistant answering 400,000 questions a month, with a measured false-hit rate and no cross-customer leaks.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 05
Sourcebook
Cited, hybrid-search answers over 4,000 internal docs for a 600-person company.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 06
Switchyard
An LLM gateway for six AI features: survives outages, bills every call to a team.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 07
Doorman
Layered injection defenses for a recruiting agent that reads 2,000 uploads a week.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 08
Querybound
A text-to-SQL analyst for 200 questions a day that cannot change a single row.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 09
Intake
Extraction with per-field provenance and review for 15,000 invoices a month.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 10
Plumbline
An LLM judge for a docs assistant, calibrated on 200 human labels and gated in CI.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 11
Docdrift
A GitHub Action that flags docs a pull request made stale and suggests fixes.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 12
Casefile
A bounded multi-agent system that triages 900 auto-insurance claims a day, stops when it should, and never pays out without a human.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 13
Slotfill
Fine-tune vs prompt vs distill: decide, with field-level evidence, how to extract 40,000 freight invoices a month into a strict schema.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 14
Fieldnote
Multimodal RAG for 40 field-service technicians: answer questions whose evidence lives in a chart, a wiring diagram or a photo, and show the tech the cropped figure.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 15
Atlas
Knowledge-graph plus vector RAG over 40 companies' public filings, answering two- and three-hop questions with citations and benchmarked by hop count against plain vector RAG.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 16
Redline
An automated red-team harness that attacks your own P06 Doorman and P04 Sourcebook on every deploy, files findings with repros, and never lets a closed hole reopen.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 17
Flywheel
Turn production logs into failure forensics and new eval cases: find which pipeline step broke, then grow a human-verified golden dataset that the CI gate runs.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 18
Canary
A prompt registry with deterministic assignment, A/B tests that don't peek, and staged rollouts that advance only on non-inferiority and roll back on their own.
The scenario · What it proves · Architecture · Stack · Data · Build it, phase by phase · Measure it · Where it goes wrong · and 2 more
- 19
Packaging, statistics and reference
Everything the project pages share: how to package a finished repo, how to talk about it, how to write a resume line you can defend, the statistics behind every ship gate, a security checklist, the datasets index and the sources.
Packaging the work · Talking about projects in interviews · Resume-line rules · Statistics primer · Security checklist · Datasets index · Sources and further reading