konpeki 0.3.1 → 0.4.0

package/slides/README.md

@@ -1,56 +0,0 @@
-# What can I make with Konpeki?
-
-Reviewed examples with editable text and vector artwork. Scenarios and data
-are illustrative; these are finished documents, not one-click templates.
-
-Download an example's JSON and choose **Demo Mode → Import** in the
-[playground](https://vcfgdev.github.io/konpeki/). For revision notes and agent
-handoff, open it in a [file-backed preview](../docs/workflow.md#file-backed-editing-with-an-agent).
-Playground edits stay in your browser.
-
-## Explain a system
-
-An order platform's request handling, data, events and fulfillment.
-
-[Editable JSON](gallery/architecture.json) ·
-[Brief](gallery/PROMPT.md#architecture) · [Source](gallery/SOURCE.md#architecture)
-
-![Editable order-platform architecture](gallery/architecture.png)
-
-## Communicate data
-
-A proportional Sankey follows 1,000 trial users through activation and outcomes.
-
-[Editable JSON](gallery/sankey.json) ·
-[Brief](gallery/PROMPT.md#sankey) · [Source](gallery/SOURCE.md#sankey)
-
-![Editable trial-user flow with proportional ribbons](gallery/sankey.png)
-
-## Announce a release
-
-A 1080×1350 Clearpath release announcement: preview, review and export Markdown.
-
-[Editable JSON](gallery/release.json) ·
-[Brief](gallery/PROMPT.md#release) · [Source](gallery/SOURCE.md#release)
-
-![Clearpath portrait announcement](gallery/release.png)
-
-## Teach a concept
-
-A 1200×1600 Folio explainer shows a stale save, its rejection and recovery choices.
-
-[Editable JSON](gallery/explainer.json) ·
-[Brief](gallery/PROMPT.md#explainer) · [Source](gallery/SOURCE.md#explainer)
-
-![Folio optimistic-concurrency explainer](gallery/explainer.png)
-
-## More examples
-
-- [Introducing Konpeki](introducing-konpeki/README.md): six-page product overview.
-- [Repository cover](github-cover/README.md): 1280×640 social preview.
-- [React/SVG drawing references](drawing-references.md): 18 older examples, not editor-importable documents.
-
-These four gallery exports are repository-only; their authoring projects are
-maintained separately. They are not bundled in npm or the hosted playground.
-The introduction and cover JSONs are included in npm; the playground bundles
-the introduction. View this gallery in the repository for its screenshots.

package/slides/architecture/PROMPT.md

@@ -1,31 +0,0 @@
-Make a three-page presentation explaining Parcel Relay to engineers joining its
-team. Help them follow an event from acceptance to delivery and understand why
-a timeout can lead to a duplicate request.
-
----
-
-Parcel Relay is a fictional webhook delivery service. A producer submits an
-event with an event ID. The API saves the event and its delivery job in one
-database transaction and returns Accepted after the transaction commits. If
-the transaction cannot commit, the API returns an error and the event has not
-been accepted.
-
-Workers claim jobs from that database using time-limited leases, then POST the
-events to customer endpoints. Each request includes the event ID. The database
-holds the job queue; there is no separate message broker.
-
-A 2xx response marks the job delivered. A timeout or 5xx schedules another
-attempt, up to three attempts in total. A third unsuccessful attempt marks the
-job failed for human investigation. A 4xx is terminal in this example. If a
-worker crashes, another worker can claim its unfinished job after the lease
-expires, even if the customer already received the earlier request.
-
-Customers must handle repeated event IDs. Relay cannot make their side effects
-atomic or guarantee exactly-once delivery.
-
----
-
-Walk through this failure: evt-204 reaches the customer, which applies its
-update, but the response is lost. Relay times out and retries evt-204. The
-customer recognizes the event ID and skips the repeated update. That final
-step depends on the customer's implementation; Relay does not enforce it.

package/slides/architecture/index.tsx

@@ -1,102 +0,0 @@
-import type { ReactNode } from 'react';
-import '../../lib/typeface.ts';
-
-const ink = '#172633', muted = '#4D5D6B', accent = '#006EAC', line = '#A7B2BC';
-function Text({ x, y, children, size = 34, weight = 400, color = ink }: { x: number; y: number; children: ReactNode; size?: number; weight?: number; color?: string }) {
-  return <text x={x} y={y} fontSize={size} fontWeight={weight} fill={color}>{children}</text>;
-}
-function Arrow({ x1, x2, y, dashed = false }: { x1: number; x2: number; y: number; dashed?: boolean }) {
-  const d = x2 > x1 ? -16 : 16;
-  return <g fill="none" stroke={accent} strokeWidth={3}><path d={`M${x1} ${y} H${x2}`} strokeDasharray={dashed ? '10 8' : undefined}/><path d={`M${x2 + d} ${y - 10} L${x2} ${y} L${x2 + d} ${y + 10}`}/></g>;
-}
-function Frame({ title, description, page, children }: { title: string; description: string; page: number; children: ReactNode }) {
-  return <svg xmlns="http://www.w3.org/2000/svg" width="1920" height="1080" viewBox="0 0 1920 1080" fontFamily="IBM Plex Sans, sans-serif" role="img" aria-label={`${title}. ${description}`}>
-    <rect width={1920} height={1080} fill="#FFFFFF"/>
-    <Text x={112} y={150} size={64} weight={600}>{title}</Text>
-    {children}
-    <Text x={1760} y={1018} size={26} color={muted}>{page} / 3</Text>
-  </svg>;
-}
-function Acceptance() {
-  return <Frame page={1} title="Parcel Relay accepts an event after commit" description="Fictional service. Producer submits an event ID to the API. The API saves event and job in one database transaction. Accepted follows commit; commit failure returns an error, so the event was not accepted. Workers claim leased jobs from the database and POST to customer endpoints with the event ID. No separate broker.">
-    <Text x={112} y={224} color={muted}>A fictional webhook service • the database holds both events and the job queue</Text>
-    <Text x={160} y={365} size={40} weight={600}>Producer</Text>
-    <Text x={548} y={365} size={40} weight={600}>API</Text>
-    <path d="M250 390 V635 M580 390 V635" fill="none" stroke={line} strokeWidth={2}/>
-    <rect x={965} y={294} width={835} height={280} rx={8} fill="#FFFFFF" stroke={line} strokeWidth={2}/>
-    <Text x={1005} y={355} size={40} weight={600}>Database</Text>
-    <Text x={1005} y={423}>Event + delivery job</Text>
-    <Text x={1005} y={479} color={accent} weight={500}>Saved in one transaction</Text>
-    <Text x={1005} y={531} size={30} color={muted}>Commit is the acceptance boundary.</Text>
-    <Arrow x1={250} x2={580} y={415}/>
-    <Text x={280} y={397} size={30}>Submit event ID</Text>
-    <Arrow x1={580} x2={965} y={415}/>
-    <Text x={690} y={391} size={30}>Save both</Text>
-    <Arrow x1={965} x2={580} y={515}/>
-    <Text x={680} y={563} size={30}>Commit succeeds</Text>
-    <Arrow x1={580} x2={250} y={610}/>
-    <Text x={236} y={660} color={accent} weight={500}>Return Accepted</Text>
-    <path d="M1120 704 V574 M1110 590 L1120 574 L1130 590" fill="none" stroke={accent} strokeWidth={3}/>
-    <Text x={1160} y={644} size={30}>Claim leased job</Text>
-    <Text x={112} y={797} size={40} weight={600}>If commit fails</Text>
-    <Text x={112} y={855}>API returns an error.</Text>
-    <Text x={112} y={907}>The event has not been accepted.</Text>
-    <Text x={1020} y={738} size={40} weight={600}>Worker</Text>
-    <path d="M1120 756 V844" fill="none" stroke={accent} strokeWidth={3}/>
-    <Arrow x1={1120} x2={1550} y={844}/>
-    <Text x={1160} y={891} size={30}>POST + event ID</Text>
-    <Text x={1555} y={817} size={38} weight={600}>Customer</Text>
-    <Text x={1555} y={869} size={30}>endpoint</Text>
-  </Frame>;
-}
-function Outcomes() {
-  return <Frame page={2} title="The response decides the job’s next state" description="2xx marks delivered. Timeout or 5xx schedules another attempt, up to three attempts total. The third unsuccessful attempt marks failed for human investigation. 4xx is terminal. If a worker crashes, another may claim the unfinished job after lease expiry even if the customer already received it.">
-    <Text x={112} y={228} color={muted}>After each POST, the worker records the outcome in the database.</Text>
-    <Text x={112} y={346} size={30} color={muted}>OBSERVED RESULT</Text>
-    <Text x={660} y={346} size={30} color={muted}>WHAT RELAY DOES</Text>
-    {[380, 490, 660, 780].map(y => <line key={y} x1={112} x2={1808} y1={y} y2={y} stroke={line} strokeWidth={2}/>)}
-    <Text x={112} y={447} size={40} weight={600}>2xx</Text>
-    <Text x={660} y={447} size={38}>Marks the job delivered.</Text>
-    <Text x={112} y={555} size={40} weight={600}>Timeout or 5xx</Text>
-    <Text x={660} y={552} size={38}>Schedules another attempt; three attempts total.</Text>
-    <Text x={660} y={609} size={32} color={muted}>Third unsuccessful attempt: failed, for human investigation.</Text>
-    <Text x={112} y={731} size={40} weight={600}>4xx</Text>
-    <Text x={660} y={731} size={38}>Terminal in this example.</Text>
-    <Text x={112} y={865} size={38} weight={600}>A worker crash can also repeat a request</Text>
-    <Text x={112} y={925} size={34}>After lease expiry, another worker can claim the unfinished job,</Text>
-    <Text x={112} y={975} size={34}>even if the customer already received the earlier request.</Text>
-  </Frame>;
-}
-function Duplicate() {
-  return <Frame page={3} title="A timeout can hide a completed update" description="evt-204 reaches the customer and applies its update, but the response is lost. Relay times out and retries the same event ID. The customer recognizes evt-204 and skips the repeated update. This deduplication depends on the customer implementation. Relay cannot enforce it, make customer side effects atomic, or guarantee exactly-once delivery.">
-    <Text x={112} y={224} color={muted}>The same event ID connects both requests: evt-204.</Text>
-    <Text x={260} y={334} size={40} weight={600}>Relay worker</Text>
-    <Text x={1130} y={334} size={40} weight={600}>Customer endpoint</Text>
-    <line x1={380} x2={380} y1={367} y2={785} stroke={line} strokeWidth={2}/>
-    <line x1={1260} x2={1260} y1={367} y2={785} stroke={line} strokeWidth={2}/>
-    <Arrow x1={380} x2={1260} y={432}/>
-    <Text x={610} y={406} size={32}>POST evt-204</Text>
-    <Text x={1310} y={445} size={34} weight={500}>Applies update</Text>
-    <path d="M1260 525 H760" fill="none" stroke={accent} strokeWidth={3} strokeDasharray="10 8"/>
-    <path d="M746 511 L774 539 M774 511 L746 539" stroke={accent} strokeWidth={3}/>
-    <Text x={835} y={504} size={32}>Response lost</Text>
-    <Text x={112} y={561} size={32}>Times out</Text>
-    <Text x={112} y={603} size={30} color={muted}>Outcome unknown</Text>
-    <Arrow x1={380} x2={1260} y={663}/>
-    <Text x={610} y={637} size={32}>Retry POST evt-204</Text>
-    <Text x={1310} y={672} size={34} weight={500}>Recognizes evt-204</Text>
-    <Text x={1310} y={720} size={34} color={accent} weight={500}>Skips repeated update</Text>
-    <Text x={112} y={861} size={40} weight={600}>Customers must handle repeated event IDs.</Text>
-    <Text x={112} y={924} size={34}>The skip above depends on customer code; Relay does not enforce it.</Text>
-    <Text x={112} y={974} size={34}>Relay cannot make customer side effects atomic or guarantee exactly-once delivery.</Text>
-  </Frame>;
-}
-
-export const meta = { title: 'Parcel Relay', createdAt: '2026-09-12T14:14:00Z' };
-export const notes = [
-  'Audience question: When is an event accepted, and where does the job live? The connector from the database to the worker denotes job ownership, not a separate message broker.',
-  'Audience question: What happens after a delivery attempt, or a worker crash? No backoff duration or lease duration is specified by the fictional brief.',
-  'Audience question: Why did evt-204 repeat, and who prevents duplicate side effects? The customer deduplication outcome is an example, not a guarantee supplied by Relay.',
-];
-const pages = [Acceptance, Outcomes, Duplicate];
-export default pages;

package/slides/article-brief/PROMPT.md

@@ -1,35 +0,0 @@
-Turn the article below into a two-page briefing for engineering managers.
-Explain its main argument and a practical way to apply it without turning
-the author's experience into a universal rule.
-
----
-
-This is the complete fictional article, written for this example.
-
-“The decision record that survived the meeting”
-By Mira Sol, an engineer at the fictional company Alder
-
-Our meeting notes were detailed, but a month later we could not explain why
-we had chosen a daily data export over a live integration. The notes recorded
-who spoke and which tasks followed. They did not record the constraint that
-made the decision sensible: the receiving system accepted only one upload
-per day.
-
-We started keeping a short decision record alongside the work. It contains
-the question, the constraints known at the time, the alternatives considered,
-the choice and the condition that would make us revisit it. For the export,
-that condition was the receiving system adding a supported live API.
-
-This is not an attempt to predict every future requirement. It gives the next
-engineer enough context to distinguish a deliberate trade-off from an accident.
-When circumstances change, we append a new decision and link the old one
-rather than silently rewriting its rationale.
-
-Not every implementation detail deserves a record. We use one when a choice
-crosses team boundaries, is costly to reverse or depends on a constraint likely
-to change. Routine local choices can stay in code review. We still need task
-lists and meeting notes; they answer different questions.
-
-We have not measured whether this practice makes delivery faster. Our claim
-is narrower: recording the reason and revisit condition makes our decisions
-easier to explain later.

package/slides/article-brief/index.tsx

@@ -1,71 +0,0 @@
-import type { ReactNode } from 'react';
-import { Text } from '../../lib/text.tsx';
-import { fontsReady } from '../../lib/typeface.ts';
-
-await fontsReady;
-
-const ink = '#182B35';
-const muted = '#4C606B';
-const accent = '#006D77';
-
-function Copy({ x = 112, y, width = 1696, size = 38, weight = 400, color = ink, children }: {
-  x?: number; y: number; width?: number; size?: number; weight?: number; color?: string; children: string;
-}) {
-  return <Text x={x} y={y} width={width} size={size} weight={weight} color={color} maxLines={8} leading={1.22}>{children}</Text>;
-}
-
-function Canvas({ page, title, description, children }: { page: number; title: string; description: string; children: ReactNode }) {
-  return <svg xmlns="http://www.w3.org/2000/svg" width="1920" height="1080" viewBox="0 0 1920 1080" role="img"
-    aria-labelledby={`title-${page} description-${page}`} data-page={page} fontFamily="IBM Plex Sans">
-    <title id={`title-${page}`}>{title}</title>
-    <desc id={`description-${page}`}>{description}</desc>
-    <rect width="1920" height="1080" fill="#FFFFFF" />
-    <Copy y={146} size={72} weight={600}>{title}</Copy>
-    {children}
-    <text x="1808" y="1020" textAnchor="end" fill={muted} fontSize="28">{page} / 2</text>
-  </svg>;
-}
-
-const Argument = () => <Canvas page={1} title="Keep the reason with the decision"
-  description="In Mira Sol’s fictional Alder account, meeting notes preserved speakers and tasks but lost why a daily export was chosen. The receiving system allowed only one upload per day. Alder’s decision record preserved that constraint and a revisit trigger: a supported live API. Sol claims decisions became easier to explain, not measured faster delivery.">
-  <Copy y={224} size={32} color={muted}>Mira Sol’s “The decision record that survived the meeting” · A fictional Alder account</Copy>
-  <Copy y={354} width={560} size={48} weight={600}>A month later, the “why” was missing.</Copy>
-  <Copy y={508} width={550} color={muted}>Meeting notes captured who spoke and what to do next. They lost the constraint behind the export choice.</Copy>
-  <Copy x={800} y={350} width={1008} size={30} weight={600} color={accent}>ALDER’S EXPORT DECISION</Copy>
-  <line x1="800" x2="1808" y1="388" y2="388" stroke="#A5B4BC" strokeWidth="2" />
-  <Copy x={800} y={450} width={260} size={34} weight={600}>Choice</Copy>
-  <Copy x={1100} y={450} width={708} size={38}>Daily data export over a live integration</Copy>
-  <line x1="800" x2="1808" y1="532" y2="532" stroke="#A5B4BC" strokeWidth="2" />
-  <Copy x={800} y={594} width={260} size={34} weight={600}>Reason</Copy>
-  <Copy x={1100} y={594} width={708} size={38}>Receiving system accepted only one upload per day</Copy>
-  <line x1="800" x2="1808" y1="676" y2="676" stroke="#A5B4BC" strokeWidth="2" />
-  <Copy x={800} y={738} width={260} size={34} weight={600}>Revisit when</Copy>
-  <Copy x={1100} y={738} width={708} size={38}>Receiving system adds a supported live API</Copy>
-  <line x1="800" x2="1808" y1="820" y2="820" stroke="#A5B4BC" strokeWidth="2" />
-  <Copy y={922} size={40} weight={500} color={accent}>The claim: decisions became easier to explain later.</Copy>
-  <Copy y={975} size={32} color={muted}>Sol reports no measurement of faster delivery; this is one team’s experience.</Copy>
-</Canvas>;
-
-const Application = () => <Canvas page={2} title="Try a record on one consequential choice"
-  description="Suggested application for engineering managers, adapted from Sol’s fictional account: choose a decision that crosses teams, is costly to reverse, or rests on a changing constraint. Keep a short record beside the work with question, constraints, alternatives, choice, and revisit condition. If Alder gains a supported live API, reassess the export; append and link a new decision rather than overwrite the old rationale. Routine local choices can stay in code review. Keep task lists and meeting notes for their separate purposes.">
-  <Copy y={224} size={32} color={muted}>A suggested first trial, adapted from Sol’s practice—not a requirement for every team.</Copy>
-  <Copy y={350} width={620} size={44} weight={600}>Choose selectively</Copy>
-  <Copy y={420} width={620} size={36}>Use a record when a choice:</Copy>
-  <Copy y={490} width={620} size={38}>• Crosses team boundaries</Copy>
-  <Copy y={552} width={620} size={38}>• Is costly to reverse</Copy>
-  <Copy y={614} width={620} size={38}>• Relies on a constraint likely to change</Copy>
-  <Copy y={780} width={610} size={34} color={muted}>Routine local choices can stay in code review. Keep task lists and meeting notes; they answer different questions.</Copy>
-  <Copy x={860} y={350} width={948} size={44} weight={600}>Keep a short record beside the work</Copy>
-  <Copy x={860} y={423} width={948} size={36}>Question · Known constraints · Alternatives</Copy>
-  <Copy x={860} y={477} width={948} size={36}>Choice · Condition for revisiting</Copy>
-  <Copy x={860} y={600} width={948} size={44} weight={600} color={accent}>When Alder gains a supported live API…</Copy>
-  <Copy x={860} y={723} width={948} size={38}>Reassess whether the daily export still fits. Append a new decision and link the old one; preserve the original rationale.</Copy>
-  <Copy x={860} y={911} width={948} size={34} color={muted}>A manager’s review question: can the next engineer explain the trade-off and when to reconsider it?</Copy>
-</Canvas>;
-
-export const meta = { title: 'Alder — The reason behind the decision' };
-export const notes = [
-  'Source: the complete fictional article in PROMPT.md by Mira Sol at Alder. This page summarizes the stated experience and preserves its explicit evidence limit.',
-  'The single-choice trial and manager’s review question are editorial applications, not quotations or measured outcomes. All five record fields and selective-use criteria come from the supplied article.',
-];
-export default [Argument, Application];

package/slides/bar-chart/PROMPT.md

@@ -1,39 +0,0 @@
-Make a two-page briefing for the operations lead at Birch about processing time
-across five workflows. Use grouped horizontal bars to compare before and after,
-then explain the decision the evidence supports and what remains unknown.
-
-Use one common zero-based minute axis, directly label every bar and keep the
-before/after series order consistent. Make the workflow that became slower as
-easy to notice as the improvements.
-
----
-
-Birch is a fictional internal operations team. These are synthetic, hand-authored
-median active processing times per completed case. Waiting time is excluded.
-Each workflow has 80 completed cases in the before period and 80 different
-completed cases in the after period. Lower is better.
-
-Workflow | Before median (minutes) | After median (minutes)
-Account setup | 18 | 12
-Address correction | 11 | 10
-Refund review | 25 | 19
-Access removal | 7 | 8
-Supplier onboarding | 32 | 24
-
-The before and after periods each lasted two weeks. A revised work queue was
-introduced between them. Cases were not randomized or matched, and case
-complexity and staffing could differ. These are independent groups, not paired
-measurements of the same cases. No raw times, variability estimates or quality
-measurements are supplied.
-
----
-
-Four workflows have lower observed medians; access removal rises from 7 to 8
-minutes. Supplier onboarding has the largest absolute median reduction, eight
-minutes, but still has the highest after-period median at 24 minutes.
-
-Recommend investigating the access-removal increase and checking case mix and
-quality before extending the revised queue. The data do not establish that the
-queue caused any change. Do not multiply median differences by case counts to
-claim total time or money saved, or imply that a lower median means every case
-became faster.

package/slides/bar-chart/index.tsx

@@ -1,97 +0,0 @@
-import type { ReactNode } from 'react';
-import { Bar } from '@nivo/bar';
-import '../../lib/typeface.ts';
-import { chartDefaults } from '../../lib/charts.ts';
-import { palettes } from '../../lib/taste.ts';
-
-const ink = '#182B36';
-const muted = '#445663';
-const before = '#536879';
-const after = '#146B60';
-export const workflows = [
-  { workflow: 'Account setup', Before: 18, After: 12 },
-  { workflow: 'Address correction', Before: 11, After: 10 },
-  { workflow: 'Refund review', Before: 25, After: 19 },
-  { workflow: 'Access removal', Before: 7, After: 8 },
-  { workflow: 'Supplier onboarding', Before: 32, After: 24 },
-];
-
-function Copy({ x = 112, y, size = 32, weight = 400, fill = ink, children }: {
-  x?: number; y: number; size?: number; weight?: number; fill?: string; children: ReactNode;
-}) {
-  return <text x={x} y={y} fontSize={size} fontWeight={weight} fill={fill}>{children}</text>;
-}
-
-function Canvas({ title, description, page, children }: {
-  title: string; description: string; page: number; children: ReactNode;
-}) {
-  return <svg xmlns="http://www.w3.org/2000/svg" width="1920" height="1080" viewBox="0 0 1920 1080"
-    role="img" aria-label={`${title}. ${description}`} fontFamily="IBM Plex Sans, sans-serif" data-birch-page={page}>
-    <rect width="1920" height="1080" fill="#FFFFFF" />
-    <Copy y={136} size={62} weight={600}>{title}</Copy>
-    {children}
-    <Copy x={1770} y={1020} size={24} fill={muted}>{page} / 2</Copy>
-  </svg>;
-}
-
-const Evidence = () => <Canvas page={1} title="Four medians fell; access removal rose"
-  description="Synthetic Birch data, median active processing minutes per completed case; lower is better. Account setup: before 18, after 12. Address correction: before 11, after 10. Refund review: before 25, after 19. Access removal: before 7, after 8. Supplier onboarding: before 32, after 24. Each workflow has 80 independent cases per period. Waiting time excluded. These observations do not establish causation.">
-  <Copy y={202} size={30} fill={muted}>Birch · Synthetic median active processing time per completed case · Lower is better</Copy>
-  <g transform="translate(112 262)">
-    <Bar {...chartDefaults(palettes.paper)} width={1696} height={640}
-      data={[...workflows].reverse()} keys={['Before', 'After']} indexBy="workflow"
-      layout="horizontal" groupMode="grouped" valueScale={{ type: 'linear', min: 0, max: 35 }}
-      margin={{ top: 0, right: 90, bottom: 60, left: 345 }} padding={0.26} innerPadding={7}
-      colors={({ id }) => id === 'Before' ? before : after}
-      label={d => `${d.id}  ${d.value}`} labelTextColor="#FFFFFF" labelSkipWidth={0} labelSkipHeight={0}
-      axisLeft={{ tickSize: 0, tickPadding: 24 }}
-      axisBottom={{ tickSize: 0, tickPadding: 16, tickValues: [0, 5, 10, 15, 20, 25, 30, 35] }}
-      enableGridX enableGridY={false} gridXValues={[0, 5, 10, 15, 20, 25, 30, 35]}
-      theme={{ text: { fontFamily: 'IBM Plex Sans', fontSize: 28, fill: ink },
-        axis: { ticks: { text: { fontSize: 28, fill: ink } }, domain: { line: { stroke: '#8A969F' } } },
-        grid: { line: { stroke: '#DCE2E5', strokeWidth: 1 } },
-        labels: { text: { fontSize: 26, fontWeight: 500 } } }}
-    />
-  </g>
-  <Copy x={1340} y={935} size={27} fill={muted}>Minutes · common zero baseline</Copy>
-  <Copy y={934} size={30} weight={600} fill={after}>Access removal: +1 minute</Copy>
-  <Copy y={984} size={27} fill={muted}>80 different cases per workflow per period · Two weeks each · Waiting time excluded</Copy>
-</Canvas>;
-
-const Decision = () => <Canvas page={2} title="Investigate before extending the revised queue"
-  description="Recommendation: investigate the access-removal increase and check case mix and quality before extending the revised queue. Supplier onboarding has the largest absolute median reduction, 8 minutes, but still the highest after median, 24 minutes. Independent groups were not randomized or matched; complexity and staffing could differ. No raw times, variability or quality measurements were supplied. Median differences cannot establish total savings or imply every case became faster.">
-  <Copy y={207} size={32} fill={muted}>Observed changes are a reason to investigate, not evidence that the queue caused them.</Copy>
-  <Copy y={322} size={38} weight={600}>Check before rollout</Copy>
-  <Copy x={1050} y={322} size={38} weight={600}>What the comparison cannot tell us</Copy>
-
-  <Copy y={400} size={32} weight={600} fill={after}>Investigate access removal</Copy>
-  <Copy y={451}>Its median rose from 7 to 8 minutes.</Copy>
-  <Copy y={497}>Review the workflow and the cases behind it.</Copy>
-
-  <Copy y={594} size={32} weight={600} fill={after}>Check case mix, staffing and quality</Copy>
-  <Copy y={645}>Before extending the queue, compare complexity</Copy>
-  <Copy y={691}>and staffing, and collect quality measurements.</Copy>
-
-  <Copy y={788} size={32} weight={600} fill={after}>Keep supplier onboarding in view</Copy>
-  <Copy y={839}>32 → 24 minutes: the largest drop, 8 minutes.</Copy>
-  <Copy y={885}>It still has the highest after-period median.</Copy>
-
-  <Copy x={1050} y={400} size={32} weight={600}>No causal attribution</Copy>
-  <Copy x={1050} y={451}>The queue changed between two two-week periods.</Copy>
-  <Copy x={1050} y={497}>Groups were independent, not randomized or matched;</Copy>
-  <Copy x={1050} y={543}>case complexity and staffing could differ.</Copy>
-
-  <Copy x={1050} y={640} size={32} weight={600}>No estimate of uncertainty or total savings</Copy>
-  <Copy x={1050} y={691}>No raw times, variability or quality data were supplied.</Copy>
-  <Copy x={1050} y={737}>Do not multiply median changes by case counts</Copy>
-  <Copy x={1050} y={783}>to claim total time or money saved.</Copy>
-  <Copy x={1050} y={861}>A lower median does not mean every case was faster.</Copy>
-  <Copy y={1000} size={27} fill={muted}>Birch is fictional. All measurements are synthetic, hand-authored data.</Copy>
-</Canvas>;
-
-export const meta = { title: 'Birch — Processing time' };
-export const notes = [
-  'Source: exact supplied PROMPT.md. The chart compares independent medians, not paired cases. All bars share a 0–35 minute scale.',
-  'Recommendation follows the supplied brief. No causal, total-savings, statistical-significance or universal-improvement claim is justified.',
-];
-export default [Evidence, Decision];

package/slides/comparison/PROMPT.md

@@ -1,29 +0,0 @@
-Make a three-page presentation helping the operations lead at Moss choose a
-support inbox for a six-person team. Compare the options against the team's
-actual needs and recommend what to trial.
-
----
-
-Moss and all three products are fictional. The team needs email intake, shared
-assignment and a complete CSV export of ticket history. Its monthly subscription
-budget is $150. Chat support would be useful later, but is not required now.
-The team does not have capacity to operate its own server.
-
-- Postbox: hosted, $18 per agent per month. Email intake, shared assignment and
-  complete CSV history export are included. No chat channel. No setup fee.
-- Threadline: hosted, $24 per agent per month. Includes email, chat, shared
-  assignment and complete CSV history export. No setup fee.
-- OwnDesk: self-hosted, no software subscription fee. Includes email, chat,
-  shared assignment and complete CSV history export. The team must supply
-  hosting, backups, upgrades and incident response; their costs are unknown.
-
-These are hand-authored scenario specifications, not vendor research. Hosted
-prices exclude tax and assume six paid agents. There are no measured usability,
-reliability or migration results. A feature being listed does not establish
-how well it works.
-
----
-
-Recommend a first trial, explain what would make the other hosted option worth
-its extra cost, and identify what to verify before purchase. Treat self-hosting
-as an operational commitment rather than a zero-cost option.

package/slides/comparison/index.tsx

@@ -1,95 +0,0 @@
-import type { ReactNode } from 'react';
-import '../../lib/typeface.ts';
-
-const ink = '#172B26';
-const muted = '#4F605A';
-const accent = '#236B50';
-const rule = '#C4CEC9';
-
-function Copy({ x = 112, y, lines, size = 36, weight = 400, color = ink }: {
-  x?: number; y: number; lines: string[]; size?: number; weight?: number; color?: string;
-}) {
-  return <text x={x} y={y} fill={color} fontSize={size} fontWeight={weight}>
-    {lines.map((line, i) => <tspan key={i} x={x} dy={i ? size * 1.35 : 0}>{line}</tspan>)}
-  </text>;
-}
-
-function Canvas({ title, description, number, children }: {
-  title: string; description: string; number: number; children: ReactNode;
-}) {
-  return <svg xmlns="http://www.w3.org/2000/svg" width="1920" height="1080" viewBox="0 0 1920 1080"
-    fontFamily="IBM Plex Sans" role="img" aria-label={`${title}. ${description}`} data-moss-page={number}>
-    <rect width="1920" height="1080" fill="#FFFFFF" />
-    <Copy y={154} lines={[title]} size={72} weight={600} />
-    {children}
-    <Copy x={1752} y={1022} lines={[`${number} / 3`]} size={28} color={muted} />
-  </svg>;
-}
-
-const Shortlist = () => <Canvas number={1} title="Moss should trial Postbox first"
-  description="Fictional scenario. Six agents need email, shared assignment and complete CSV history export. Postbox includes all three for $108 per month before tax, leaving $42 of the $150 subscription budget. Threadline costs $144 and adds chat. OwnDesk requires server operations Moss cannot supply.">
-  <Copy y={234} lines={['Six people. Email intake, shared assignment and complete CSV history export.']} color={muted} />
-  <Copy y={332} lines={['All three list the required features. Cost and operating capacity decide the shortlist.']} size={38} weight={500} />
-  <Copy x={112} y={423} lines={['Option']} size={30} color={muted} />
-  <Copy x={510} y={423} lines={['Monthly cost · six agents']} size={30} color={muted} />
-  <Copy x={1038} y={423} lines={['Fit for Moss now']} size={30} color={muted} />
-  <line x1={112} x2={1808} y1={452} y2={452} stroke={rule} strokeWidth={2} />
-  <Copy y={512} lines={['Postbox']} size={44} weight={600} color={accent} />
-  <Copy x={510} y={512} lines={['$108 subscription', '$18 × 6 agents']} size={36} />
-  <Copy x={1038} y={512} lines={['Hosted · trial first', 'Meets today’s needs; no chat channel.']} size={36} />
-  <line x1={112} x2={1808} y1={594} y2={594} stroke={rule} strokeWidth={2} />
-  <Copy y={653} lines={['Threadline']} size={44} weight={600} />
-  <Copy x={510} y={653} lines={['$144 subscription', '$24 × 6 agents']} size={36} />
-  <Copy x={1038} y={653} lines={['Hosted · conditional alternative', 'Adds chat, useful later rather than now.']} size={36} />
-  <line x1={112} x2={1808} y1={735} y2={735} stroke={rule} strokeWidth={2} />
-  <Copy y={794} lines={['OwnDesk']} size={44} weight={600} />
-  <Copy x={510} y={794} lines={['$0 software subscription', 'Operating costs unknown']} size={36} />
-  <Copy x={1038} y={794} lines={['Self-hosted · exclude for now', 'Moss cannot operate its own server.']} size={36} />
-  <line x1={112} x2={1808} y1={876} y2={876} stroke={rule} strokeWidth={2} />
-  <Copy y={936} lines={['Fictional, hand-authored specifications—not vendor research. Hosted prices exclude tax;', 'both hosted options have no setup fee. Listed features do not establish quality.']} size={30} color={muted} />
-</Canvas>;
-
-const Tradeoff = () => <Canvas number={2} title="Chat must earn its $36 monthly premium"
-  description="Postbox is $108 per month with $42 subscription headroom; Threadline is $144 with $6 headroom against a $150 budget, before tax. Trial Threadline if a concrete near-term chat workflow is valuable enough to justify the premium. OwnDesk includes chat but requires hosting, backups, upgrades and incident response with unknown costs.">
-  <Copy y={239} lines={['Both hosted options fit the $150 subscription budget before tax.']} size={38} color={muted} />
-  <Copy y={358} lines={['Postbox']} size={42} weight={600} color={accent} />
-  <Copy y={442} lines={['$108 / month']} size={64} weight={600} />
-  <Copy y={505} lines={['$42 budget headroom']} size={34} color={muted} />
-  <Copy x={982} y={358} lines={['Threadline']} size={42} weight={600} />
-  <Copy x={982} y={442} lines={['$144 / month']} size={64} weight={600} />
-  <Copy x={982} y={505} lines={['$6 budget headroom']} size={34} color={muted} />
-  <Copy y={624} lines={['Start with the current workflow']} size={40} weight={600} />
-  <Copy y={682} lines={['Postbox covers the three required capabilities.', 'Do not pay for chat on a feature list alone.']} size={36} />
-  <Copy x={982} y={624} lines={['Trial Threadline when chat has a job']} size={40} weight={600} />
-  <Copy x={982} y={682} lines={['Name a near-term chat workflow and test it.', 'Choose Threadline only if the added value', 'justifies $36/month and the final bill fits.']} size={36} />
-  <line x1={112} x2={1808} y1={847} y2={847} stroke={rule} strokeWidth={2} />
-  <Copy y={911} lines={['OwnDesk also lists chat, but Moss would own hosting, backups, upgrades and incident', 'response. With no operating capacity and unknown costs, it is not a zero-cost alternative.']} size={34} />
-  <Copy y={1014} lines={['Fictional scenario · subscription calculations for six paid agents, before tax.']} size={28} color={muted} />
-</Canvas>;
-
-const Trial = () => <Canvas number={3} title="Use the trial to test the purchase decision"
-  description="Start Postbox with a representative sample. Verify email intake and shared assignment with all six agents; reconcile a CSV export to ticket history; confirm six-agent pricing and tax. No usability, reliability or migration results are measured. Purchase only after required workflow and export checks pass; compare Threadline if chat becomes a justified need.">
-  <Copy y={239} lines={['Begin with Postbox and representative tickets, then make a go/no-go decision.']} size={38} color={muted} />
-  <Copy y={369} lines={['Verify in the trial']} size={32} color={muted} />
-  <Copy x={788} y={369} lines={['Evidence to collect before purchase']} size={32} color={muted} />
-  <line x1={112} x2={1808} y1={397} y2={397} stroke={rule} strokeWidth={2} />
-  <Copy y={463} lines={['Email + assignment']} size={40} weight={600} />
-  <Copy x={788} y={463} lines={['Send incoming email; assign and reassign tickets.', 'Have all six agents confirm ownership is clear.']} size={36} />
-  <line x1={112} x2={1808} y1={549} y2={549} stroke={rule} strokeWidth={2} />
-  <Copy y={613} lines={['Complete CSV history']} size={40} weight={600} />
-  <Copy x={788} y={613} lines={['Export the sample and reconcile it to ticket history.', 'Check records, fields and chronological completeness.']} size={36} />
-  <line x1={112} x2={1808} y1={699} y2={699} stroke={rule} strokeWidth={2} />
-  <Copy y={763} lines={['Final cost + transition']} size={40} weight={600} />
-  <Copy x={788} y={763} lines={['Confirm the six-agent quote and tax against budget.', 'Test a small migration before committing the inbox.']} size={36} />
-  <line x1={112} x2={1808} y1={849} y2={849} stroke={rule} strokeWidth={2} />
-  <Copy y={915} lines={['Buy only after required workflow and export checks pass.']} size={40} weight={600} color={accent} />
-  <Copy y={974} lines={['No measured usability, reliability or migration results exist in this fictional scenario.', 'Review reliability evidence separately; a short trial cannot establish long-term reliability.']} size={30} color={muted} />
-</Canvas>;
-
-export const meta = { title: 'Moss — choosing a support inbox', createdAt: '2026-09-12T14:20:00Z' };
-export const notes = [
-  'Recommendation based only on supplied fictional specifications, not observed product performance.',
-  'Derived arithmetic: 18 × 6 = 108; 24 × 6 = 144; 144 − 108 = 36; 150 − 108 = 42; 150 − 144 = 6.',
-  'Trial checks are proposed decision criteria, not measured results or claims about product behavior.',
-];
-export default [Shortlist, Tradeoff, Trial];

package/slides/decision-memo/PROMPT.md

@@ -1,34 +0,0 @@
-Make a three-page presentation for the operations lead at Cedar Support to help
-decide whether to extend a trial of suggested replies. Explain the trade-off
-between handling time and quality, what the evidence supports, and what the
-team should learn next.
-
----
-
-Cedar Support is a fictional customer-support team. These figures are synthetic,
-hand-authored examples rather than results of an actual trial.
-
-Two groups each handled 120 tickets during one week. Assignment was not
-randomized, and ticket difficulty and agent experience were not controlled.
-
-- Standard workflow: median handling time of 12 minutes; 108 tickets passed
-  quality review; 9 reopened within seven days of closure.
-- Suggested replies: median handling time of 9 minutes; 102 tickets passed
-  quality review; 15 reopened within seven days of closure.
-
-Quality review and reopening are separate measures: a ticket can pass review
-and later reopen. Each rate uses all 120 tickets in its group. The quality rates
-are 90% and 85%; the reopen rates are 7.5% and 12.5%.
-
-We have no raw timing observations, variance estimates, confidence intervals,
-labor costs or customer-satisfaction results. The groups cannot establish
-causality, and their median times cannot tell us total hours saved.
-
-The proposed next step is a longer randomized trial with comparable ticket
-categories and human review retained. Quality and reopen-rate acceptance
-criteria would be agreed before starting; no numerical thresholds have been set.
-
----
-
-Give it a light editorial feel, with a white background, a deep forest-green
-accent, serif headlines and clean sans-serif body text.