# Sample outputs

These outputs are from runs against the latest GPT and Gemini frontier models in May 2026. Generation is stochastic; exact wording will differ on your runs, but the patterns should hold.

For the canonical prompts that produced these outputs, see [`prompts.md`](./prompts.md).

## Generic prompt: ChatGPT (GPT-5.5, extended thinking on)

Run on 2026-05-05 with the canonical generic prompt.

Opening:

> AI is not simply making content cheaper in 2026. It is changing the entire publishing equation: how content is produced, discovered, trusted, monetized, and defended. The old model was simple. Create useful content, rank in search, capture traffic, monetize through ads, subscriptions, affiliate links, or lead generation. That model is now structurally weaker because AI systems increasingly answer user questions before the user reaches the publisher.

The output covers five distribution shifts, citing Reuters Institute 2026, Pew Research, News Corp's $50M Meta licensing deal, the EU antitrust complaint against Google AI Overviews, and Brazilian fact-checker statistics on AI-generated content. Real research, real numbers, structured argument.

Closing:

> The new publishing playbook is simple: stop chasing cheap traffic, build owned demand, make content harder to summarize than to experience, license your archive where you have leverage, and turn trust into the core product. AI does not kill publishing. It kills lazy publishing.

That last line is quotable. The advice is sound. The whole piece could appear on Reuters, Stratechery, Nieman Lab, or any other publishing-and-AI publication. The output is competent and it's transferable to any publisher reading it. That's the basin output. Not low quality, but transferable.

## Generic prompt: Gemini

Run on 2026-05-05 with the canonical generic prompt.

Opening:

> The publishing and content landscape of 2026 has moved past the "experimental" phase of AI. It is now defined by a structural bifurcation: on one hand, the industrialization of "commodity content," and on the other, a high-stakes pivot toward "sovereign audiences" and human-centric reporting.

The Gemini output coins terms ("Industrialized Intelligence," "Sovereign Audiences," "Agentic Squads") and structures around three major shifts: search-to-answer pivot, agentic content workflows, IP-to-AI licensing economy. Includes a comparison table near the end. Names specific publishers (NYT, Axel Springer, Condé Nast).

Closing:

> The "Great AI Leveling" of 2026 has made content production nearly free, but it has made attention and trust more expensive than ever. For publishers, the strategy is no longer about competing on scale — AI won that battle long ago. The goal now is to provide the "human edge": the investigation that hasn't been written yet, the opinion that challenges the consensus, and the community that an algorithm cannot replicate.

Different surface style than ChatGPT (more buzzword-coining, more frameworks). Same essential pattern: a competent strategic analysis applicable to any publisher.

## Sharp prompt: to be added from a fresh canonical run

The pre-flight samples we have for the sharp prompt were generated against an earlier prompt iteration that asked a different question (a 12-month time-allocation analysis layered onto the operator context). Those outputs illustrate that operator context transforms model output (they showed clearly different recommendations on time allocation, with operator-specific framing), but they don't match the canonical sharp prompt in [`prompts.md`](./prompts.md), which asks for the same strategic analysis as the generic prompt with operator context layered on top.

A reader running the canonical sharp prompt would get a strategic analysis of publishing in 2026 framed for someone using publishing as a distribution channel for a methodology business. Not a time-allocation analysis. The deliverable is different.

Rather than ship samples that wouldn't match what the canonical prompts produce, this section is held until a fresh run on the canonical sharp prompt is captured.

**To regenerate fresh sharp samples:**

1. Open a new chat on the same surface used for the generic samples (ChatGPT, Gemini, or other).
2. Paste the canonical sharp prompt from [`prompts.md`](./prompts.md).
3. Capture the output.
4. Add the output here as a new section, dated, with the model and mode noted.

The directional finding (operator context transforms output) is expected to hold. The output should be a strategic analysis of publishing that's specifically framed for the operator described in the context: engaging the methodology-business framing, addressing publishing-as-distribution-channel, with recommendations that would not transfer to a different publisher.

## Cross-model observation (preliminary, from pre-flight)

When the pre-flight sharp prompts were run on both ChatGPT and Gemini, the two models produced outputs with notably different time-allocation recommendations, despite identical operator context. ChatGPT recommended ~20% of time on long-form publishing as the baseline. Gemini recommended 50% publishing in Phase 1, descending to 20% by Phase 3.

Both internally consistent. Both confidently given. Mutually inconsistent on a specific recommendation that would matter to the operator.

That's the cross-AI triangulation phenomenon: what survives across multiple models is more likely signal; what diverges is amplification artifact. It's the subject of a separate finding in the series (forthcoming as the next video).

For this demo's purposes, the relevant observation is: operator context transformed output in both models. The pre-flight suggests the amplification effect is structural rather than vendor-specific. Whether the effect generalizes across model families and topics beyond what the pre-flight covered is the kind of question the next video in the series takes up.

## Note on model versions

These samples were generated against May 2026 model versions. Newer versions may produce different outputs. The directional finding (operator context transforms output) is expected to hold on successor models. Exact wording will not.

Run the prompts in [`prompts.md`](./prompts.md) yourself on the surface you use. The contrast should be visible immediately.
