Juno Chen — Design Context File v1
One question governs every field in this file: what can a machine cite, what is off-limits, and which proof point maps to which buyer? Twelve companies. Two positioning frames with hard switching rules. Five case studies carrying cover-letter-ready proof blocks. Three active portfolio boundary violations that determine what gets linked and what doesn't. This is Juno Chen's canonical context file. The positioning layer between her background and whatever AI system turns it into a specific document for a specific company this week.
Juno Chen — Design Context File v1
One question governs every field in this file: what can a machine cite, what is off-limits, and which proof point maps to which buyer? Twelve companies. Two positioning frames with hard switching rules. Five case studies carrying cover-letter-ready proof blocks. Three active portfolio boundary violations that determine what gets linked and what doesn't. This is Juno Chen's canonical context file. The positioning layer between her background and whatever AI system turns it into a specific document for a specific company this week.
Four Act-Tier Positioning Sheets — Amplitude, Ramp, Brex, Maven
The positioning mistake I see most at Director+ level is obvious once you name it: leading with the same proof everywhere because it's your best work. It is your best work. But four buyers have four problems, and the candidate who opens with a regulated-environment case study at a company where designers ship PRs has already lost the room before the portfolio review starts. This issue assigns one lead proof per company — Amplitude, Ramp, Brex, Maven — no overlap. Each pairing comes from what the posting actually says when you read the verbs, not the title. Open the sheet for whichever company you're writing to this week.
Four Act-Tier Positioning Sheets — Amplitude, Ramp, Brex, Maven
The positioning mistake I see most at Director+ level is obvious once you name it: leading with the same proof everywhere because it's your best work. It is your best work. But four buyers have four problems, and the candidate who opens with a regulated-environment case study at a company where designers ship PRs has already lost the room before the portfolio review starts. This issue assigns one lead proof per company — Amplitude, Ramp, Brex, Maven — no overlap. Each pairing comes from what the posting actually says when you read the verbs, not the title. Open the sheet for whichever company you're writing to this week.
Fix the Surface Before You Build on It
Your site still ships the private essay in full to anyone who clicks the homepage card. The TinyFish case study card is still visible, treating product work as portfolio proof against your own published boundary. Both were P0 in issue #3. Both are still wrong. Below the fixes: a gap analysis against your current Act/Watch tier, a ranked build queue, and complete first drafts of the top three artifacts, starting with the AI-native design process essay that eleven of thirteen target roles are screening for. The essay is ready to publish. The surface it sits on is not.
Fix the Surface Before You Build on It
Your site still ships the private essay in full to anyone who clicks the homepage card. The TinyFish case study card is still visible, treating product work as portfolio proof against your own published boundary. Both were P0 in issue #3. Both are still wrong. Below the fixes: a gap analysis against your current Act/Watch tier, a ranked build queue, and complete first drafts of the top three artifacts, starting with the AI-native design process essay that eleven of thirteen target roles are screening for. The essay is ready to publish. The surface it sits on is not.
The Buyer-Angle Map (Trust-Sensitivity Axis Edition)
A CPO is judging whether you reduce their cognitive load. An engineering leader at an AI-native company is judging whether you've actually built in the medium. A design VP is reading your portfolio construction as a craft artifact. Same candidate. Five rooms. Five completely different failure modes for your portfolio boundaries.
Pull this up before every portfolio review. Which pillar leads, which supports, which stays in reserve. And how much it costs you if this particular buyer inspects what your site actually delivers versus what you say in the room.
The Buyer-Angle Map (Trust-Sensitivity Axis Edition)
A CPO is judging whether you reduce their cognitive load. An engineering leader at an AI-native company is judging whether you've actually built in the medium. A design VP is reading your portfolio construction as a craft artifact. Same candidate. Five rooms. Five completely different failure modes for your portfolio boundaries.
Pull this up before every portfolio review. Which pillar leads, which supports, which stays in reserve. And how much it costs you if this particular buyer inspects what your site actually delivers versus what you say in the room.
Said vs. Shipped — Eight Agentic AI Design Patterns and Who Actually Built Them
Every company building agentic AI products says "trust." The word has converged so completely across launch posts and keynote decks that it no longer tells you anything about the product. So I stopped reading the blog posts and read the interfaces instead. Eight shipped products. Eight design patterns. Some products place human gates exactly where consequences become irreversible. Others default to opacity because it is cheaper to build. One company puts its best visibility surface behind the enterprise paywall, which tells you everything about what they actually value. Names named throughout.
Said vs. Shipped — Eight Agentic AI Design Patterns and Who Actually Built Them
Every company building agentic AI products says "trust." The word has converged so completely across launch posts and keynote decks that it no longer tells you anything about the product. So I stopped reading the blog posts and read the interfaces instead. Eight shipped products. Eight design patterns. Some products place human gates exactly where consequences become irreversible. Others default to opacity because it is cheaper to build. One company puts its best visibility surface behind the enterprise paywall, which tells you everything about what they actually value. Names named throughout.
Vanta Head of Design — Your Thesis Is Their Product Problem
Vanta crossed $300M ARR in April. An IPO-prep CFO started 45 days ago. The Head of Design posting names agentic UX patterns across a 40-person org. Rubric score: 27 combined. Act Now.
But the score is not why this is first in the queue. Every product surface Vanta is building — Custom Agents, QAuto, Contract Gap Analysis — terminates on a human who has to decide whether to trust what an agent found. That is not adjacent to your Trust essay. It is your thesis, mapped one-to-one across five handoffs and five product surfaces. Outreach package is ready to send Monday.
Vanta Head of Design — Your Thesis Is Their Product Problem
Vanta crossed $300M ARR in April. An IPO-prep CFO started 45 days ago. The Head of Design posting names agentic UX patterns across a 40-person org. Rubric score: 27 combined. Act Now.
But the score is not why this is first in the queue. Every product surface Vanta is building — Custom Agents, QAuto, Contract Gap Analysis — terminates on a human who has to decide whether to trust what an agent found. That is not adjacent to your Trust essay. It is your thesis, mapped one-to-one across five handoffs and five product surfaces. Outreach package is ready to send Monday.
Portfolio as Trust Product
Trust Calibration Starts at Home
Juno's Trust essay argues that trust is built through designed handoffs where the system proves reliability at each transition. Her portfolio has three handoffs where the system proves the opposite. The private essay ships full HTML before the password fires. All five cases deliver content before checking authorization. The homepage links internal-only evidence into the public loop. Each failure maps to a named handoff from her own framework. A hiring panel will read the portfolio as the essay's proof environment. Right now, it proves the wrong thing.
Architecture: Watch → Verify → Delegate
Piece 1 identified three boundary failures. This piece asks whether the portfolio's surfaces do their jobs once those failures are fixed. Four of five teasers earn the next click. Equinox+ doesn't. But the deeper problem is the gating architecture: when full cases deliver complete HTML before checking authorization, you lose the touchpoint where a hiring manager requests access and you choose what to show them. Here is the architectural prescription.
