Diagnosis: Three Boundary Failures
Verified state, July 24, 2026. The TinyFish case-card issue from prior audits is resolved. TinyFish no longer sits in the homepage grid. It appears once, correctly, as a hero aside: "Currently building agentic platforms at TinyFish." The case grid holds five entries: Alibaba, Thermo Fisher, Red Cross, Equinox+, Allē. Homepage title reads "Design Leadership for High-Stakes Systems."
What has not been resolved:
- The private essay delivers ~35KB of HTML, including TinyFish pricing strategy and competitive analysis, before the password overlay fires.
- All five full case studies deliver complete content in the initial HTTP response before a
localStoragecheck redirects unauthorized browsers. - The homepage links the private essay from the Essays & Field Notes section.
Three boundary failures. Each one violates a named handoff from "Trust Is the New Interface."
I have watched enough hiring panels evaluate senior design candidates to say this with high confidence: a security-minded reviewer will not treat the essay and the portfolio as separate artifacts. They will treat the portfolio as the essay's proof environment. A candidate who publishes a framework about irreversible gates and builds a cosmetic gate around her most sensitive content has handed the panel a metaphor that works against her. Literally.
Failure 1: The Private Essay. Decision Gate violation.
The Decision Gate handoff in your framework says: give the human enough context for a real call, automate what can be verified, keep human authority where the outcome is irreversible.
The password overlay on what-do-you-count looks like a Decision Gate. Password field. Implied controlled access. But the server already shipped the full essay in the response body. The irreversible action (content delivery) happened before the gate rendered. The human decision (entering a password) fires after the system already acted on the assumption that everyone is authorized.
The gate controls nothing. The outcome it appears to govern already occurred.
The content behind this gate is the most boundary-sensitive material on the site. TinyFish launch meetings with the CEO and CPO. Competitive pricing comparisons across agent frameworks. Cost-model construction. Tier-naming rationale. The portfolio boundary rule classifies all of this as internal-only evidence.
Your framework describes irreversible decision gates. You built a reversible one around the content that needed the strongest gate on the site.
Failure 2: Five Full Cases. Intent-Setting violation.
Intent-Setting in your framework: structured intake where interpretation is confirmed and success is defined before execution starts. Ambiguous input interpreted as precise causes the agent to act confidently on the wrong thing.
When a browser requests cs-01-alibaba.html, the server receives an HTTP request with no authorization signal. It cannot distinguish a hiring manager you gave the password to from a competitor, a scraper, or a casual visitor. The server's response to this ambiguous input: deliver the full case. Process images, outcome metrics, strategic narrative. Then, after delivery, a client-side script checks localStorage for a key that would indicate prior authorization.
Ambiguous intent interpreted as authorized intent. Confident action on that interpretation. Across all five cases, identical pattern. Thermo Fisher delivers 214KB. Red Cross delivers 249KB. Allē delivers 254KB. (Byte counts from live fetches, today's date.) Partner adoption rates, margin opportunities, disbursement figures, CAC reductions. Available to anyone who views source or disables JavaScript.
The framework says confirm interpretation before execution. The portfolio executes before confirming anything.
Failure 3: The Homepage Link. Loop Feedback violation.
Loop Feedback in your framework: the transition where output from one loop becomes input for the next. Small errors compound into wrong strategy when the feedback path is undesigned.
The portfolio runs two loops. Public loop: homepage, teasers, the Trust essay, leadership framing. Private loop: full cases, the private essay, TinyFish product evidence, interview-only context. The boundary rule exists because the evidence appropriate for each audience is different and the risk profile of exposure is different.
The homepage links the private essay from the Essays & Field Notes section. Internal-only evidence feeds directly into the public loop. A hiring manager browsing the homepage clicks the link, encounters the password overlay, views source out of curiosity or habit, and receives content that was never meant to shape their pre-interview evaluation.
This compounds both prior failures, and the Loop Feedback framing makes the cost precise. The output of one evaluation cycle (browsing the public portfolio) becomes uncontrolled input for the next (forming pre-interview judgments about TinyFish pricing, competitive positioning, internal decision-making). You have no way to correct the interpretation because you don't know it happened. No correction mechanism. No designed feedback path. No ability to reframe. Each subsequent interaction builds on a foundation you didn't lay and can't see.
Small errors compounding into wrong strategy. Your essay's own warning, playing out on your own site.
The root cause across all three. The portfolio treats access control as a client-side UX pattern rather than a server-side trust architecture. The essay argues that trust is built through designed handoffs where the system proves reliability at each transition. The portfolio's transitions are cosmetic. The content is already on the client. The gates are JavaScript overlays. The boundary between public and private evidence is enforced by a localStorage key that any technically literate reviewer can bypass, or that any curl request ignores entirely.
I flagged the private essay gate as a P0 in issue #3. Still P0. The five full cases are a P1 that has not moved. The homepage link compounds both.
The Trust essay has gotten stronger since then. It is the best thing on the site. Which makes the counterexample more expensive every week it stays live.