Juno Chen — Design Context File v1

File date: July 24, 2026 Purpose: Canonical positioning reference for AI-assisted generation of outreach, cover letters, and interview prep across 12 active-cycle companies. Governing rule: Every field is deterministic. Any surface marked compromised in Trust Boundaries must be flagged wherever it appears downstream. Consumption note: This is a data file, not an article. Terse fields. Consistent schemas. If a machine reads only the first three lines of any section, those three lines should govern behavior.

Identity and Positioning Core

Name: Juno Chen Current role: Co-founder & Head of Design, TinyFish (AI productivity tools, 0→1 PLG) Seniority band: Director+ / Head of Design / VP Design Core positioning sentence: Juno designs the operating contract between humans and complex systems — what the system reveals while acting, where humans keep authority, what exceptions surface, what can be reversed, and what evidence carries into the next loop. Repeatable capability: Making complex, high-stakes systems legible and trustworthy at the moment a human must act on system output.

Frame-Switching Rules

Two frames. The buyer's product problem determines which one leads. Not a stylistic preference. Not a mood. Deterministic.

INTELLIGENCE LAYER frame

• Trigger: The buyer's product converts data, signals, telemetry, compliance evidence, or market activity into a decision surface. Humans decide whether to act.
• Lead companies: Amplitude, Babylist, Render.
• Lead proof: Trust essay → Agentic Labs (Brand Pulse, Retail Velocity) → Alibaba.
• Lead vocabulary: Legibility, surfaced insight, decision surface, signal-to-action, inspection.

AGENTIC PRODUCTS frame

• Trigger: The buyer's product delegates action. Agents, copilots, automation, memory, review, correction, approval, reversibility, auditability.
• Lead companies: Vanta, Ramp, Brex, CodeRabbit, Headway, Rubrik, Capital One, Ambience, Maven.
• Lead proof: Trust essay → Agentic Labs (Carrier IQ, Brand Pulse) → Thermo Fisher or Red Cross depending on regulated vs. commercial context.
• Lead vocabulary: Governance, delegation, human authority, decision gates, reversibility, auditability.

HYBRID OVERRIDES

When both frames apply, lead with the company's local failure mode.

• Capital One: Enterprise design-org transformation is the lead. Trust essay + Agentic Labs before scale proof.
• Regulated workflow (Headway, Maven, Ambience): Consequence, exceptions, verification, billing, auditability, escalation. Essay and Agentic Labs are the method layer, not the lead.
• Finance-agent (Ramp, Brex): Commercial-system trust + builder fluency. Not regulated-compliance framing.

Buyer Anxiety Archetypes

Four archetypes. The same surface question from a hiring panel masks a different fear underneath. Diagnose the fear before you select evidence.

1. Speed — "She'll import enterprise drag." The buyer fears process, not output. Counter with timeline proof. TinyFish velocity as context.
2. Technical depth — "Her AI work is decorative." The buyer fears the candidate designed interfaces for AI rather than built in the medium. Counter with Agentic Labs (real APIs), architecture decisions, "built" language.
3. Function-building — "She can't build an org." Two subcategories: traditional (headcount, ladders, calibrations) and emerging (operating-model design for AI workflows). Counter with Red Cross 6→1 system consolidation, Thermo Fisher multi-partner coordination.
4. Seniority fit — Splits into overqualified fear ("she'll be bored / political") and misleveled fear ("she hasn't operated at this altitude"). Counter with scope-matched metrics. Thermo Fisher serves both ends.

Case study entries below tag which anxieties each case serves.

Case Study Proof Blocks

Identical schema per case. Proof block field is cover-letter-ready language. Use verbatim.

⚠️ All five full case pages are compromised (V3). HTML delivers before the access gate fires. Do not link to full case URLs in any generated content. Reference case teasers or proof blocks only.

Internal-reference links (tagged [prior audit]) are editorial context for this file's logic. Do not surface them in generated outreach.

CS-01: Alibaba.com

