WCOJ map items 1–3: cyclic fixture, bag oracle, galloping seek_from, GYO, P-7 check

[AdaWorldAPI]

Runs the test items from the worst-case-optimal-join map (#1586) ahead of D-ASM-11. Full results are in .claude/board/entries/2026-10-16-wcoj-probes-1-3.md.

Changes

• lance-graph-contract::ordered_lane: adds gallop_partition_point, a seek that starts at a cursor and gallops forward, and SealedFacetLane::seek_from, its witnessed form.
• lance-graph-relalg::join_body: adds is_alpha_acyclic, a GYO reduction over a join body that holds only variables, no strings.
• lance-graph-metta/examples/wcoj_probe.rs:
  • the F4 cyclic fixture (2+2+2 × k);
  • a bag oracle (datafrog with counts, checked against a nested loop);
  • the P-7 check: the exact cyclic mask built from the ops that exist today.

Results

• F4: the semijoin chain keeps every row, and the query is empty.
• P-1: the bound m·(2·log₂(N/m)+4) holds.
  • The pre-registered constant was 2; the measured value at N/m = 4,096 was 26.9 against 26.
  • Galloping beats a fresh binary search below about N/m = 1,000 and a linear step above about 16.
  • So the seek wants a hybrid. The pre-registered kill condition was stated the wrong way round.
• P-3: 7 acyclic and 4 cyclic bodies are classified correctly.
• P-7: the mask can be expressed, but only as one disjunct per value, which costs rows × |D|.
  • mask-risc has no lane-to-lane compare.
  • Rule 25's insufficiency proof is therefore met.
• DuckDB: core has no worst-case-optimal join. Its ASOF join gallops from a cursor (physical_asof_join.cpp:1182).
• Bind: quack's Binder trait is the shared surface for SAP, dir-sim, report, and the planned D-ASM-1 binder.

Disable runs (each went red)

• from ignored in the seek.
• GYO forced to true, and GYO with the ear-variable step skipped.
• The tc == v conjunct dropped.
• Counts collapsed to 1 in the bag oracle.

Gates

• lance-graph-contract: 1500/1500 pass; clippy -D warnings clean.
• lance-graph-relalg: 11/11 pass; clippy clean.
• metta examples: all pass. The new example is clippy clean; join_range_probe was already failing manual_is_multiple_of and is untouched.
• Nothing was timed.

Follow-up plans (docs only, nothing built)

• .claude/plans/wcoj-closing-atoms-v1.md: spec ratified by a 5+3 council for the two closing atoms the P-7 result asks for. Pred::EqU32ViaLane handles functional relations. MaskOp::RunsMeet is a gated EXISTS over two sorted runs, for n:m relations. D-ASM-11A/B are not authorized. Council record: entries/2026-10-16-wcoj-closing-atoms-council.md.
• .claude/plans/quack-multitable-bind-v1.md: one bind path for joins, shared by MeTTa bodies and SAP (D-QMB-0..5).
• TECH_DEBT TD-NO-BOUNDED-U32-GATHER-1.

🤖 Generated with Claude Code

https://claude.ai/code/session_011BMJnDBAfzcuQh5HeT39Rh

---

Generated by Claude Code

---

Generated by Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: a2e8dc1c-cdc5-4cb3-b1f1-d3849f25b568

• Autofix · 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.

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.}

[chatgpt-codex-connector]

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-16T16:27:17.067625Z	925243f	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.