Observe

W01 · 4 h 20 min

What GEO is—and is not

Essential question

What is the actual object of optimization?

What you should be able to do

  1. Distinguish an object, a pipeline stage, a metric, and an outcome.
  2. Mark observable and unobservable components of a generative-search event.
  3. Frame a bounded GEO question without implying access to a closed-system algorithm.
PrerequisitesRead the course evidence-ceiling legend.Bring one answer surface or use the supplied synthetic fixture.
Builds on

Read the course evidence-ceiling legend. · Bring one answer surface or use the supplied synthetic fixture.

Investigates

What is the actual object of optimization?

Feeds

L01 system card v1 and source inventory.

Arrive with a prepared artifact

Reading route
Core PAPER-16/PAPER-19; Extend PAPER-06/PAPER-15.
Viewing route
Open the complete text-first lecture packageEight-minute course orientation: question, evidence boundary, artifact sequence. The current equivalent is notes, slide script, worked case, and no-video transcript; no recording is claimed.
Readiness check
Define retrieval and citation in one sentence each; identify one claim that a screenshot cannot support.
Bring
One completed scope card naming system, surface, locale, account state, query, time, and unknowns.

Concepts, assumptions, and boundary

The object comes before the tactic

GEO is treated here as the study and responsible intervention of source visibility in generative search systems—not as a bag of prompt or copywriting tricks. A usable research object must name a source, query distribution, system surface, response, observation window, and measurable event. Discovery, retrieval, context selection, generation, attribution, and downstream action are different stages. A source can be crawlable yet never retrieved, retrieved yet not selected, selected yet not cited, or cited without changing the generated answer. Conflating these events makes a result impossible to diagnose or reproduce.

Closed systems require epistemic restraint

A screenshot can establish what a named surface displayed at a named time under recorded conditions. It does not disclose the platform’s ranking function, training data, hidden candidate set, or causal reason for the output. We therefore separate observation, interpretation, mechanism hypothesis, intervention, and outcome in every artifact. Open retrieval sandboxes can expose intermediate variables; commercial systems usually cannot. The course uses open systems to learn mechanisms and bounded field observations to study externally visible behavior, while keeping those evidence classes distinct.

Inspect the mechanism or evidence structure

Conceptual modelSix-stage conditional visibility chain
Six-stage conditional visibility chainSix rounded nodes are connected by conditional arrows. Each arrow is annotated with a possible failure and its observable denominator. A background band marks stages that may remain unobservable in a closed platform; the caption explicitly rejects algorithm disclosure.DiscoverRetrieveSelectGenerateAttributeOutcome
Figure design. A left-to-right chain—discover, retrieve, select, generate, attribute, outcome—with a measured denominator under every arrow and a red hatched band behind hidden closed-platform stages. Every arrow is conditional; closed stages may remain unobserved.
Long description

Six rounded nodes are connected by conditional arrows. Each arrow is annotated with a possible failure and its observable denominator. A background band marks stages that may remain unobservable in a closed platform; the caption explicitly rejects algorithm disclosure.

One action, one feedback state

Action

Classify twelve statements as observation, inference, hypothesis, or guarantee.

Feedback

Each answer reveals the missing system, surface, denominator, date, or hidden-stage caveat.

Accessible alternative

A printable answer table contains the same statements and rationales.

Open the visibility-chain diagnostic

Produce a reviewable intermediate file

Task
Construct a system card and visibility-chain map for one approved public or synthetic surface.
Inputs
Scope-card template, synthetic response fixture, evidence-ceiling legend.
Timebox
70 minutes
Intermediate file
system-card-v1.json plus an annotated chain diagram
Stop condition
Stop if collection would require automation, personal data, paywall circumvention, or an unapproved account.

Why each controlled source is here

Complete, retrieve, and revise

Checkpoint
L01 system card v1 and source inventory.
Reflection
In 250 words, state the strongest claim the observation supports and three claims it cannot support.
Revision
Replace every unqualified mechanism verb with an observable event or a labeled hypothesis.
Low-compute route
Use the supplied static response, citation list, and screenshots; no live engine account is required.

Five retrieval questions

01Why is a citation not equivalent to source absorption?

A citation can be displayed even when the source contributes no source-distinctive claim to the answer; absorption needs claim-level evidence.

02What makes a GEO question bounded?

It names the object, system surface, query population, observation window, event metric, and evidence limits.

03What can one screenshot prove?

Only the recorded visible state under its documented conditions, not the hidden mechanism or population frequency.

04What is the evidence boundary for W01?

These readings frame the field and system objects; they do not disclose the current internals of any commercial engine.

05What must you submit or revise after this week?

L01 system card v1 and source inventory. Replace every unqualified mechanism verb with an observable event or a labeled hypothesis.

Continue in the practice package