Skip to content

coresearch: "CE64 is like BF16 for thinking" — exploration map + 5 .arxiv harvests - #1423

Merged
AdaWorldAPI merged 4 commits into
mainfrom
ccr-bd5a6e03-niaink
Oct 9, 2026
Merged

AdaWorldAPI merged 4 commits into
mainfrom
ccr-bd5a6e03-niaink

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

This PR adds research notes only. No code changes, nothing adopted.

  • .claude/board/entries/2026-10-08-coresearch-ce64-bf16-for-thinking.md: the exploration map from a /coresearch council (premise gate, 5 scouts, 3 co-architects, a 21-row crosswalk, verdicts, pre-registered probes).
  • .arxiv/: five papers, each read in full and written up in the existing harvest format (punchline, what it establishes, mapping, kill condition). They are 1905.12322 (BF16), 2209.05433 (FP8), 2603.24161 (limited-precision stochastic rounding), 0712.1182 (Jøsang, cumulative/averaging fission) and 2310.10537 (microscaling).

Headline findings

  • The premise gate split the question. CE64 is a tagged instruction word, not a number format. "BF16 for thinking" fits only the F/C truth bytes (bits 24..39), with the truth functions as their ALU. Bits 46..49, 50..52 and 53..58 mean different things in the code than in the infographic: the opcode, per-plane plasticity flags, and a corpus handle.
  • Bits 40..42 are a subset lattice, not a ladder. SO = 0b101 and PO = 0b011 are incomparable (pearl.rs), so a "rung ≥ k" predicate over that field is ill-posed.
  • c = 255 needs a policy decision, not a float fix. Revision has an exact integer form in the u8 codes, and at c1 = c2 = 255 that form is 0/0 even in exact arithmetic. An f32 model of revision also found two exact .5 ties, so the rounding mode matters. This was checked in numpy; a Rust probe is still owed.
  • Revision is cumulative fusion. Following Jøsang, cumulative fusion is only valid for independent evidence; for dependent evidence the idempotent averaging rule applies. The missing stamp gate is why revising an edge with itself raises c.
  • D-RPF-4 needs no new opcode. Its weighted sum can be a per-byte c→w lookup feeding the existing strided group-sum.

Each idea is graded ADOPT-NOW, PROBE, PARK or SKIP, and every probe has a kill condition. The operator picks which to run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01R2EuNHrariL6B3G3agyASK


Generated by Claude Code

… map)

Premise split: CE64 is a tagged instruction word; the BF16 analogy holds
for the F/C truth bytes (24..39) only. Five scouts, three co-architects,
21-row crosswalk with ADOPT-NOW / PROBE / PARK / SKIP verdicts and
pre-registered probes. Nothing adopted; no code changed.

Notable: revision has an exact integer form in the u8 codes and the
c=255+255 case is 0/0 even in exact arithmetic (a policy cell, not a float
bug); bits 40..42 are a plane-subset lattice (SO, PO incomparable), so a
rung threshold over them is ill-posed; revision is cumulative fusion, so
the missing stamp gate is what lets self-revision double-count.

.arxiv harvests (read in full): 1905.12322 BF16, 2209.05433 FP8,
2603.24161 limited-precision stochastic rounding, 0712.1182 Josang
cumulative/averaging fission, 2310.10537 microscaling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R2EuNHrariL6B3G3agyASK
@coderabbitai

coderabbitai Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 76a315ed-4fbe-4926-b9f7-860d0789ffbd
📥 Commits

Reviewing files that changed from the base of the PR and between 083b71e and 448d733.

📒 Files selected for processing (7)
  • .arxiv/0712.1182_fusion_needs_to_know_whether_evidence_is_independent.md
  • .arxiv/1905.12322_narrow_storage_wide_accumulate_round_once.md
  • .arxiv/2209.05433_special_values_are_declared_not_computed.md
  • .arxiv/2310.10537_shared_scale_lives_outside_the_element.md
  • .arxiv/2603.24161_stagnation_is_a_rounding_property.md
  • .claude/board/entries/2026-10-08-coresearch-ce64-bf16-for-thinking.md
  • .claude/board/entries/README.md
 ____________________________
< The OG: Original Grepster. >
 ----------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


Comment @coderabbitai help to get the list of available commands.

claude added 3 commits October 8, 2026 22:52
Sorts every idea into decided-and-testable work, open measurements with
kill conditions, and blockers (decisions, missing primitives, censuses).
Corrects X4: NarsTables is used by the planner (NarsEngine default
c_levels=1 makes revision confidence-blind; chain_admission replays with
it), and "four quantisers" is a lower bound (37 files define revise/revision).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R2EuNHrariL6B3G3agyASK
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R2EuNHrariL6B3G3agyASK
@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review October 9, 2026 03:46
@AdaWorldAPI
AdaWorldAPI merged commit 4eb2734 into main Oct 9, 2026
3 of 4 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T03:46:45.663887Z 448d733 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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.

2 participants