root law: hierarchy is the address space, not the ontology (+ the probe that finds its boundary)

[AdaWorldAPI]

Proposes a memory-ABI root law, and measures its corollary on shipped operators — finding a real boundary rather than confirming it.

The law

Hierarchy is the address space, not the ontology.

HHTL need not claim reality is a tree. It claims every piece of reality can be given a hierarchical address from which non-hierarchical relations can be expressed zero-copy.

The Active Directory lesson. CN=Jan,OU=Engineering,DC=example,DC=com gives Jan a deterministic home without asserting everything about Jan is ancestry — group membership, manager links and ACLs are cross-links between objects that already have hierarchical identities. The hierarchy solves where; edges solve how things relate. AriGraph, CausalEdge, EpisodicEdge, anaphora pointers, premise relations and R2IL ops can all point between HHTL-resident things without any of them being trees.

Two consequences recorded:

• HHTL sits BENEATH the V3/V4 distinction. V3 and V4 don't own the railway; they're payload/read contracts for objects that already have a home. Cleaner than "V4 may ride V3 routes."
• The brutal admission rule (also added to belief-abi-restoration: Step 1 delegation-verification audit (pure negative audit) #1006): if a datum cannot be assigned a meaningful HHTL address without using Vec position as identity, it has not been normalized into the memory ABI. arena[37] is not a semantic hierarchy — it's an implementation accident wearing an HHTL costume. That's the sharp form of what belief-abi-restoration: Step 1 delegation-verification audit (pure negative audit) #1006's recut withdrew.

The probe — PROBE-EVIDENCE-RISES-BY-GENERALIZATION-1, 7/7

Tests the corollary "evidence rises only as high in the HHTL tree as its independent support generalizes" — attractive because it deletes a metadata system (no enum Scope {Local, Regional, Global}, no global-concern score, no promotion scheduler). Globality becomes geometry.

The operators it needs already ship and were not written for this: common_prefix is the MEET and never invents an address; RowFocusMask is literally an antichain of HHTL regions with absorbing union and conservative difference; TruthValue::revise pools by evidence_weight() = c/(1−c).

Measured: support rises exactly as far as it generalizes (G1 one basin stays local; G2 three independent siblings rise to the common ancestor, pooled c=0.9444 > 0.85; G6 cross-region support rises coarser, never sideways); the operator can refuse (G7 no common ancestor across classes → None); a dissenting sibling stays addressable rather than averaged away (G4); and nothing moves (G5 children byte-identical — children stay, parent learns).

⚠ The boundary — G3, the load-bearing negative result

Geometry alone over-generalizes. One source observed through three sibling basins pools naively to c=0.9444 — bit-identical to three genuinely independent sources. The two situations are geometrically indistinguishable.

globality = geometry is true only with provenance.

Not a caveat — the constraint. The hard problem was never aggregation (NARS revises correctly already) but independence detection, which is exactly what Stamp's disjoint → revise / overlap → CHOICE guard protects, and what spo::truth's revision doc already requires verbatim: "combine two truth values with independent evidence."

Graded honestly

The universal-addressability claim is [CONJECTURE], not demonstrated — for Belief the audit found the opposite of a demonstration (zero FacetCascade occurrences in nars/). Nothing here mints a tenant, an address, or a classid. Also applies the operator's own correction: frequency is not sample count; confidence carries evidence mass, confirmed by evidence_weight().

Relation to the open PRs

This weakens the framing of #1008's entry (stream-order vs prefix-tree as an opposition) — a temporal datum can be HHTL-addressed with ±i4 offsets as local traversal inside an addressed neighborhood; layered, not rival. #1008 carries an in-place regrade saying so. Its [ABSENT] verdicts and its type-drift fence both survive — the fence is strengthened, since the right move was never to re-scope VersionRange but to give the temporal datum its own address.

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[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_429369b6-6c45-4784-9667-e41e18341856)

[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: Pro Plus

Run ID: 1281aa83-07eb-49e5-99fa-d5a126a6b78e

---

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