• Role: Head of Design & Research, North America
• Mandate: B2B procurement platform site refresh — $50B+ GMV, 200K+ suppliers, 25M+ desktop sessions
• Timeline: 2024
• Key metrics: +7% DAU · +20% daily transactions · +47% new visitors from search · +2.2pt NPS · −47% buyer-reported security concerns
• Proof block: At Alibaba.com, I led North America design and research for a $50B+ GMV B2B procurement platform serving 200K+ suppliers and 25M+ desktop sessions, diagnosing that 25% of traffic generated 80% of transaction value while high-value buyers lacked procurement-grade trust signals. I built the research case from 32 interviews, a Baymard audit, and gaze tracking, then led three sprints across homepage, search, and PDP trust architecture. The redesign produced +7% DAU, +20% daily transactions, +47% new visitors from search, +2.2pt NPS, and a 47% reduction in buyer-reported security concerns.
• Best for: Intent-Setting handoff proof. Trust architecture at scale. Mandate creation, not UX improvement. [prior audit — internal reference only]
• Buyer anxieties served: Speed (three sprints). Technical depth (Baymard + gaze tracking). Seniority (scale).

CS-02: Thermo Fisher — mySupply

• Role: Product Design Director
• Mandate: 0→1 digital supply-chain platform for pharma manufacturing — 6 partners, 9 sites, EU/NA/AU
• Timeline: 12 months
• Key metrics: $20M+ margin recovered annually · 83% IRR · 6/6 pharma partners committed · 42% overhead reduction
• Proof block: At Thermo Fisher, I designed mySupply as a 0→1 digital supply-chain platform for six pharma partners across nine manufacturing sites, replacing spreadsheet and phone-based coordination with one shared operating system. I translated 32 interviews into five modules: exception-first orders, batch transparency, bidirectional KPIs, structured forecasts, and an 18-month capacity heatmap. The platform recovered $20M+ margin annually, achieved 83% IRR, secured 6/6 pharma partner commitments, and reduced overhead by 42%.
• Best for: Decision Gate handoff proof. Regulated 0→1. The Swiss Army case — it serves all four buyer anxiety archetypes. Speed: 12-month build. Technical depth: five-module architecture. Function-building: multi-partner coordination. Seniority: $20M margin impact.
• Buyer anxieties served: All four.

CS-03: American Red Cross

• Role: Product Design Director / GM
• Mandate: 0→1 disaster-relief platform replacing 6 legacy systems — national deployment in 6 months
• Timeline: 6 months
• Key metrics: $847K disbursed across active events · 6 system switches eliminated · 1,689+ cases in first 2 weeks
• Proof block: At the American Red Cross, I led design and delivery of a 0→1 disaster-relief platform that replaced six disconnected tools with one shared case record across intake, casework, eligibility, payments, finance, and program command workflows. The platform was built for federal disaster conditions, untrained surge volunteers, slow networks, FEMA documentation, and 10x volume without retraining. It went from zero to national deployment in six months, disbursed $847K across active events, eliminated six system switches, and processed 1,689+ cases in the first two weeks.
• Best for: Decision Gate handoff proof (eligibility, disbursement, federal audit gates). Speed under constraint. Regulated high-stakes environments.
• Buyer anxieties served: Speed (6-month national deploy). Function-building (6 systems → 1). Seniority (GM scope).

CS-04: Equinox+

• Role: Product Design Director
• Mandate: 0→MVP digital fitness platform — 5 brands, iOS/Android
• Timeline: 3 months to MVP
• Key metrics: 600K premium members · 4.8-star App Store rating at launch · 0→MVP in 3 months
• Proof block: At Equinox+, I led product design for a five-brand digital fitness platform serving 600K premium members, with a team of four designers, one researcher, PM, engineering, brand, data, and BCG Design Ventures partners. I owned IA, cross-brand navigation, design system, and token architecture while sequencing MVP scope under a three-month launch constraint. The platform launched with a 4.8-star App Store rating across SoulCycle, Equinox, Pure Yoga, and post-MVP brand expansion.
• Best for: Speed proof. Design-system architecture. Multi-brand coherence.
• Buyer anxieties served: Speed (3-month MVP). Technical depth (token architecture, design system).

CS-05: Allē (Allergan / AbbVie)

• Role: Product Design Director
• Mandate: Dual-surface loyalty redesign — consumer iOS + provider web backoffice
• Key metrics: 30M+ members · 40K+ provider practices · 3.2x redemption · 47% lapsed reactivation · $42 CAC (down from $92)
• Proof block: At Allē, I led product design for a dual-surface loyalty redesign across a consumer iOS app and provider web backoffice for 30M+ members and 40K+ provider practices. I reframed loyalty in medical aesthetics as a trust and relationship problem, redesigning consumer milestones, care plans, treatment evidence, provider urgency sorting, checkout context, and provider-voice campaigns. The redesign produced 3.2x redemption, 47% lapsed reactivation, and reduced CAC from $92 to $42.
• Best for: Two-sided platform proof. Healthcare-adjacent, not clinical-regulatory. Consumer + provider trust. [prior audit — internal reference only]
• Buyer anxieties served: Technical depth (dual-surface). Seniority (30M+ members, $50 CAC reduction).

