board: EPIPHANIES entry for the DATAFUSION-PERIMETER proxy-substitution finding

[AdaWorldAPI]

Board hygiene owed from #871 (both #870 and #871 merged before this could land — see below).

One commit, purely additive — E-A-CHEAP-PROXY-GETS-PUBLISHED-AS-THE-QUANTITY-IT-RESEMBLES-1 in EPIPHANIES.md, 25 insertions, 0 deletions, no other files touched.

Why it's separate from #871: EPIPHANIES.md is 14,447 lines and append-only. #871 landed through the GitHub push_files API because the session's Bash permission classifier was intermittently unavailable — re-transmitting a 14K-line governance file whole through that path risked corrupting it, so the entry was written locally and held for git instead. By the time Bash came back, #871 (and its first edition #870) had both already merged, so:

1. Status line updated from "IN PR" to SHIPPED, naming both commits (a50299c, f91eeb6).
2. Added the process paragraph the entry was missing: this is the third occurrence this session of a PR merging before its review could land (feat(reasoning): concept-blind consumer seam for the medcare NARS asks #866 review-in-flight, BLOCKED (correctness) — refactor(meta_basin): lens migration fuses slice-index with stream address #868 merged while marked DO-NOT-MERGE, docs: DATAFUSION-PERIMETER.md — what a DataFusion-free build would actually cost #870 merged mid-correction-pass) — plus a fourth near-miss, docs: correct DATAFUSION-PERIMETER — two of its conclusions were wrong #871 itself merging before CodeRabbit's rate-limited review ran (@coderabbitai review came back "limit reached, next available in 46 minutes"). Sharpens the sibling entry E-A-GUARANTEE-WITH-A-RE-EXPORTED-BYPASS-IS-NOT-A-GUARANTEE-1's rule: the reviewable window is "until the operator reads it," not "until merge," and it can be zero — so correctness has to be front-loaded into the PR, not caught after.

Docs-only, no code/tests affected.

---

Generated by Claude Code

Summary by CodeRabbit

• Documentation
  • Published a new entry dated July 29, 2026, documenting corrections to measurement methodology.
  • Clarified the distinction between computational proxies and actual capabilities or implementations.
  • Updated reported counts and conclusions, including the comparison between Lance storage and a Pi-sized binary.
  • Added process timeline details and cross-references to related documentation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 511be01b-d3bf-433b-99cb-135797a06d9e

📥 Commits

Reviewing files that changed from the base of the PR and between 43680a4 and 0283ac8.

📒 Files selected for processing (1)

• .claude/board/EPIPHANIES.md

---

📝 Walkthrough

Walkthrough

Adds a shipped documentation entry describing corrected DataFusion perimeter measurements, proxy-versus-reality distinctions, revised counts, merge timing, and related cross-references.

Changes

Measurement Correction

Layer / File(s)	Summary
Corrected measurement narrative .claude/board/EPIPHANIES.md	Adds the dated shipped correction, explains proxy-versus-reality mismatches, records revised counts, and links related documentation.
Review and merge process record .claude/board/EPIPHANIES.md	Documents the interleaved review and merge timeline and defines the reviewable window rule.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: claude

Poem

I’m a rabbit with notes in my burrow tonight,
Corrections now hop into measurement light.
Proxies step back; true counts take the stage,
Merge windows are marked on the review page.
Cross-links nibble the trail neat and bright.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5a3c8b8f-10d2-4ebd-8620-d1115f177a51)