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

const headlineStat = {
  value: "$50B+",
  label: "spent each year on AI work that dies between demo and deployment",
  sub: "The pilot graveyard. Most of it was paid to someone for a strategy, not a system."
};

const ladder = {
  left: {
    label: "The deck",
    title: "Ends at agreement.",
    items: [
      "Forty use cases ranked in a workshop.",
      "A roadmap nobody on the build side pressure-tested.",
      "A handoff to your team, or to a second vendor."
    ]
  },
  right: {
    label: "The system",
    title: "Ends at running.",
    items: [
      "One workflow, scoped to a schema.",
      "An agent built against that schema and run.",
      "An owner and a gate. Nothing to hand off."
    ]
  }
};

const alignmentSteps = [
  { title: "Scope one workflow", body: "The single piece of work where a dropped ball is most expensive: the deadline-or-compliance coordination that runs through one person. One, not forty." },
  { title: "Write the schema", body: "“Automate approvals” is vague enough that everyone nods. A field that names the approver role and the dollar threshold cannot be misread. The schema is the alignment." },
  { title: "Build the agent", body: "Against the schema, with a refusal list and a kill switch from the first version, not a later phase." },
  { title: "Run it behind a gate", body: "A human signs before it acts. What you are handed is a running agent that is already doing the job." }
];

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 deck is not a <em>system</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">
        A firm sells an assessment. The assessment becomes a roadmap. The roadmap becomes a multi-year engagement. Somewhere around month fourteen, someone asks what was actually built, and the answer is a stack of documents. The deliverable described a possible future. The business went back to running the way it ran, a little more confused.
      </p>

      <Pivot attr="The load-bearing rule, this piece">
        The handoff is where the system dies. So there is no <em>handoff</em>.
      </Pivot>

      {/* SECTION 1: what the deck sells */}
      <h2>What the strategy deck actually sells.</h2>
      <p>
        A deck sells alignment, and alignment is real: getting a room of stakeholders to agree on what matters is hard, and a good deck does it. The trouble is that the consulting model stops there, because a strategy that takes a thousand hours to advise on is better business for an hourly firm than a system that takes ten hours to build. The room nods, the check clears, and execution becomes someone else&rsquo;s problem.
      </p>

      <Stat {...headlineStat} />

      <p>
        That is the half a deck skips: building the thing and running it, which is the half you were paying for.
      </p>

      {/* SECTION 2: alignment in a slide doesn't hold */}
      <h2>Alignment in a slide does not hold.</h2>
      <p>
        &ldquo;Automate the approval process&rdquo; is vague enough that everyone in the room agrees to it. That agreement feels like alignment. It holds until someone has to build the thing and finds that no two people meant the same approver, the same threshold, or the same exception.
      </p>

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

      <ParaWithMargin
        tag="W2 &middot; specific"
        note="Names the mechanism: the schema forces the decisions the slide let everyone avoid. Holds."
      >
        Real alignment happens when you write the work down precisely enough to run it. A schema that names the approver role and the dollar threshold cannot be read two ways. Building is how you find out what you actually agreed to.
      </ParaWithMargin>

      <Steps steps={alignmentSteps} />

      {/* SECTION 3: the handoff */}
      <h2>The handoff is the failure mode.</h2>
      <p>
        The common pattern: a company hires a consultant to design the strategy, then a second vendor to build it. The consultant hands off a spec. The build shop builds the spec. The result does not work, because the spec rested on business assumptions no engineer pressure-tested and technical limits no strategist ever saw. You paid two firms to cover one scope, and the seam between them is where the system died.
      </p>
      <p>
        This is most of the eighty-eight percent of pilots that never reach production. The technology is rarely what breaks. The handoff is, and it compounds every time the people who design a system are not the people who run it.
      </p>

      {/* SECTION 4: the refusal */}
      <h2>We build it, run it, keep it honest.</h2>
      <p>
        LVRD aligns in hours, and the alignment happens by building the canon and the agents instead of assembling slides. Then we run the result. We refuse the engagement that ends at a document, because the document is the part that does not work. The refusal is named in <FChip>REFUSALS.md</FChip>.
      </p>

      <Refusal
        kind="On the strategy deliverable"
        struck="We&rsquo;ll deliver a comprehensive AI strategy and implementation roadmap, with a prioritized backlog of use cases and a recommended vendor stack for your team to execute against."
        replacement="We deliver a running agent, behind a gate you control, doing one job to a standard you ratified. Nothing to execute later. Nobody to hand it to. The system is the deliverable."
      />

      <p>
        When this decade&rsquo;s pilots get audited, the question will be simple: did the thing still run on its first bad day? A deck cannot answer that. A running system can. LVRD builds for that day.
      </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;