ce64 vocabulary correction · NARS/MeTTa mapping inventory · metta-datalog-assimilation-v1 plan

[AdaWorldAPI]

What

Doc-only commits, one research document, one plan; no executable change.

1. TrustTexture is the MUL vocabulary for the topology coordinate, not a second reading (7bc2f38b, d5cb9b43)

Bits 59..63 are the epistemic ladder (EpistemicState5 = Topology2 × Certification3, as the README front-page diagram and docs/architecture/ce64-semantic-upper-half.md state). The lower coordinate is the Faktorortung — Direct / IndirectKnownIntermediates / IndirectUnknownIntermediates / Unknown — and TrustTexture's Crystalline / Solid / Fuzzy / Murky are the Meta-Uncertainty-Layer names for the same four cells (Murky = Unknown). The mapping is the identity. The Proceed / Sandbox / Compass column is the MUL's reaction to a cell, not a second meaning of the bits, and a contradiction needing revision is an epistemic pothole the MUL reacts to, not a cell of the field.

site	said	now says
causal-edge/src/layout.rs TRUTH_SHIFT	"TrustTexture … legacy: no mapping into the canonical state"; "remains the canonical epistemic-trust reading"	same cells, identity mapping; prior text struck with ⊘
layout.rs SPARE_SHIFT	"Spare: reserved for sprint-12+", candidate list	certification coordinate of the ladder; name kept for source compatibility
layout.rs TrustTexture table	0b11 = Murky | Contradiction	0b11 = Murky | Unknown; contradiction = epistemic pothole
layout.rs CausalTopology doc	"EPISTEMIC-TRUST texture … correlated but not the same fact"; "historical factual provenance NOT guaranteed"	provenance is the EdgeProvenance gate (were the bits written at all), not a semantic gap; the LensMismatch gate in band_reading::project_truth is unchanged and checks the declaration, not a second meaning
causal-edge/src/lib.rs	"TrustTexture (59-60) and spare (61-63) registers"	the two coordinates of EpistemicState5
lance-graph-contract/src/epistemic_state5.rs legacy-readings para	TrustTexture lens listed with ReasoningBand as "OTHER meanings"	only ReasoningBand on 61..63 wrote other meanings
lance-graph-contract/src/band_reading.rs banner + TruthLens docs	"FOUR shipped readings … not recoverable from the bits"; Trust = "canonical epistemic-trust reading"	one reading under two vocabularies on 59-60; the unrecoverable ambiguity is on 61..63 only; project_truth still refuses a request for the other vocabulary

No class in the tree declares either TruthLens variant (.band_reading( has no production caller; project_band is reached only by the obsolete reasoning_band_probe), so the over-refusal the old prose implied for Trust-declared classes was never live.

2. Mapping inventory (600b74b4)

.claude/research/2026-10-15-nars-metta-ce64-mapping-inventory.md, read from source (hyperon-experimental 3f76dc4, PeTTa 1d19a1d, ONA dc4efd0, opennars Java 4d1bdb0, Narsese.rs 16d4d18) against causal-edge, lance-graph-contract, planner/nars, lance-graph-nal, -relalg, -metta and OGAR ogar-loco. Changes no meaning of any atom, proposes no byte. Headline rows: no foreign system carries a 59..63 or a 40..42; lance-graph's abduction/induction argument order matches OpenNARS Java while ONA and PeTTa use the swapped convention; ONA's ATOMS_MAX = 255 fits the u8 S/P/O palette; Narsese.rs already holds the parser lance-graph-nal needs; the single most unblocking gap is relalg join + μ.

3. Plan: metta-datalog-assimilation-v1 (2da8f437, D-ASM-0 only)

.claude/plans/metta-datalog-assimilation-v1.md: umbrella over D-MTP-2/3/5/6, D-RA-3/4 and D-NALP-4/5/7 toward one target — MeTTa/PeTTa atoms assimilated into a Datalog AST held as relalg values, executed through R2IL/mask-risc, with Hyperon, PeTTa and datafrog as oracles and ONA/OpenNARS for NAL truth. Adds only what no plan names: binder (D-ASM-1), join as D-CMR-5 preimage (D-ASM-2), bag terminal (D-ASM-3), LanceSpace + three-way harness (D-ASM-4), ONA-shaped 64×u8 compound-term tenant that would lift ledger R10 (D-ASM-5), rule catalogue as data with engine argument-order tags (D-ASM-6), mining seam reserved for a lance-graph-cog driver tier (D-ASM-7). Nothing beyond D-ASM-0 is authorized; /5plus3 before non-probe code. Board: INTEGRATION_PLANS prepend, STATUS_BOARD D-ASM section, entry, indexes regenerated; append_only_gate OK; supersession index current.

Gates

• cargo test -p lance-graph-contract --lib -- epistemic_state5 12/12, -- band_reading 13/13
• cargo test --manifest-path crates/causal-edge/Cargo.toml --all-features all green
• cargo clippy -p lance-graph-contract --all-targets -- -D warnings clean; cargo fmt --check clean on both crates
• cargo doc: the one band_reading.rs warning (ClassView::band_reading link) is pre-existing on main
• entries_index.py --check green (346 rows); append_only_gate.py OK; supersession_index.py output identical to the committed file

Not touched (ledger/plan prose carrying the older framing, for a follow-up if wanted)

.claude/knowledge/causal-plane-inventory.md:55 ("two ordinal-identical readings"), docs/TYPE_DUPLICATION_MAP.md:15 ("Pearl-3 epistemic lens"), and the historical plans (dismech-causality-v3-v1.md:141 "three lenses", causaledge64-mailbox-rename-soa-v1.md:57 "Murky/Dissonant"), plus the append-only board/research ledgers.

🤖 Generated with Claude Code

https://claude.ai/code/session_017SNHxJYC1MeW3HsyhGZo1E

[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: fdb7d862-6565-44d2-a4b0-46432710ce26

• 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-15T23:47:29.564257Z	7bc2f38	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7bc2f38b54

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