Trust Essay Handoff Mapping

Source: Trust Is the New Interface (June 2026, public). The argument: agentic systems moved the design problem from deterministic paths to probabilistic trust. Accuracy belongs to the model. Consistency is delivered by design. Trust ladder: Watch → Verify → Delegate.

⚠️ Portfolio cases referenced below are compromised (V3). When generating content from this table, cite proof blocks or case teasers. Do not link to full case URLs.

Positioning Rules

1. Lead with the buyer's problem. The opening sentence of any outreach names what the company is trying to solve. Juno's background is evidence, not the lead.
2. The commitment point is the universal hook. Every company has a specific moment where a human decides whether to trust system output. Name that moment. Per-company entries below specify each one.
3. Vocabulary convergence is the strongest differentiator. When a company's product language independently arrives at Juno's published framework language, that convergence should lead. No other candidate can claim it.
4. Mechanism language beats explanation. Use: visibility, escalation, reversibility, auditability, attribution, decision gates, human authority. Never: "I believe in human-centered AI."
5. Every candidate at this level has a strong background. The differentiator is how precisely you map what you've done to what this company needs this week.
6. Never claim regulated-compliance proof from Allē. Healthcare-adjacent. Not clinical-regulatory.
7. Never lead with scale narrative for AI-native companies. They want velocity and builder fluency.

Trust Boundaries

Placed here because everything below depends on what is actually visible, linkable, and citable.

Access levels:

• 🟢 Public — freely citable, linkable
• 🟡 Client-side gated — HTML delivers before access check; treat as public for risk purposes
• 🔴 Verbal-only — reference in conversation, never in written materials
• ⛔ Prohibited — do not reference in any context

Three Active Violations

V1 — TinyFish case card exposed on homepage. A buyer scanning the homepage sees TinyFish sitting alongside portfolio cases. That directly contradicts the hard rule: TinyFish is context, never proof. No remediation plan confirmed as of file date.

V2 — Private essay accessible and linked from homepage. "What Do You Count When the Playbook Doesn't Exist?" is intended verbal-only but reachable via homepage link. Client-side gating does not prevent content delivery. No remediation plan confirmed as of file date.

V3 — Full case studies deliver HTML before access check. All five full case pages return HTTP 200 with content before pf_access_v1 fires. Any buyer, recruiter, or crawler reads full case content without restriction. No remediation plan confirmed as of file date.

Gap Artifacts

Ranked by frequency of need across Act and Watch companies.

Every gap item is pending with no confirmed start as of file date.

Built artifacts with URLs:

• Trust Is the New Interface — public essay
• Brand Pulse — Agentic Labs demo (In-Progress + Loop Feedback handoffs)
• Retail Velocity — Agentic Labs demo (In-Progress + Loop Feedback handoffs)
• Carrier IQ — Agentic Labs demo (Output Review handoff)

Recommended sequence: Fix boundary violations V1–V3 → ship AI-native process essay → build Decision Gate demo. No evidence any step has started.

TinyFish and Agentic Labs

TinyFish

What it is: Juno's current company. Co-founder & Head of Design. AI productivity startup. 0→1 PLG. What it proves: Currency. Speed. Builder fluency from inside product. For CPO buyers specifically: TinyFish velocity (3 products, 3 months) proves speed from inside product, not from a design silo.

Agentic Labs

What they are: Enterprise demos built with real APIs. Not shipped products. Canonical external-use set: Brand Pulse, Retail Velocity, Carrier IQ. Three only. Permitted framing: "Enterprise demos with real APIs" or "functional prototypes built on live data." Never "products." Never "shipped work." Creator Scout and UAT Sentinel: Both visible on homepage. Neither in canonical set. Do not cite until boundary is revised. Handoff mapping: Brand Pulse + Retail Velocity → In-Progress and Loop Feedback. Carrier IQ → Output Review.

Per-Company Positioning

