# v2.4 clarification: the exact changes, for the implementing agent and for the author

**Type:** release specification (level 3: the author approves the merge) · **Date:** 5 October 2026 · **Source:** the editor's direction note (`../../lab/19_mpe_h1/99_DIRECTION_NOTE.md`), which found that the site states two opposite pairings of *this* and *that*, and the author's decision on the editor's proposal of the same day ("We can do all of these except 5", 5 October 2026), which took the note's recommendation: *this* is the orientation toward represented content, *that* the orientation toward awareness · **Editor:** Claude Opus 5.5 (wrote this wording) · **Implementer:** a Claude Sonnet 5.5 agent (mechanical edits across surfaces) · **Cap:** within the USD 8 the author approved for steps 2 to 4; one Codex call · **Branch:** `release/v2.4-clarification`, cut from `main` after the playground and Positions work has merged; nothing merges without the author

The wording below is the editor's proposal. The implementer applies it verbatim to every served surface named, keeps frozen records (lab records, prompts, quotations inside research files, reception entries, earlier changelog entries) unchanged, and makes the drift and style tests pass.

## What this release is, in one paragraph

A clarification, not a repair of an argument. The paper's Part IV says "Zen's intimacy with *this*. Advaita's dissolution into *that*." and never says which orientation each word names. The research agenda filled the gap one way, the H1 pre-registration the other. The author has fixed it: *this* is the orientation toward represented content, what appears; *that* is the orientation toward representational activity, awareness itself. No tier, confidence number, falsifier or claim node changes. The release must say plainly that the pairing was fixed **after** the exploratory H1 analysis had been seen, and that under this pairing that analysis leans slightly toward the prediction; the stated grounds for the choice are the Positions page's readings and the traditions' own usage, not the data, and no claim moves on the H1 work.

## C1. Part IV: the pairing sentence

In `site/downloads/Space_Immanence_Working_Paper.md`, `md/Space_Immanence_Working_Paper.md` and `site/paper.html`, in the paragraph that begins "The phenomenological claim is narrower than the structural one", after "Advaita’s dissolution into *that*." insert:

> Here *this* names the orientation toward represented content, what appears, and *that* the orientation toward representational activity, awareness itself (Part III, the two primitive orientations).

Keep the paragraph's existing apostrophe style (’). In `paper.html` use `<em>this</em>` and `<em>that</em>`.

## C2. The research agenda's H1 list

In `site/research.html` (the `#h1` section), `site/downloads/Research_Agenda_and_Tests.md` and `md/Research_Agenda_and_Tests.md`, replace the two list items with:

> - toward represented content / world / *this*;
> - toward representational activity / awareness / *that*.

(HTML: `<li>toward represented content / world / <em>this</em>;</li>` and `<li>toward representational activity / awareness / <em>that</em>.</li>`; Markdown keeps its current plain-word style: `this;` and `that.`)

In `site/research.html`, replace the last two sentences of the H1 status paragraph, from "The paper has not yet said" to "before any confirmatory test.", with:

> Version 2.4 states the pairing in Part IV: <em>this</em> is the orientation toward represented content, <em>that</em> toward awareness. That matches the tests’ pre-registration; until v2.4 the list above stated the opposite (<a href="downloads/lab/mpe-h1/99_DIRECTION_NOTE.md">note</a>). The author fixed the pairing after the exploratory analysis had been seen, and under it that analysis leans slightly toward the prediction. The choice rests on the paper’s other readings and the traditions’ usage, not on the data; no claim moves on these results, and a confirmatory test must be filed fresh.

## C3. The direction note: decided

Append to `research/lab/19_mpe_h1/99_DIRECTION_NOTE.md` and its served copy `site/downloads/lab/mpe-h1/99_DIRECTION_NOTE.md`, before "## What would count against this":

