Skip to content

"SOLVED" was a note to a reader of the previous page - #283

Merged
dhobi merged 1 commit into
masterfrom
docs/drop-the-solved-tags
Aug 23, 2026
Merged

"SOLVED" was a note to a reader of the previous page#283
dhobi merged 1 commit into
masterfrom
docs/drop-the-solved-tags

Conversation

@dhobi

@dhobi dhobi commented Aug 23, 2026

Copy link
Copy Markdown
Owner

Asked what the — SOLVED tag in mov.md meant — whether it documented a bugfix process. It documents neither a process nor a property of the format. It means this page used to say something else.

Where it came from

A sound can name the frame that follows it — SOLVED got the tag in 29d75db, whose own commit message says why:

docs/formats/mov.md had described the field and concluded "no shipped movie uses the jump field", which is what made this a shipped bug: measured, 30 records across the six editions use it, all of them this one film.

That bug is #2 — the pocket watch playing 6.97 s of a 27.1 s monologue and then parking on the frame for ever.

A movie carries its own pacing — SOLVED, out of the demo build's engine predates the squashed initial import, but its body has the same shape: "The port derived a frame rate from the soundtrack for years. It did not have to."

So the tag is addressed to somebody who read the previous version of the page. There are exactly two in the whole doc set and no OPEN / UNSOLVED / UNKNOWN counterpart anywhere, which leaves a reader today asking which of the other twenty sections are unsolved. The answer is none of them — there was never an axis.

What changed

Tags dropped; the history kept where it belongs.

The pacing section already opened with its own history, so it only needed the recovery folded into the prose. The sound section was missing the better half of the story, and now has it — the page did not merely fail to know, it published the opposite:

This page is why. It described the field and then concluded that no shipped movie used it, so the port dropped it — and a documented wrong answer is worse than a documented gap, because nothing goes looking for it. Measured, 30 records across the six editions use the field, all of them this one film.

This also shortens an anchor that has broken twice already: six links pointed at #a-movie-carries-its-own-pacing-—-solved-out-of-the-demo-build-s-engine, an em dash and an apostrophe inside a slug. All six updated to #a-movie-carries-its-own-pacing.

What it deliberately does not do

Strip the voice. ## The behaviour rules that took a while to pin down is a sibling heading and stays — that is prose about the subject. — SOLVED was a tag about the document.

Docs only. Build clean, every anchor and link resolving.

🤖 Generated with Claude Code

Two headings in mov.md carried a `— SOLVED` tag, and the question of what it
meant has an exact answer: it is not a claim about the format and not a record
of a fix. It means THIS PAGE USED TO SAY SOMETHING ELSE.

`A sound can name the frame that follows it` got the tag in 29d75db, whose own
message says why: the page "had described the field and concluded 'no shipped
movie uses the jump field', which is what made this a shipped bug". That bug is
#2 — the pocket watch playing 6.97 s of a 27.1 s monologue and then parking on
the frame for ever. `A movie carries its own pacing` predates the squashed
import, but its body is the same shape: the port derived a frame rate from the
soundtrack for years and did not have to.

So the tag is addressed to somebody who read the page before, and there are
exactly two of them in the doc set with no OPEN or UNSOLVED counterpart
anywhere — which leaves a reader today asking which of the other twenty sections
are unsolved. The answer is none of them; there was never an axis.

Dropped, and the history kept where it belongs. The pacing section already
opened with its own ("derived a frame rate for years"), so that one only needed
the recovery moved into the prose. The sound section was missing the better half
of the story, which is now in it: the page did not merely fail to know, it
published the opposite, and a documented wrong answer is worse than a documented
gap because nothing goes looking for it.

This also shortens an anchor that had broken twice — six links pointed at
`#a-movie-carries-its-own-pacing-—-solved-out-of-the-demo-build-s-engine`, an em
dash and an apostrophe in a slug. All six updated.

What this deliberately does NOT do is strip the voice. `## The behaviour rules
that took a while to pin down` is a sibling heading and stays: it is prose about
the subject. `— SOLVED` was a tag about the document.

Docs only. Build clean, every anchor resolving.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dhobi
dhobi merged commit 812bd78 into master Aug 23, 2026
2 checks passed
@dhobi
dhobi deleted the docs/drop-the-solved-tags branch August 23, 2026 14:59
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