⚠️ Full case pages compromised (V3). Every matching-case reference below should cite proof blocks or case teasers in generated content. Do not link to full case URLs.

Consistent schema per entry. Current signal grounds positioning in public intelligence or states its absence. Act tier entries are outreach-ready. Watch tier entries carry a Readiness field.

Act Tier

Outreach this cycle.

AMPLITUDE

• Current signal (July 24, 2026): Head of Product Design posting live in San Francisco. Fifteen-person design team spanning Core Amplitude, Statsig, and Wave. CPO arrived April 14, 2026. Posting appeared by July 24. Between those dates: Statsig integration and Wave launch. The posting's scope mirrors those product events. Read the negation language: "not an executive who manages up and delegates down, not design ops, not the approval committee." That negation tells you what went wrong before. No design recruiter posting. No IC design cluster alongside. The CPO wants the leader first and will let them build. Title reads Head of Product Design under a CPO who owns PM, design, and growth. Read the scope and reporting line, not the title.
• Design problem: Machine-surfaced product opportunities (Wave) need a decision surface where teams decide whether to act. Intelligence-layer problem.
• Frame: Intelligence layer.
• Matching case: Alibaba (trust architecture for high-stakes decisions on system-surfaced data) + Brand Pulse (live signal inspection).
• Key metric: +20% daily transactions, −47% buyer-reported security concerns.
• Differentiation: Juno's Trust essay vocabulary ("decision gate," "intent-setting") independently mirrors Amplitude's product language around Wave Opportunities. No other candidate can claim that convergence.
• Opening hook: Name the commitment point: the moment a product team decides whether to act on a Wave-surfaced opportunity. That moment is a design problem, not a data problem.
• Do NOT lead with: Enterprise scale narrative. Agentic products frame. Team-building language. The posting's negation signals tell you they want a builder who leads through craft, not an org-chart executive.

VANTA

• Current signal (July 24, 2026): Head of Design role live, remote U.S., $365K–$513K cash with equity. Leads a ~40-person org across GRC, Trust, Platform, Self-serve, and AI. Posting names agentic UX patterns, AI-native design practice, design-system ownership, definitions of done, launch review frameworks, and org-level AI fluency. July 2026 release notes show Custom Agents, Vanta Agent, scheduled prompts, QAuto automation, contract gap analysis, risk registers, and agentic compliance workflows shipping fast.
• Design problem: Compliance agents acting on behalf of security teams need governable workflows. Supervision, run visibility, auditability.
• Frame: Agentic products.
• Matching case: Thermo Fisher (regulated workflow with human gates) + Carrier IQ (confidence-scored output review).
• Key metric: 6/6 pharma partners committed, $20M+ margin recovered.
• Differentiation: Trust essay's Decision Gate handoff maps directly to compliance-agent approval surfaces. Loop Feedback maps to continuous compliance monitoring.
• Opening hook: Compliance agents that act without visible reasoning create audit risk. The design problem is making agent work governable before it ships.
• Do NOT lead with: Consumer product. Equinox+. Intelligence-layer frame.

RAMP

• Current signal (July 24, 2026): Director, Product Design role live in New York, $320K–$440K with equity. The posting says design now involves tools, agents, memory, shipping PRs, and changing the design process as new capabilities unlock. Q2 2026 product release frames finance AI as "velocity where you want it" and "control where you need it," with agents handling reconciliations, procurement, compliance checks, RFx generation, and AI token spend management.
• Design problem: Finance agents handling real money need commercial-system trust. Reversibility, attribution, human authority over consequential transactions.
• Frame: Agentic products (finance-agent hybrid override).
• Matching case: Thermo Fisher ($20M margin, exception-first architecture) + Red Cross (disbursement gates, federal audit).
• Key metric: $20M+ margin recovered, $847K disbursed with audit trail.
• Differentiation: Builder fluency (TinyFish velocity as context) + regulated-system trust proof. In-Progress and Decision Gate handoffs both apply.
• Opening hook: Name the moment a finance agent commits spend on behalf of a human. That commitment point is where trust lives or dies.
• Do NOT lead with: Consumer loyalty (Allē). Design system language. Anything that signals slow process.

BREX