> ## Decided (5 October 2026)
>
> The author took the recommendation ("We can do all of these except 5", 5 October 2026, on the editor's proposal whose second step was this clarification): *this* is the orientation toward represented content and *that* toward awareness, stated in Part IV from version 2.4; the research agenda's list is corrected. The decision came after the exploratory all-codings analysis had been seen, and under this pairing that analysis leans slightly toward the pre-registration's prediction. The grounds given are the Positions page's readings and the traditions' usage; the H1 results remain exploratory, and no claim moves on them.

## C4. Version surfaces

- `site/state.json`: `version` "2.4"; `versionLabel` "v2.4"; `versionDate` "2026-10-05"; add `whatV24Is` after `whatV23Is`:
  > The clarification release: no tier or confidence moved, no claim node added. Part IV now says which orientation each of its two words names: *this* the orientation toward represented content, *that* the orientation toward awareness. The research agenda's H1 list, which stated the opposite pairing, now matches. The author fixed the pairing after the exploratory H1 analysis had been seen; the results stay exploratory and move no claim.
  (plain text in JSON: write this and that without asterisks.) Leave `changelogLatest` as the test requires (set it to "2026-10-05" if not already).
- Colophons: every page whose colophon reads "Space Immanence v2.3 · September 2026" becomes "Space Immanence v2.4 · October 2026" (including `site/lab/*.html`). Pages with a different colophon pattern: change only the version token and month.
- `site/paper.html`: `<title>` "Space Immanence — Working Paper v2.4"; kicker "Working paper · v2.4 · October 2026"; citation note "version 2.4, October 2026".
- `site/downloads/Space_Immanence_Working_Paper.md` and `md/…`: front matter `version: "v2.4 working paper"`; the line `*Version 2.3, September 2026*` becomes `*Version 2.4, October 2026*`.
- `site/claims.json` `version` "2.4". `site/llms.txt`: "version 2.4 (2026)" and "against Space Immanence version 2.4". Any `framework`/`against` version field in `site/container.json` or `site/meta-problem.json` that the drift test ties to state: follow the test.
- `site/respond.html`: kicker "Critique · v2.4"; add a release entry above the v2.3 entry, in the same format: `<h3>v2.4 — 5 October 2026</h3>` and a paragraph: "The clarification release: no tier or confidence moved, no claim node added. <strong>What changed:</strong> Part IV of the paper now says which orientation each of its two words names: <em>this</em> the orientation toward represented content, what appears, and <em>that</em> the orientation toward awareness. The research agenda&rsquo;s H1 list stated the opposite pairing and now matches; the tests&rsquo; pre-registration already used this one. The author fixed the pairing after the exploratory H1 analysis had been seen, and under it that analysis leans slightly toward the prediction; the grounds are the paper&rsquo;s other readings and the traditions&rsquo; usage, the H1 results stay exploratory, and no claim moves on them (<a href=\"downloads/lab/mpe-h1/99_DIRECTION_NOTE.md\">direction note</a>)."
- Rebuild the feed: `python3 scripts/build_feed.py`. Rebuild the paper PDF: `python3 scripts/build_pdfs.py --only Space_Immanence_Working_Paper`.
- Tests pinned to v2.3 on purpose: `test/candidate-v3.test.mjs` (`baseline.version` → '2.4'), `test/feed.test.mjs` (newest release title "v2.4 — 5 October 2026"; adjust the newest-item expectation to what the feed builder produces, and keep the assertion). Add `test/v24-clarification.test.mjs` asserting: the C1 sentence in all three paper surfaces; research.html's list pairs content with *this* and awareness with *that*, and no longer contains "awareness / <em>this</em>"; the downloads research agenda likewise; state.json version "2.4" and `whatV24Is` mentions "after the exploratory".
- `CLAUDE.md`: "Current: v2.4 (5 October 2026), the clarification release."

## C5. Not changed

Frozen: `research/lab/19_mpe_h1/00_PREREG.md` and every H1 result record; earlier changelog entries; reception entries; the floor and lab records. The Academic Edition (it does not use the words). The Code It Yourself prototype (fixed separately, before it goes live).

## What would count against this

- A passage the editor missed, anywhere in the paper, Academic Edition or Aperture Framework, that already fixes the pairing the other way; then C1 contradicts the paper and the release is wrong.
- Readers taking the timing disclosure as cosmetic: if the pairing had been chosen to favour the data, the disclosure would not repair that. The editor's recommendation was itself written after the exploratory analysis. What can be checked is the grounds: the Positions page's readings of Advaita (awareness given priority) and of Dōgen (a self actualised by the myriad things) were on the site from June and September 2026 (commits `c29006a`, `629e0c8`), before the H1 work began on 3 October 2026.
- Any surface left stating the old pairing after the sweep; the new test covers the three known ones only.