Skip to content

paper: a four-column table declared three - #3315

Merged
gHashTag merged 1 commit into
masterfrom
w117e-one-character
Sep 5, 2026
Merged

paper: a four-column table declared three#3315
gHashTag merged 1 commit into
masterfrom
w117e-one-character

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 5, 2026

Copy link
Copy Markdown
Owner

build-paper.yml has been red on master since 2026-04-14 and has never been
green.

1e482f3e  failure  Build PDF from LaTeX   <-- THE CAUSE CHANGED HERE
947d2614  failure  Build PDF from LaTeX

The two runs before those failed with no step reported at all — a start-up
failure — so the cause had already changed once, and reading only the oldest
would have sent me somewhere else entirely.

The fix

docs/WHITEPAPER/latex/main.tex:278

\begin{tabular}{lll}
\toprule
Property & IEEE 754 & Posit & GoldenFloat (GF) \\

Three columns declared. Counted per row: 4, 4, 4, 4, 4.

{lll}{llll}. One character, one file, one line.

Where it came from

Fanned tri red why across every workflow red on the default branch — 10 of
them:

recommendation count
FIX 5
LEAVE 4
RESTRICT_TRIGGER 1
DELETE / DISABLE 0

That last row is the answer to the question the sweep set out to ask: nine of
these have never once been green, and not one of them should be removed. The
adversarial stage had nothing to check, because no agent proposed removing a
check.

This PR is the cheapest of the five FIXes. The other four are recorded for
follow-up.

Refs #3270

`build-paper.yml` has been red on master since 2026-04-14 and has never been
green. `tri red why` names the current cause as "Build PDF from LaTeX"; the runs
before it failed with no step reported at all, so the cause had already changed
once and reading only the oldest would have sent me somewhere else.

`docs/WHITEPAPER/latex/main.tex:278` declares

    \begin{tabular}{lll}

while the header and every body row carry FOUR columns -- Property, IEEE 754,
Posit, GoldenFloat. Counted per row: 4, 4, 4, 4, 4.

One character.

Found by fanning `tri red why` across every workflow red on the default branch:
10 diagnosed, 5 FIX, 4 LEAVE, 1 RESTRICT_TRIGGER, and zero DELETE or DISABLE --
none of them should be removed, which was the question the sweep set out to ask.

Refs #3270

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 18:01:57 UTC

Summary

Status Count
Total Open PRs 12
PRs with Failing Checks 10
PRs with All Checks Green 2
READY 1
FAILING 10
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=ffccfa1a71cf != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit b52d4ca into master Sep 5, 2026
28 checks passed
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