Chapter 2: Narrative As Infrastructure

Collapse teaches you to see architecture. But seeing isn't enough—you have to document what you've seen in ways others can learn from. That requires different methodology entirely.

In 2015, I joined the San Diego Memoir Writers Association to develop that methodology. I wasn't seeking emotional catharsis. I needed to learn how to document what had happened in a way that would make the architecture visible to others.

The distinction mattered. Healing is personal. Documentation is structural. I was looking for a way to translate lived experience into something that could be studied, taught, replicated by others navigating similar terrain.

The group met monthly inside the home of a local author. Published authors, former journalists, people working on family histories, a few who'd survived things they needed to name. The range of experience was wide, but everyone understood: writing is craft, not therapy. You study it the way you'd study any discipline that requires precision.

I started reading memoir craft books. Mary Karr's "The Art of Memoir." Vivian Gornick's "The Situation and the Story." Books on screenplay structure, three-act frameworks, how to build dramatic tension when your story doesn't have a clear antagonist.

That last part kept surfacing as a problem.

McGee was in the story, but he wasn't the story. The story was the structure that let him operate with hidden incentives while facing no accountability. The story was the gap between fiduciary responsibility as stated mission and extraction as actual behavior. The story was why competence didn't protect me when someone with positional power decided my success should belong to someone else.

How do you write that?

Traditional memoir wants a villain you can point to, a clear moral arc, a moment of triumph where you reclaim power. Agents want to know: who's the bad guy, what's the lesson, why should readers care?

But institutional extraction doesn't work that way. The people involved are almost incidental. If it hadn't been McGee, it would have been someone else operating within the same incentive structure, using the same blind spots, protected by the same institutional silence.

I needed to learn how to make that visible without losing the human story that made it matter.

STORIES AS SYSTEMS

I started studying memoir craft. The first thing I noticed: my experience had already organized itself into three-act structure. Building Inspirador (rising action). The collapse (reversal). Emergence (resolution with knowledge, not triumph).

I hadn't engineered this structure. It had emerged naturally from the events themselves.

That realization stopped me. Entrepreneurship follows narrative architecture. Every business I'd built had followed this pattern. Vision (inciting incident). Build (rising action). Crisis (reversal). Collapse or survival (climax). Aftermath (resolution).

Stories are systems. Systems are stories. Both require clear structure, internal logic, cause and effect, resilience under pressure, narrative coherence.

This wasn't metaphor. It was methodology. I was discovering that documenting a system is itself a form of system intervention—the act of making structure visible changes what builders can see before they commit.

At Inspirador, I'd built an operating system where seven businesses reinforced each other. Venue supported caterer, caterer supported florist, photographer supported stationer. Revenue streams were narrative threads that wove together into a coherent whole.

When I lost Inspirador, I lost the physical business but the operating system survived. The new owners didn't redesign the model. They inherited the narrative structure I'd built. Seven years later, it was still running because the story held together.

Now I was learning to do the reverse: build a narrative structure that could hold a complex system and make it legible to people who'd never seen institutional extraction up close.

The memoir workshops taught me craft basics. Scene construction. Character development. How to compress time. But what I was really learning was systems documentation through narrative form.

How do you show coordination failure without getting lost in technical detail? How do you make institutional extraction feel visceral without simplifying it into individual villainy? How do you document evidence while maintaining dramatic tension?

I started writing scenes. The day I met the building's owner and he warned me about "property snatchers." The moment I realized McGee had falsified loan documents. The morning after loss when I stood in the pool and understood I'd been living inside a structure designed to allow what happened.

The craft was coming. But so was something else. I was reverse-engineering my own experience to find the pattern underneath—the mechanism, not just the narrative. I was identifying the architectural vulnerability that made my story possible, beyond the personal experience of loss.

I wasn't learning to write my story. I was learning to map a system. The craft skills I was developing—scene construction, narrative compression, evidence integration—were system documentation tools disguised as memoir techniques.

That pattern was what others needed to see.

THE FORM PROBLEM

I started sharing early chapters with the writers group. The feedback was consistent and contradictory.

"This is powerful." "Nobody's going to read 300 pages about SBA financing."

"Your writing is strong." "The story is too complex for general readers."

"I can feel what you went through." "Agents won't touch this—there's no clear resolution."

