Skip to content

Give a travelling body a floor to travel on - #29

Merged
WWStoryMode merged 1 commit into
mainfrom
feat/floor-for-a-travelling-body
Oct 19, 2026
Merged

WWStoryMode merged 1 commit into
mainfrom
feat/floor-for-a-travelling-body

Conversation

@WWStoryMode

@WWStoryMode WWStoryMode commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

The ground grid was 6 m across — ±3 m from the origin. Against that:

One line, Kimodo 2.11 m
One line, SnapMoGen 3.89 m
Furthest ghost sibling 4.77 m
Whole baked poem, net displacement 3.63 m (docs/journal/2026-09-08-day-4.md:267)

So the body walked off its own floor, and once off it there was no ground left to read the travel against. It is 20 m now at the same 0.5 m cell — about twice the worst measured case, and centred on the origin, so only half of it lies in whichever direction the body happens to go.

Day 4's headline 9.51 m is path length, not displacement — that body ran left and then right. Path length is the trails' and the floor path's problem, not the floor's, which only has to reach as far as the body gets from the start.

The colour, and an honest note about it

The grid was painted in --line (#232732) — the hairline colour for 1px dividers between panels, chosen at desk distance. Measured against the backgrounds it actually sits on:

rendered contrast
Bench, 0.5 opacity rgb(23,26,33) 1.12 : 1
Performance, 0.22 rgb(13,15,20) 1.045 : 1
Performance, full opacity rgb(35,39,50) 1.34 : 1

That last row is why this is a colour change and not an opacity change: #232732 tops out at 1.34:1 even opaque. It is #434b5c now with #6b7689 centre lines, both a step along the house ramp between --line and --ink-faint rather than an invented colour — 1.94/1.68:1 for the floor, 3.38/2.67:1 for the origin. Deliberately under the 3:1 graphics floor, because the performance view exists to send the eye to the body and a floor that passed a text-contrast bar would compete with it.

The centre lines are new in effect: GridHelper takes a separate centre-line colour and both arguments used to be the same, so there was no origin cue at all. On 20 m of floor that is what lets travel read as distance from somewhere.

This part measured better and was judged no better by eye. It is kept because the tuning stopped, not because it was shown to help. The likely reason is that 41 lines each way converging toward the horizon is a density problem rather than a contrast one, and brightening them made that worse. Reverting to #232732 while keeping the 20 m floor is a one-line change if that is the call.

Not in this PR

  • The compare page is unchanged. Its panels pass grid: false and have always been floorless, so there was nothing there to recolour. Whether they should share a floor — which would give the travel comparison a common scale instead of a footer number — is left open.
  • No follow camera. Three mechanisms were surveyed (lazy pan on controls.target, fit-to-trajectory bounds, dead-zone follow) and all wait on seeing this from the back of a room.

What the change exposes, recorded in roadmap.md

Nothing else in the performance view travels with the body — the spotlight least of all, since style.css:531 is a radial gradient pinned at 50% 44% of the viewport, so a body at 3.9 m stands outside its own light. A camera following the pelvis would fix that without touching the data, which is a different thing from pelvis-aligning the motion and does not reopen the "displacement stays" decision. But with the ghost-cloud on it cannot be done innocently: the far siblings are where that ~75% of divergence lives. So what a follow camera should follow stays a research decision.

Verification

tsc clean; 87 pass, 0 fail. No test is added — this is a scene constant, not a decision that can be wrong without looking wrong, which is what this repo's test convention covers.

Fixture mode cannot exercise any of it. slip-away at 0.46 m is the only fixture that travels, so the change is invisible without the real workers.

What has actually been done: the change was looked at in a browser with all three models running, and the colour was judged no better by eye. That is the extent of it.

Still owed, and named rather than implied — none of these has been run:

  • a SnapMoGen line that travels, confirming the body stays over floor for its whole path
  • a Kimodo bake, confirming the accumulating whole-poem displacement stays on the floor
  • G on, confirming the 4.77 m sibling — the case that set the ±10 m — has ground under it
  • P, at projector distance rather than desk distance

The last one is the only one that can settle the colour question, and it is the judgement v4-proposal.md track 3 says not to make at a desk.

🤖 Generated with Claude Code

https://claude.ai/code/session_014yJSPiRjB5WvTH2x4LB8V6

The ground grid was 6 m across — ±3 m from the origin — while one line travels
2.11 m on Kimodo and 3.89 m on SnapMoGen, the furthest ghost sibling reaches
4.77 m, and a whole baked poem's net displacement measured 3.63 m. So the body
walked off its own floor, and once off it there was no ground left to read the
travel against. It is 20 m now at the same 0.5 m cell: about twice the worst
measured case, and centred on the origin, so only half of it lies in whichever
direction the body happens to go.

Day 4's headline 9.51 m is path length, not displacement — that body ran left
and then right. Path length is the trails' and the floor path's problem, not
the floor's, which only has to reach as far as the body gets from the start.

The grid was also painted in --line (#232732): the hairline colour for 1px
dividers between panels, chosen at desk distance. Measured against the
backgrounds it actually sits on it reached 1.12:1 on the bench and 1.045:1 in
performance, and only 1.34:1 even at full opacity, so no amount of alpha was
ever going to carry it. It is #434b5c now, with #6b7689 centre lines so the
origin is readable and travel reads as distance from somewhere. Both are a step
along the house ramp between --line and --ink-faint, measuring 1.94/1.68:1 for
the floor and 3.38/2.67:1 for the origin — deliberately under the 3:1 graphics
floor, because the performance view exists to send the eye to the body and a
floor that passed a text-contrast bar would compete with it.

That second change measured better and was judged no better by eye. It is kept
because the tuning stopped, not because it was shown to help. What this view
needs first is an opinion formed in a room, which is the judgement roadmap.md
track 3 says should not be made at a desk.

The compare page is unchanged. Its panels pass grid: false and have always been
floorless, so there was nothing there to recolour; whether they should share a
floor — which would give the travel comparison a common scale instead of a
footer number — is left open.

roadmap.md records what the wider floor exposes: that nothing else in the
performance view travels with the body, the spotlight least of all, since it is
a radial gradient pinned to the centre of the viewport. A camera that followed
the pelvis would fix that without touching the data, which is a different thing
from pelvis-aligning the motion — but with the ghost-cloud on it cannot be done
innocently, because the far siblings are where that ~75% of divergence lives.
So what a follow camera should follow stays a research decision.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014yJSPiRjB5WvTH2x4LB8V6
@WWStoryMode
WWStoryMode merged commit 50dbf16 into main Oct 19, 2026
2 checks passed
@WWStoryMode
WWStoryMode deleted the feat/floor-for-a-travelling-body branch October 19, 2026 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant