Build architecture · v1 · 2 Jul 2026
One spine,
four surfaces,
one loop.
You don't have three inputs feeding one tool. You have a single shared signal store underneath, and every build is just a different view of it. Same data, three jobs: apply, learn, express — turned by one feedback loop.
01 The substrate
Sources write in. Surfaces read out.
Signals written in
market
open roles, JDs, keywords
interview
recordings → gaps, stories
ai-world
new models, discourse
stories
work history, master resume
Signal store
The shared spine. Everything above is written here; everything below reads from here. The plumbing, not the product.
Surfaces reading out
UptakeScan + deliver
Runs the daily scan and ingests AI-world news. The engine that keeps everything timely.
also writes back → straddles source + surface
Resume toolApply
Market signals + story corpus → a resume tailored per role off the master. Also hosts the Interview Agent — the loop's signal generator, working off real call recordings (ground truth, not simulation). Classifies the call & emits gaps.
reads: market · stories · writes: interview
Agent AcademyLearn
Interview gaps + market + AI-news → a chapter that closes the hole. Built on Leslie & Arman's vocab. Read-only — it consumes signal, never writes it.
reads: interview · market · ai-world
Ask BlakeExpress
Story corpus → conversation. Your portfolio as an agent of you — the front door people talk to. Not the interviewer; a pure read of the corpus.
reads: stories
02 The crown jewel
The loop is the product. Everything else is plumbing that makes it turn.
- 1
A gap appears. The Interview Agent analyzes a real call recording, classifies the stage, and exposes a topic you fumbled — "couldn't answer chunking."
- 2
Academy writes the chapter. Gap detected → auto-authored lesson: what it is, why it matters, how teams use it.
- 3
You learn it. The lesson lands in the curriculum, ramped to your level.
- 4
The Interview Agent lets you rehearse. Practice it out loud in the resume tool's Interview Agent — graded good / bad / different against ground truth, not a simulation.
- 5
Next time you nail it. A better story enters the corpus — the resume tool draws on it, and Ask Blake tells it to recruiters.
closed loop — pointed at one goal: get good at agents, get hired
03 Two corrections
One untangle to make, one trap to avoid.
Untangle
Uptake is doing two jobs
It's a content source (new model → discourse) and the scan engine (job search that makes everything timely). Bundling them is what makes the diagram feel circular.
Split them: Uptake = daily scan/cron + a news feed riding on it. Resume tool and Academy subscribe to the scan; Academy also subscribes to the feed.
Caution
Gap-driven, not calendar-driven
"A chapter almost every day" should be triggered by a real gap or market signal, not a quota. A chapter-a-day for its own sake produces filler and drops the signal-to-noise.
Let the daily cron be how often you check — let cadence be an output of how much you're interviewing and scanning.