PROBE-ORACLE-FUNNEL Stage 0: pre-registration + measured results + the legend-is-not-the-grammar finding

[AdaWorldAPI]

What this is

The consumer-side record of PROBE-ORACLE-FUNNEL Stage 0 — the first measurement over the ogar-loco funnel the wishlist delivery (OGAR #244) unlocked. Docs/board only; no Rust code changes here. The harness itself lives OGAR-side (PR #245) per the no-cross-dependency ruling in the merged handover: candidates and legends cross as data, never as a crate edge.

Contents

• .claude/plans/oracle-funnel-probe-v1.md (new) — the staged probe plan. §1–§4 are the pre-registration (three deterministic arms R/G/W bracketing what an LLM could emit; expectations E1–E4 including the E4 discrimination KILL at a 50-point bar; the Stage 1 LLM arm and Stage 2 Gadamer-bag arm both explicitly gated), written before the run. §5 is the measured result, appended after.
• Results: E1–E4 all met. Floor (uniform bytes) 0.5% survival; legend-constrained 2.5%; stack-aware walk 100%. Spread 99.5 points — the funnel discriminates, so the Stage-1 LLM arm is justified on this vocabulary (still gated on operator word + API).
• EPIPHANIES.md — E-THE-LEGEND-IS-NOT-THE-GRAMMAR-1 (FINDING, measured): the mid-model arm landed at the floor, not midway. Knowing the full vocabulary table buys almost nothing; ~all of the funnel's selectivity is the stack discipline. Stage-1 consequence: the prompt must teach the postfix discipline (or constrain decoder-side) — the ~382-token legend alone is nearly worthless. Also: the per-gate refusal distribution is a diagnosis channel (Uncovered = doesn't know the vocabulary; Underflow = doesn't know the grammar), still inside W-4's raw-loopable validity half.
• STATUS_BOARD.md — S0 row MEASURED; S1 (rig LLM arm) and Stage-2 PROBE-GADAMER-BAG rows recorded as GATED.
• AGENT_LOG.md — main-thread run entry (pre-register → build → run → record order kept).

Cross-refs

• OGAR PR tech-debt: Frankenstein blast radius breadcrumbs (Vsa10k / L3 / 157) #245 — the deterministic harness (ogar-loco example), gates green.
• OGAR D5 Trajectory + MarkovBundler + board hygiene for categorical-algebraic inference #243/plan: VSA precision tiers, father-grandfather compression, DU-4/DU-5 shipped #244 — the wishlist handover and its same-day delivery (W-1/W-2/W-4/W-5) this probe consumes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@AdaWorldAPI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6cd45830-7ea5-4656-88d4-0e405379989f

📥 Commits

Reviewing files that changed from the base of the PR and between 75acb67 and e4967e3.

📒 Files selected for processing (4)

• .claude/board/AGENT_LOG.md
• .claude/board/EPIPHANIES.md
• .claude/board/STATUS_BOARD.md
• .claude/plans/oracle-funnel-probe-v1.md

---

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_1b0282fc-3ccd-4f1b-bc69-ce2cba347067)