research(deepnsm-v2): Haspelmath grammar harness on frozen 8:8:8 thought ABI

[AdaWorldAPI]

Architectural correction after operator review: The SPO 8:8:8 lanes are a byte-level ALU/ISA register contract, analogous to BF16's common numeric format and TCP/IP's shared protocol, not an invitation to mint per-verse lexical meanings. An earlier branch version accidentally introduced per-verse CE64 operand palettes. That was removed. The revised harness consumes one frozen, version-identified dictionary for the whole execution epoch. This dictionary is deliberately only a fixture until an actual cross-system canonical registry and full-vocabulary indirection are specified. Spo remains a 3×u16 lexical representation; the register contract is not redefined. No claim of globally interoperable semantics until that registry is certified.

Purpose

Executable, deliberately non-authoritative Haspelmath semantic-map wiring harness for the existing DeepNSM-v2 Reading/PosSet → multi-reading FSM → certain SPO → hydrate.rs → syntax-only CausalEdge64 seam.

This is the research continuation of H12 (#1551) and the DeepNSM-v2 grammar work (#1321). It does not reassign CE64 bits, change the parser, or claim that semantic contiguity proves causality or truth.

Files

• crates/deepnsm-v2/src/haspelmath.rs: Fig. 8.1 eight-function adjacency, complete-vs-incomplete connectedness falsifier, token binder, an explicitly supplied, frozen epoch-wide u16 WordId ↔ u8 CE64 operand dictionary with version checking (fixture, not a global registry), existing hydrate consumption, preservation of alternative triples, explicit refusals and six unit tests.
• crates/deepnsm-v2/examples/haspelmath_wiring.rs: small CLI fixture, known token bindings → CE64 roundtrip at minted verse path.
• crates/deepnsm-v2/src/lib.rs: additive module export.
• .arxiv/2026-10_haspelmath-deepnsm-ce64-harness.md: annotated primary-source constraints and executable/held follow-ups.

Non-negotiable semantic fences

1. Haspelmath (2003) pp. 212–219: nodes are functions distinguished by linguistic evidence; graph edges propose adjacencies, not geometric distances. A disconnected complete multifunctional distribution contradicts this proposed map; an incomplete sample remains unresolved.
2. Spo has 3×u16 WordIds; CausalEdge64 has 3×u8 indices. No narrowing cast. The externally pinned, shared operand ABI is compulsory to interpret these research-only CE64 payloads. No per-verse or per-thought remapping. The same 8:8:8 operand bytes must have the same contract at the same sealed epoch.
3. CE64's upper 40 bits stay zero. Grammar does not mint NARS confidence, Pearl interventions, CausalEdge64 maturity, or source-root independence.
4. Ambiguous FSM alternatives stay separate from hydrated givens; parser overflow, unaddressed triples, bad form evidence, missing canonical operands and fixed-ABI overflow refuse.
5. This still calls the existing TOC-based hydrate.rs; it is not a claim to have eliminated all trees.

Verification

Tests are committed but not locally run in this session (no Rust toolchain in the isolated working container). Please let CI/future reviewer run:

cargo test --manifest-path crates/deepnsm-v2/Cargo.toml haspelmath
cargo test --manifest-path crates/deepnsm-v2/Cargo.toml --all-targets
cargo clippy --manifest-path crates/deepnsm-v2/Cargo.toml --all-targets -- -D warnings
cargo fmt --manifest-path crates/deepnsm-v2/Cargo.toml --check
cargo run --manifest-path crates/deepnsm-v2/Cargo.toml --example haspelmath_wiring

Held until separate authorization: TEKAMOLO × case morphology × 24xi4 anaphora Sudoku; source-backed CE64 writer, persistent version-scoped sidecar; end-to-end Bible performance and held-out UD accuracy. No production writer or claim of solved grammar.

Related: #1549 (independent oracle fidelity), #1551 (H12), #1555 (MeTTa polyfill), #1564 (givens/thoughts).

[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: 9f74d846-39a9-46c3-b7ae-c968988f0acf

• 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

Here are some automated review suggestions for this pull request.

Reviewed commit: 331f0bba34

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Correct the Rustdoc to require an epoch-wide palette

A consumer following this public module documentation could construct a different operand mapping for each verse by invoking run_harness separately, even though AddressedSyntax records only the ABI version and therefore cannot distinguish those mappings. The same CE64 operand byte would then decode to different WordIds across verses, directly contradicting the implementation and commit's epoch-wide interoperability contract; describe this as the single frozen epoch-wide dictionary instead.

Useful? React with 👍 / 👎.

[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-15T23:49:59.660632Z	331f0bb	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.