Skip to content

osint/p6: 2³ Pearl decomposition from a real COCA parse (D-DNV-2)#644

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/v3-substrate-migration-review-o0yoxv
Jul 4, 2026
Merged

osint/p6: 2³ Pearl decomposition from a real COCA parse (D-DNV-2)#644
AdaWorldAPI merged 1 commit into
mainfrom
claude/v3-substrate-migration-review-o0yoxv

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

D-DNV-2 of the DeepNSM→V3 convergence plan. #624 proved the SPO→CausalEdge64→2³ pieces separately (P2 packed PRNG palette indices; P3b ran all_projections on hand-set cells). This probe composes them into one end-to-end path from real text:

real COCA text
  → Vocabulary::tokenize        (real COCA word ranks)
  → Parser::parse (FSM)          → real SpoTriple (S, P, O)
  → rank → centroid → CausalEdge64::pack_v2   (the edge)
  → SpoHead → SpoDistances::all_projections   (the 8 Pearl masks)

Two tests, both grounded in a real parse:

Honest scope

The only stand-in is the distance palette — the trained centroid codebook is future work (E-V3-DEEPNSM-IS-THE-ENCODER-NOT-A-MIGRATION-1); the S/P/O identity landing is real, produced by the shipped FSM on the committed COCA CSVs (crates/deepnsm/word_frequency/), so the load is CI-safe. The rank→centroid map (rank & 0xFF) is the documented stand-in for codebook(word) until the codebook is trained.

Verification

cargo test --manifest-path crates/lance-graph-osint/Cargo.toml --test p6_real_coca_2cube2/2 green. p6_real_coca_2cube.rs is fmt + clippy clean.

Pre-existing 1.95-toolchain clippy debt in sibling probes (p3b erasing_op on 0 * 256, a few unused imports) is left untouched — lance-graph-osint is a workspace-excluded crate (not in the main CI clippy gate), and that debt predates this change. STATUS_BOARD: D-DNV-2 → In PR (D-DNV-1 → Shipped).

🤖 Generated with Claude Code

https://claude.ai/code/session_01MLBnPuScZy6w9di2QEjsXM


Generated by Claude Code

Composes the pieces #624 proved separately into one end-to-end path from
text: real COCA Vocabulary → FSM parse → real SpoTriple → CausalEdge64
pack_v2 → SpoHead → SpoDistances::all_projections (the 8 Pearl masks).

p6a: a real FSM-parsed S/P/O identity round-trips the CausalEdge64 carrier
     unchanged (extends P2's PRNG-index round-trip onto real words).
p6b: the 8 projections run over a head built from a real parse; the 2³
     ladder is monotone and the counterfactual (SPO) dominates (extends
     P3b's hand-set-cell amortization onto a real-derived head).

The only stand-in is the distance palette — the trained centroid codebook
is future work (E-V3-DEEPNSM-IS-THE-ENCODER-NOT-A-MIGRATION-1); the S/P/O
identity landing is real, from the shipped FSM on committed COCA CSVs, so
the load is CI-safe. STATUS_BOARD: D-DNV-2 → In PR (and D-DNV-1 → Shipped).

Verified: cargo test --manifest-path crates/lance-graph-osint/Cargo.toml
--test p6_real_coca_2cube — 2/2 green; p6 fmt + clippy clean. Pre-existing
1.95-toolchain clippy debt in sibling probes (p3b erasing_op, unused
imports) left untouched — osint is a workspace-excluded crate, not in the
main CI clippy gate.

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

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: ddda94c1-41f4-4c93-9ad9-ffcbc1c0c0af

📥 Commits

Reviewing files that changed from the base of the PR and between 0ac5eb9 and e033397.

📒 Files selected for processing (2)
  • .claude/board/STATUS_BOARD.md
  • crates/lance-graph-osint/tests/p6_real_coca_2cube.rs

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

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

@AdaWorldAPI AdaWorldAPI merged commit 7384bc3 into main Jul 4, 2026
7 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.

2 participants