The First Hypothesis

Your protagonist starts with their hands on the novum at Section 3a, observing, measuring, cataloguing what’s visible. The experimental phase produces data and not yet understanding, and the crucial thing to hold onto is that the data is real and will stay valid through the whole story. What’s wrong isn’t the measurements. It’s the interpretation. The framework being used to make sense of the data was built for a different kind of phenomenon, and the fit is imperfect in ways your protagonist can’t yet see.

Watch three examples run the same error in different keys.

The structural heart of this section is the bias problem. Your protagonist’s tools are the right tools for some problems and the wrong tools for this one, and the framework isn’t neutral. It determines what they can see. An astronomer looking for mathematical structure in an alien signal will find mathematical structure, and may miss everything the signal does that isn’t mathematical. The data gets filtered through disciplinary assumptions, so it confirms what the framework expects and fails to capture what the framework wasn’t built to register.

At root this is a partial-knowledge problem, the condition of all storytelling turned into the protagonist’s predicament: they don’t yet have enough information for the correct theory. And genuine novelty doesn’t announce which of your methods apply, so some approaches produce usable data and others produce noise, and the protagonist can’t yet tell which is which. That uncertainty isn’t a failure of the protagonist. It’s a feature of the situation.

It’s also where you manage a specific gap. Good first-engagement scenes let your reader perceive the limits of the protagonist’s framework even while the protagonist works confidently inside it. This is information management, the SF-specific application of the dramatic irony that Chapter 6: Technique as Execution laid out as a deliberate craft tool.

Reader and protagonist see the same events, but the reader’s accumulated context, including their fluency in genre convention, opens a different interpretive space. The heptapod circular writing accumulates on the screens while Louise’s framework is still trying to map it as a code, and a reader attuned to SF may register its significance before she can classify it. Nothing is being withheld. The gap comes from the reader’s different context, not from concealment, and that gap is the sequence’s first source of tension.

Out of the engagement comes the first coherent explanation at Section 3b, a working model that accounts for the observed data, makes predictions, and produces relief. The theory feels satisfying because it is satisfying within its frame: internally consistent, elegantly organized, capable of generating accurate predictions.

This is the hardest beat in the sequence to execute, and the reason is a craft law worth stating plainly. A theory that’s transparently wrong from the start creates no tension, because your reader can’t invest in a model they don’t believe, and a model nobody believes can’t fail in a way that matters. The initial theory has to be the kind of explanation a smart, capable person would actually build from the available evidence, and would keep as the best available explanation until new evidence forced its revision. The more compelling the first theory, the more devastating its structural inadequacy.

Contact meets that standard. After decoding the signal’s surface, the primes, the rebroadcast of the 1936 Olympics, Ellie’s team builds a model: the senders are using mathematics, the most universal language they can assume, to identify themselves and signal that they received our transmissions. The model predicts a next layer amounting to some form of greeting. The prediction is confirmed, there is a next layer, and the model looks right. What Ellie doesn’t yet know is that the model’s claim about what kind of message is completely wrong.

The Prometheus theory deserves respect for the same reason. A star configuration repeated across unconnected human civilizations, an expedition to that system, a breathable atmosphere, an engineered structure, and the theory, the Engineers created us and this is an invitation, makes every available data point cohere. It misses only the one data point that would have changed everything: why the invitation was never acted upon.

A good initial theory produces relief precisely so your protagonist can act on it, which is what makes the coming failure devastating rather than merely inconvenient. They acted on the model, the model was wrong, and something happened because it was wrong. The theory usually has allies too, the colleagues and advisors who help build it and who share the framework, which means they’re also the people whose worldview will be most shaken when it breaks.

And the theory’s blind spots are legible, in retrospect, as your protagonist’s own. Louise’s model treats heptapod as a code, which is what a linguist looking for decodable patterns sees. The Prometheus model treats the Engineers as benefactors, which is what people who badly want to believe in meaning see. The blind spot is in the seer, and the theory reveals the seer.

That’s why the initial theory is science fiction’s form of the wrong strategy. Chapter 7: The Wrong Strategy and the B-Story established it as the protagonist’s best available move, correct within its frame. In SF the frame itself is the wrong one, and the mechanism is less a psychological coping habit than a category error, human institutional frameworks applied to something that predates or exceeds them.

It’s the cognitive signature from Chapter 48: The Baseline Reality applied at full strength, the curiosity pattern and the disciplinary toolkit producing both the theory’s genuine appeal and its specific failure. Chapter 49: The Novum planted the seed that the protagonist’s first reach toward the novum was the earliest draft of this theory. The sequence now harvests it.

And the seer was established by arc.

Then the novum behaves outside the theory’s predictions in a way nobody can patch. This is Pinch Point 1 in science fiction’s specific form, and Chapter 2: The Structural Skeleton covered its general mechanics, the first real cost that turns the second act. SF’s version isn’t an external opposition arriving to fight your protagonist. The opposition is epistemological: the protagonist’s own best model meets evidence it can’t absorb.

The distinction you have to get right at Section 3c is the difference between a correctable failure and a structural one. A correctable failure, the calculation was off, the measurement was imprecise, leaves the framework intact and lets the protagonist refine within it. A structural failure, the phenomenon was misclassified, the wrong question was being asked, requires the framework to be discarded and rebuilt from better premises. Pinch Point 1 here is always the second kind.

All three failures are total. None can be patched.

The failure must be total, and the reason is structural. If the first hypothesis only needed refinement, your protagonist could refine it and the story’s central tension, the challenge of understanding something genuinely new, would resolve too early. The total failure keeps the question open and establishes that this is a phenomenon that doesn’t yield to the first model brought against it. The cost attached to the failure, a person, a relationship, a resource, an institutional position, is what turns an intellectual event into a story event with lasting weight. The wrong framework had consequences a correct framework would have avoided, and that’s the story’s first statement of what epistemological error costs in practice.

So the closing recognition reframes the whole sequence. The collapse at Section 3c isn’t the story’s first obstacle. It’s the story’s first information. Before the first engagement, your protagonist didn’t know what kind of thing they were dealing with. After the failure, they know something they couldn’t have learned any other way: the novum isn’t the kind of problem their framework was built for.

That’s a genuine discovery, and it arrives with retrospective inevitability. The sense, on a second look, is that of course the framework was aimed in the wrong direction, of course a linguist would treat first contact as a translation problem, of course seekers of meaning would read an invitation as a welcome. The failure wasn’t predictable in the moment, and it was structurally right.

The wrong hypothesis is always wrong in an illuminating direction, and that’s the chapter’s last gift to you as a writer: build the failure so that what breaks names the right question. The Prometheus framework assumed benevolent intention without evidence, so the work ahead has to engage what the Engineers were actually doing and what they were running from. Ellie’s framework misidentified the category of contact, greeting versus invitation, so the revised model has to grapple with what kind of contact this is and what it asks of the one who answers.

The direction of the failure is a map. Your protagonist carries forward a diagnostic rather than a deficit: the framework was wrong here, in this specific way, which means the right framework has to be built from different premises in a specific direction.

The investigation doesn’t end at the failure. It actually begins there, and Chapter 51: Testing the Model is the harder work that follows, running the surviving understanding against a novum that keeps behaving like it has more to reveal.