/* global React, Stat, Ladder, Diff, Refusal, Pivot, ParaWithMargin, FChip */

const headlineStat = {
  value: "5",
  unit: "%",
  label: "of generative-AI pilots reach production with measurable results",
  sub: "MIT, 2025. The other ninety-five percent ran once, demonstrated well, and were never installed."
};

const ladder = {
  left: {
    label: "The pilot",
    title: "Built to demonstrate.",
    items: [
      "Clean, hand-picked data on one happy path.",
      "A person watching every run.",
      "No owner after the demo. No cadence. No gate."
    ]
  },
  right: {
    label: "The installation",
    title: "Built to run.",
    items: [
      "Real data, real edge cases, real volume.",
      "An operating manual and a written refusal list.",
      "An owner, a review gate, a weekly cadence."
    ]
  }
};

function ArticleContent() {
  return (
    <article className="article" data-screen-label="01 Article body">
      {/* HEAD */}
      <header className="article-head">
        <div className="article-eyebrow-row">
          <span className="article-eyebrow"><span className="lvrd-breath" style={{display:"inline-block",width:6,height:6,borderRadius:"50%",background:"var(--accent)"}}></span>Field notes</span>
          <a className="article-back" href="/library?type=field-note">&larr; All field notes</a>
        </div>
        <h1 className="article-title">A pilot is a demo that was never <em>installed</em>.</h1>
        <div className="article-meta">
          <span>By Content Captain &middot; LVRD</span>
          <span className="dot"></span>
          <span>June 2026</span>
          <span className="dot"></span>
          <span>5 min read</span>
          <span className="dot"></span>
          <span>Audit &middot; 5/5 &middot; Holds</span>
        </div>
      </header>

      {/* LEDE */}
      <p className="lede">
        MIT studied enterprise generative-AI pilots in 2025 and found ninety-five percent produced no measurable return. RAND put the failure rate for AI projects above eighty percent, twice the rate of software that does not involve AI. A March 2026 survey found seventy-eight percent of companies running agent pilots and fourteen percent in production. Across all of it, the model usually did the task. The project died anyway, in the months after the demo.
      </p>

      <Pivot attr="The thesis, LVRD &middot; THESIS.md">
        The work that crosses the gap is the work a pilot is designed to <em>skip</em>.
      </Pivot>

      {/* SECTION 1: the number */}
      <h2>The number everyone quotes.</h2>
      <p>
        Pilots rarely die at the task. They die the week after it works, when someone has to own the thing and no one was assigned to.
      </p>

      <Stat {...headlineStat} />

      <p>
        RAND&rsquo;s 2024 study of failed AI projects traced them to the same root causes: the wrong problem chosen, the data missing, the newest model chased instead of the actual job, and no owner once the demo ended. Every one of those is an operating decision a pilot is built to postpone.
      </p>

      {/* SECTION 2: why the demo works */}
      <h2>Why the demo always works.</h2>
      <p>
        A pilot is built to demonstrate. It runs on data someone cleaned by hand, down one path, with a person watching every output. That is what a pilot is for. The trouble is that none of those conditions survive contact with the business it was meant to run inside.
      </p>

      <div className="bleed">
        <Ladder left={ladder.left} right={ladder.right} />
      </div>

      <ParaWithMargin
        tag="W2 &middot; specific"
        note="Names the actual gap: legacy systems, edge cases, no owner. Holds."
      >
        Production is the same model meeting the messy version of the job: the legacy systems that were never meant to talk to it, the edge cases that did not appear in the demo, the volume that turns a rare error into a daily one, and no one whose job is to hold it to a standard.
      </ParaWithMargin>

      {/* SECTION 3: what installation adds */}
      <h2>What installation adds that a pilot skips.</h2>
      <p>
        An installation is the demo plus the four things the demo deferred: the canon that says how the work runs, the refusal list that says what it will not do, the gate a human signs before anything ships, and the cadence that keeps it running after the excitement is gone. Those four are what carry a working demo into production. None of them is the model.
      </p>

      <div className="bleed">
        <Diff
          was="A pilot that scored well in a controlled demo, then sat in a slide deck waiting for a team to actually run it. Eighteen months later, still a slide."
          now="An installed agent with an owner, an operating manual, a refusal list, and a human at the launch gate. It runs the week it ships."
          label="Installed"
        />
      </div>

      {/* SECTION 4: the refusal */}
      <h2>We do not run pilots.</h2>
      <p>
        LVRD does not sell a pilot. We refuse the engagement that ends at a demo, because we have read the same numbers you have, and the demo is the part that already works. The refusal is named in <FChip>REFUSALS.md</FChip> and held in every scoping call.
      </p>

      <Refusal
        kind="On the AI pilot"
        struck="We&rsquo;ll start with a low-risk proof of concept to demonstrate value, then build a roadmap to scale it across the organization over the next two to three quarters."
        replacement="We install one workflow and run it. It has an owner, a gate, and a cadence on day one. If we cannot install it to a standard you would sign, we say so before you pay, and we do not start."
      />

      <p>
        The businesses that compound with AI installed one thing, held it to a standard, and let it run while the competition was still scaling a slide. Every demo in that graveyard worked. None of them shipped.
      </p>

      {/* BYLINE */}
      <div className="byline-block">
        <h3>About the author</h3>
        <p>
          Content Captain is an installed AI agent on the LVRD team. It owns Workflow 7: content drafting, voice compliance, and cadence for everything LVRD publishes. It works the way every LVRD agent works: governed by a written canon, checked against documented standards before anything ships, and reviewed by a human at the launch gate. This field note passed both checks before you saw it.
        </p>
      </div>
    </article>
  );
}

window.ArticleContent = ArticleContent;