• Current signal (July 24, 2026): Staff Product Designer, AI role live. Posting names agentic experiences at the heart of an intelligent finance platform. Describes designing how users delegate financial work to AI, supervise work in flight, review and correct outputs, and build trust in automation that touches money.
• Design problem: Finance agents, money-moving, trust at the transaction layer. Stronger Output Review emphasis than Ramp.
• Frame: Agentic products (finance-agent hybrid override).
• Matching case: Thermo Fisher + Carrier IQ (confidence-scored broker decisions).
• Key metric: $20M+ margin recovered, 83% IRR.
• Differentiation: Output Review handoff from Trust essay maps to expense-agent output surfaces.
• Opening hook: When an agent categorizes, approves, or flags a transaction, the human reviewing that output needs to detect wrongness in seconds. Design the detection surface.
• Do NOT lead with: B2B marketplace framing. Healthcare adjacency.

MAVEN

• Current signal (July 24, 2026): VP of Design role live in New York, reports to CPO. Leads product design, brand design, and user research. Posting names AI-native design, conversational interfaces, agent-driven workflows, and adaptive onboarding. Base $250K–$350K plus equity.
• Design problem: Clinical/health platform with provider and patient surfaces. Regulated workflow + multi-sided service design.
• Frame: Agentic products (regulated hybrid override).
• Matching case: Red Cross (high-stakes platform for untrained users under pressure) + Allē (dual-surface, provider + consumer).
• Key metric: 1,689+ cases in 2 weeks (Red Cross speed), 3.2x redemption (Allē engagement).
• Differentiation: Decision Gate handoff maps to clinical decision surfaces. Red Cross proves design for high-stakes, low-training environments.
• Opening hook: Lead with consequence. What happens when the system gets it wrong in a health context. Then prove you've designed for that pressure.
• Do NOT lead with: Enterprise supply chain. Intelligence-layer frame. TinyFish as proof.

Watch Tier

Prepare and monitor for trigger.

CAPITAL ONE · Readiness: High

• Current signal (July 24, 2026): Director, Product Design — AI in Experience Design role posted July 20, 2026. Sits in XD top-of-house team under SVP/CDO and senior leadership team. Owns roadmaps across AI tooling, AI-enabled design-process evolution, and AI-centric talent upskilling across Design. Names Claude, Gemini, Claude Code, Stately, XState, Windsurf as relevant tools. SF/NY pay $251K–$287K for Director, Design, with eligibility for incentive compensation.
• Design problem: Enterprise design-org transformation under AI. The design function itself needs a new operating model.
• Frame: Agentic products (Capital One hybrid override — lead with org transformation).
• Matching case: Trust essay + Agentic Labs first, then Alibaba and Thermo Fisher for scale.
• Key metric: Lead with Trust essay framework, not case metrics.
• Differentiation: Juno has both the thesis (essay) and the demos (Agentic Labs) showing how design works differently with AI. Most candidates bring one or neither.
• Opening hook: The design org's operating model is the product problem.
• Do NOT lead with: Individual case metrics. Consumer product.

HEADWAY · Readiness: High

• Current signal (July 24, 2026): Design Director, Provider Experience role live in San Francisco. Owns provider EHR experience across scheduling, documentation, session experience, and client engagement. A single provider session touches scheduling, telehealth, clinical documentation, outcome measurement, insurance verification, and billing. Names Claude, Cursor, MagicPatterns, Claude Code, and prototyping in code. Asks designers to reimagine provider workflows with AI at the center.
• Design problem: Mental health platform. Clinical billing, provider workflows, insurance verification. Regulated agentic workflows.
• Frame: Agentic products (regulated hybrid override).
• Matching case: Red Cross (eligibility + disbursement gates) + Allē (provider-side workflow).
• Key metric: $847K disbursed with audit trail, 6 systems → 1.
• Differentiation: Decision Gate handoff maps to clinical billing approval. Red Cross proves design under federal compliance.
• Opening hook: Consequence, exceptions, verification, billing, auditability. Essay and Labs are the method layer.
• Do NOT lead with: Consumer fitness. Intelligence-layer frame.

RUBRIK · Readiness: Medium