One instructor pulled me aside after a workshop. "You're a good writer," she said. "But this story doesn't fit what publishers want. They need: clear villain, relatable struggle, inspirational ending. Your story has institutional critique, systemic analysis, ongoing extraction. That's not what sells."

She wasn't wrong. She was describing the market accurately.

Traditional publishing wanted simple narrative, individual triumph, clean ending, broad appeal, inspirational message.

What I had: multiple actors operating within flawed systems, competence that didn't prevent extraction, evidence that proved fraud but didn't stop it, a business model that worked so well it survived my displacement, no redemptive ending where I "got my power back."

Publishers wanted "Eat, Pray, Love" or "Wild." Woman overcomes hardship, finds herself, emerges stronger.

I had woman who builds successfully, system extracts anyway, woman documents why this was structurally possible and develops frameworks so others can recognize the pattern. Educational material, not inspirational narrative.

The rejection wasn't just about my story. It was about what kind of stories get told and who gets to decide what's valuable. Women's memoirs sell when they're about personal transformation, resilience, overcoming. They don't sell when they're about systems that punish competence and protect extraction.

The problem wasn't story quality. It was market ideology. Traditional publishing was another centralized system with gatekeepers who decided what narratives were worth distributing and what narratives threatened the structures that made their business model possible.

WHEN THE FORM BREAKS

The rejection list revealed something I hadn't expected: my story resisted traditional form because it was documenting coordination failure, not individual failure.

Most memoirs operate on the assumption that individual agency determines outcomes. You make choices. Those choices have consequences. You learn. You grow. You change. Your transformation is the story.

But what happens when you perform flawlessly and the system extracts anyway? The story becomes one of structural design rather than personal growth.

Traditional memoir assumes a clear protagonist with agency, an identifiable antagonist, character arc through personal change, and resolution through individual action.

My story demonstrated the opposite: competence doesn't override systemic vulnerability, no single villain exists when multiple actors operate within flawed structures, personal transformation doesn't prevent institutional extraction, and resolution requires architectural change rather than individual empowerment.

The problem wasn't my writing. The problem was narrative form designed for a world where individual merit determines outcomes.

That worldview works when systems are neutral. When playing by the rules protects you. When competence translates to security. When documentation equals proof.

But I'd lived through the opposite. Where the system wasn't neutral, it protected concentrated power. Where playing by the rules exposed you to actors who didn't. Where competence made you a more valuable target. Where documentation only mattered if someone in authority agreed on its interpretation.

Historian Carolyn Kay Steedman argued that traditional autobiography encodes middle-class assumptions about individual agency. In "Landscape for a Good Woman," she showed how working-class experience resists memoir form because the form presumes upward mobility and personal transformation. Cultural theorist Lauren Berlant would later term this "cruel optimism"—when the genres we're taught to aspire to actually organize the conditions of our harm. My story resisted traditional memoir for similar structural reasons: the form presumes individual agency determines outcomes. My experience documented the opposite.

Traditional memoir form encodes the just-world fallacy. The belief that outcomes track deservingness, that systems reward competence, that telling your truth protects you.

My story required different architecture: systems narrative. Instead of chronicling personal transformation, I needed to document how the system operates, why that made extraction possible, and what design principles would prevent it.

This was why agents said it was "too complex." The form itself challenged the market's organizing assumptions about how the world works, threatening not readers' comprehension but the industry's ideology.

Publishing wants stories that confirm: you have agency, work pays off, truth wins.

My story documented: systems concentrate vulnerability, competence doesn't equal protection, truth requires someone in power to recognize it.

Architecture doesn't sell the way inspiration does. But I wasn't writing for the inspiration market. I was writing for the people who needed to see the structure. The entrepreneurs who would build next. The founders who would navigate financing. The creators who would need to recognize when systems were protecting them and when systems were exposing them.

That audience didn't need me to simplify. They needed me to stay precise.

I kept writing, but no longer for agents, publishers, or the market that wanted simple villains and clean endings. I was writing the documentation that would make the next generation of builders less vulnerable to what I'd lived through.

That meant preserving complexity. Maintaining technical detail. Showing the mechanics of extraction without reducing it to personal grievance. Building the case study that could be studied.

The story and the methodology were the same thing. I wasn't just documenting institutional extraction—I was building the analytical infrastructure that would let others recognize it before experiencing it. Documentation wasn't record-keeping. It was preventive architecture.

