An anthropological reading of the creative world FC is selling into. Maps the mythology of the golden age, heroic archetypes (the deep cuts — Leiter, Marker, Martin, Shuggie Otis), symbolic objects, sacred places, rituals, the moral code of the industry, and the central taboo that makes AI dangerous territory. Concludes with the cultural transformation FC offers: taste is what remains.

5.1 The Founder System

5.1.1 "You didn't assemble like a team. You assembled like a system."

• 5.1.1.1 Conor — external momentum (rooms, relationships, narrative, urgency)
• 5.1.1.2 Polina — directional coherence (meaning, product integrity, "what we are and aren't")
• 5.1.1.3 Marin — reality and buildability (first-principles, shipped artefact, pragmatism)

5.1.2 This loop is why they out-ship larger teams. Failure mode is imbalance, not conflict: Conor = sole commercial engine (burnout), Polina = all emotional load (quiet resentment), Marin = silent bottleneck (invisible complexity).

5.1.3 FC must build structures that prevent single-point-of-human load while preserving creative flow.

5.2 Psychological Profiles

5.2.1 Conor — momentum and bridge-building.

• 5.2.1.1 Drive: impact and cultural proximity, not money. Wants to be in rooms where culture is shaped
• 5.2.1.2 Gifts: relationship-led sales, narrative energy ("windshield around fragile ideas"), bias to action
• 5.2.1.3 Shadows: outrunning structure, scattered focus under excitement, help-avoidance
• 5.2.1.4 Needs: repeatable GTM system others can run, clear stop rules, recognition that rest is part of the engine

5.2.2 Polina — meaning and integration.

• 5.2.2.1 Drive: usefulness, integrity, empowerment of creatives. Chooses people carefully, commits fully
• 5.2.2.2 Gifts: translates chaos into direction, protects product from becoming soulless, reads what creatives will resent before they articulate it
• 5.2.2.3 Shadows: invisible responsibility (absorbs emotional load), self-doubt as over-accountability, becomes safety net for everyone
• 5.2.2.4 Needs: explicit boundaries on what is hers, meaning check-ins not her solo job, psychological safety to flag overload early, visible leadership credit

5.2.3 Marin — reality and building.

• 5.2.3.1 Drive: mastery, buildability, ethical constraint ("people love it daily" + "not making the world worse")
• 5.2.3.2 Gifts: first-principles feasibility, cuts elegance to reach PMF, coherent product thesis, calm under pressure
• 5.2.3.3 Shadows: fixes alone with late visibility, technical scaling cliff risk (AI-generated code, low review), communication avoidance
• 5.2.3.4 Needs: earlier surfacing of complexity, hiring plan to reduce single-point-of-failure, permission to slow down for future speed

5.3 Culture Recommendations

5.3.1 Operating principles (not values posters):

• 5.3.1.1 Taste is the work — amplify judgment, do not replace it
• 5.3.1.2 Flow is sacred — interruptions are expensive, async is default
• 5.3.1.3 Ownership without permission — high agency, low bureaucracy
• 5.3.1.4 Pragmatism over purity (until PMF) — ship to learn, then stabilise
• 5.3.1.5 System trust — aligned then sprint; misaligned then realign

5.3.2 Burnout guardrails:

• 5.3.2.1 No lone-engine rule: if a domain requires one founder constantly, it is a red flag
• 5.3.2.2 No invisible-load rule: emotional labour and complexity must be visible early
• 5.3.2.3 No vibe-drift rule: if messaging/product sounds like generic AI tooling, stop and reset

5.3.3 Hiring philosophy. Hire for: demonstrated taste (any craft) + ability to explain what good is, high agency, trustworthy collaboration (low ego, low politics), comfort with ambiguity and speed. Avoid early: process worshippers, status/title seekers, constant-sync-attention people.

5.3.4 Culture-product consistency: if the product is a decision ledger, the company must model crisp decision records, clear rationale, visible tradeoffs. Otherwise the promise is performative.

5.4 Rituals

5.4.1 Alignment Sprint (every 4-6 weeks, 90 min):

• 5.4.1.1 15 min — what changed in market/customers?
• 5.4.1.2 30 min — top 3 decisions made or avoided — still right?
• 5.4.1.3 30 min — re-choose one target customer and one pain point for next sprint
• 5.4.1.4 15 min — name one load imbalance risk + mitigation
• 5.4.1.5 Output: 1-page alignment note shared internally

5.4.2 Flow Protection Protocol (daily). Shared language: FLOW (do not interrupt), OPEN (interrupt okay), URGENT (tap only if truly urgent).

5.4.3 Decision Ledger (weekly, 15 min Friday): one decision that moved forward, one deferred (why), one needed next week.

5.4.4 Meaning & ethics check (monthly, 30 min, rotating owner): still building something not making the world worse? Where is AI slop creeping in? What would a senior creative respect?

5.4.5 Complexity reveal (weekly engineering): top 3 brittle areas, top 3 unknowns, what would force a rewrite. Prevents silent-bottleneck dynamics.

5.5 Onboarding Questions

5.5.1 For early hires, advisors and pilot customers:

• 5.5.1.1 Taste: show 3 excellent pieces of work + what makes them excellent. A time your taste changed — what caused it?
• 5.5.1.2 Agency: a time you shipped something imperfect on purpose. When you cold-started with no permission?
• 5.5.1.3 Flow: conditions for deep work? How you signal them? How you prefer critique?
• 5.5.1.4 Ethics: where does AI harm creative work? What would you refuse to build?
• 5.5.1.5 Empathy: what would make a senior creative resent this tool? How prevent it?

5.6 Founder Narratives

5.6.1 Story engines for website, decks, talks, PR:

• 5.6.1.1 The Windshield — early ideas are fragile, FC protects a spark long enough to catch. Use: landing page, keynote, brand film
• 5.6.1.2 Taste is what's left — AI strips low-value execution, taste remains scarce. FC = taste amplifier. Use: thought leadership, hiring, investor narrative
• 5.6.1.3 A system, not a team — momentum x meaning x reality. Use: founder story, recruiting, internal alignment
• 5.6.1.4 Creative DNA — team's judgment accumulates over projects. Must be agency-safe and opt-in. Use: longer-term narrative, not early marketing

5.7 Consistency Checklist

5.7.1 Before shipping, posting publicly or hiring:

• 5.7.1.1 Does this amplify taste or produce generic output?
• 5.7.1.2 Does this protect flow or add process?
• 5.7.1.3 Does this create compounding memory or just more content?
• 5.7.1.4 Does this reduce context fragmentation in the earliest phase?
• 5.7.1.5 Does this increase founder dependence (bad) or system capability (good)?

5.8 Immediate Recommendations

5.8.1 Name the tripwire: "imbalance is our failure mode."

5.8.2 Install Alignment Sprint now (before hiring accelerates).

5.8.3 Begin decision ledger habit internally.

5.8.4 Make one visible commitment: "Conor is not the only engine" — transfer one GTM activity.

5.8.5 Give Polina one explicit protected domain as decision owner.

5.8.6 Ask Marin to publish weekly complexity reveal.

5.8.7 Language guidance — lean into: taste, judgment, coherence, protection, flow, decision, craft, "hold the thread." Avoid: "replace creatives," "automate creativity," "digital twin" (too early), generic AI hype.