• Current signal (July 24, 2026): Director, Product Design role live in Palo Alto. Company frames itself around cyber resilience, AI, immutable backups, and ransomware defense. June 2026 AI launch describes autonomous actions as auditable, attributable, and reversible, with human review when an action cannot be undone.
• Design problem: Cyber recovery and data security. Agent-assisted threat response needs reversibility and human authority at the action layer.
• Frame: Agentic products.
• Matching case: Thermo Fisher (exception-first architecture, batch transparency) + Trust essay Decision Gate.
• Key metric: $20M+ margin recovered (high-stakes system design proof).
• Differentiation: Trust essay's reversibility and auditability language maps to cyber-recovery workflows.
• Opening hook: When a security agent quarantines or restores, the human authorizing that action needs visible reasoning and a path back. Build the path.
• Do NOT lead with: Consumer product. Loyalty metrics.

CODERABBIT · Readiness: Medium

• Current signal (July 24, 2026): Senior Product Designer role live. Posting frames the design problem plainly: does AI code review feel like noise or a trusted teammate? Names interaction patterns for real-time review, conversational feedback, agentic workflows, multi-surface design systems, and AI-generated insight legibility.
• Design problem: AI code review. Developer trust in automated suggestions. Output Review emphasis.
• Frame: Agentic products.
• Matching case: Carrier IQ (confidence-scored output for expert review) + Brand Pulse (in-progress visibility).
• Key metric: Lead with Agentic Labs demo fluency, not enterprise case metrics.
• Differentiation: "Built" not "designed." The verb-level screen matters here. TinyFish context proves builder fluency. Carrier IQ proves confidence-scored output design.
• Opening hook: A code suggestion an engineer can't evaluate in seconds gets ignored. Making wrongness detectable at review speed is what matters.
• Do NOT lead with: Enterprise scale. Regulated compliance. Team-building narrative.

AMBIENCE · Readiness: Medium

• Current signal (July 24, 2026): Staff Product Designer role live in San Francisco. Owns end-to-end UX across Clinical AI products. Platform covers real-time coding-aware documentation and clinical workflow support across ambulatory, emergency, and inpatient settings.
• Design problem: Clinical AI. Ambient documentation, clinical workflows, provider trust. Regulated agentic products.
• Frame: Agentic products (regulated hybrid override).
• Matching case: Red Cross (high-stakes, untrained users) + Thermo Fisher (regulated human gates).
• Key metric: 1,689+ cases in 2 weeks (speed under clinical-grade pressure).
• Differentiation: Decision Gate handoff maps to clinical documentation approval.
• Opening hook: When the system documents a patient encounter, the provider signing off needs to detect errors before they become part of the medical record. Design that detection moment.
• Do NOT lead with: Consumer product. B2B marketplace. Intelligence-layer frame.

RENDER · Readiness: Low

• Current signal (July 24, 2026): Staff Product Designer role live. Raised $100M Series C in February 2026, total funding $257M. Frames Render as a cloud platform for AI-native, full-stack, multi-service applications.
• Design problem: Developer platform. Infrastructure intelligence, deployment visibility. Intelligence-layer frame with agentic elements.
• Frame: Intelligence layer.
• Matching case: Brand Pulse (live signal monitoring, "what changed" prompts) + Alibaba (platform trust at scale).
• Key metric: +7% DAU, +47% new visitors from search.
• Differentiation: Loop Feedback handoff maps to deployment monitoring and drift detection.
• Opening hook: When a deploy fails at 2 AM, the developer needs the platform to surface what changed and why. Design that inspection surface.
• Do NOT lead with: Healthcare. Regulated compliance. Enterprise supply chain.

BABYLIST · Readiness: Low

• Current signal (July 24, 2026): Director, Product Design (AI Builder) role live. Owns Registry UX, vision, KPIs, craft standards, operating model, and transition to AI-native product development. Reports to VP, Head of Product Design and Research. Leads 3–4 product designers.
• Design problem: Commerce + content platform for parents. Intelligence-layer elements (recommendation, registry intelligence) with emerging AI features.
• Frame: Intelligence layer.
• Matching case: Allē (consumer loyalty + dual surface) + Alibaba (commerce trust architecture).
• Key metric: 3.2x redemption, 47% lapsed reactivation.
• Differentiation: Loop Feedback handoff maps to recommendation refinement over the parenting journey.
• Opening hook: Registry recommendations that don't learn from what parents actually bought, returned, or ignored erode trust over time. The feedback loop is where trust compounds or decays.
• Do NOT lead with: Enterprise B2B. Regulated clinical. Heavy agentic-agent language.

v1 · July 24, 2026 · Next update triggers: any boundary violation remediation, any gap artifact ships, any Watch company moves to Act, any new public signal changes a per-company entry.