Documenting how systems fail is itself a framework for building systems that don't. Teaching others to see coordination failure is teaching them to design coordination differently. Narrative architecture and business architecture use the same principles, and both can be designed to either protect or expose the builder.

The writing apprenticeship wasn't making me a memoirist. It was making me a systems architect who could use narrative to make invisible structures visible.

RECOGNIZING THE PATTERN

Around this time, I read Jaron Lanier's "Ten Arguments for Deleting Your Social Media Accounts Right Now."

The book wasn't about social media toxicity in the way most critiques were. It was about how centralized platforms extract value from users while maintaining the illusion of participation.

Users generate content. Platforms control distribution. Algorithms decide what gets seen. The creator does the work. The platform captures the value. And the creator is told this is "democratization."

I recognized the pattern immediately.

I built Inspirador. McGee controlled the financing structure. I did the work. He captured the value. The system called this "fiduciary responsibility."

Now I was seeing it again in publishing. Writers create the work. Publishers control distribution. Gatekeepers decide what gets published. The writer does the labor. The publisher captures the rights. The industry calls this "curation."

Centralized authority. Asymmetric power. Extraction disguised as protection. Someone else deciding whether your work has value and on what terms you can share it.

Traditional publishing would do to my story what McGee did to my business: take the thing I built, decide what it was worth, control how it reached people, and capture most of the value generated.

That clarity changed everything.

I wasn't interested in finding the right agent or crafting the perfect query letter or figuring out how to make my story fit what New York wanted. I wasn't interested in signing away rights to documentation that was going to serve as foundational material for a field I was building.

I was interested in permission-less distribution. In owning my work. In reaching the people who needed it without asking gatekeepers whether my story was "marketable."

I didn't know what technology would make that possible yet. But I knew I was willing to wait for it.

I'd already lost one thing I built by trusting a centralized system that claimed to protect me while serving someone else's interest. I wouldn't do that again.

ARCHITECTURE AS PROTECTION

The writing apprenticeship taught me something I hadn't expected.

I'd thought I was learning how to tell my story. What I was actually learning was how to see that stories and systems use the same architecture, and both can be designed to either protect or expose the builder.

Inspirador's multi-tenant operating system was designed to be resilient. Revenue streams reinforced each other. One function supported the next. The structure survived my displacement because the architecture was sound.

Traditional memoir form is designed for individual transformation narratives. It assumes agency, requires clear antagonist, ends with personal triumph. My story broke the form because it documented systemic failure.

I'd been learning to recognize extraction architecture across domains: real estate, financing, supply chains, narrative forms, publishing platforms.

I was learning to ask a different question: Where can I build so the architecture protects me instead of exposing me? The question was no longer about succeeding within existing systems, but about finding different systems entirely.

The ecommerce experiment had shown me I could build without brick-and-mortar vulnerability. The writing apprenticeship had shown me I needed permission-less distribution.

I wasn't ready to build publicly again. But I was ready to recognize the pattern I'd been watching throughout my career: how coordination systems concentrate power in whoever controls infrastructure, how that concentration creates vulnerability for everyone else, how building inside centralized systems means accepting terms that can change unilaterally.

The question forming wasn't about finding better partners. It was about finding different architecture. Where verification doesn't require interpretation. Where ownership doesn't require permission. Where evidence doesn't require someone in authority to agree it's valid.

I was learning that the documentation I was building—the case studies, the frameworks, the pattern recognition methodology—would only matter if I could distribute it through infrastructure that didn't replicate the extraction I was documenting.

Using centralized platforms to critique centralized extraction would reproduce the problem. The platforms would monetize my documentation while I lost control over distribution, narrative integrity, and audience relationships.

So I waited. And while I waited, I built capacity. The writing craft to make complexity legible. The analytical frameworks to extract teachable patterns from lived experience. The evidence base to support structural claims. The methodology to help others recognize architectural vulnerability before they build inside it.

By the time the right infrastructure emerged, I would be ready with the documentation complete, the frameworks extracted, the patterns mapped, and the evidence preserved.

What comes next is not about rebuilding my business. It is about understanding the pattern that made my collapse both possible and instructive. Chapter 3 examines how information asymmetry functions as structural vulnerability: how systems create separate realities for different parties, why contradictions persist without reconciliation, and how concentrated information control enables extraction even when all parties follow the stated rules.

The architecture I was learning to see in my own collapse was the same architecture operating across every coordination system I'd ever built inside. Understanding it would change everything about how I built next.