Withdrawn (repository-boundary violation) - #976
Conversation
The report-before-code deliverable. Twelve sections, every number carrying the command or file:line that produced it; anything not personally measured is labelled "claimed, unverified". Two findings correct the board itself, and both get their own entry: E-HHTL-IS-MINTED-IN-THE-ARTIFACT-NOBODY-CITES-1 — the standing claim "HHTL is zero on every baked row in both production bakes" is precise about the two artifacts it names and silent about a third. Measured on the pinned bytes: obo-core.soa 0/68,797, spine.soa 0/7,641, but all-lanes.soa 164,031/770,360 (21.29%), with MONDO/HPO/UBERON/PATO/ICD-10-GM/OMIM at 100%. Those are exactly the namespaces a DisMech overlay grounds against, so HHTL is available or unavailable depending on which artifact a reader names — a first-class design decision, not a detail. The generalization error is the transferable part: two citations counting the same 68,797 rows is ONE measurement reported twice. E-THE-ORACLE-POPULATION-IS-64-PERCENT-AND-A-GATE-HARDCODES-THE-OTHER-36-1 — only 2,449 of 3,825 INDIRECT_KNOWN_INTERMEDIATES edges actually name an intermediate (three independent methods agree). The supervision corpus is 2,449 edges over 534 diseases, not 3,869; and 74 INDIRECT_UNKNOWN edges DO name mediators, so they must leave any restraint control. The gate that should have caught this asserts == 3.869 and cannot pass on any corpus revision; its own rule is "stoppen und melden, nicht die Zahl anpassen", so this is the report rather than an edit. The structural headline: the substrate is read-rich and write-empty at four independent layers — CE64 bits 53-63, CausalEdgeV3, CausalWitnessFacet and the dismech_evidence module that landed yesterday — every one with rich read machinery and zero production writers. Hence the sequencing rule in D-CV3-*: the benchmark (0..2) must be green before a HoleV3 tenant (3) exists, or the tenant becomes the fifth entry in that column. Board hygiene in the same commit per the rule: plan file, INTEGRATION_PLANS prepend, two EPIPHANIES entries, seven STATUS_BOARD rows.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 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. Comment |
Bugbot couldn't run - usage limit reachedBugbot 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_da8c7506-dc74-482a-bcb5-b369e35ed170) |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f66f092c51
ℹ️ 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".
| | **D-CV3-0** | Pin the corpus (checksum + fetch entry). Emit the three frozen TSVs from a typed parse. **No new types.** | Re-running on a fresh container reproduces 2,449 / 4,076 / 361 **exactly**, or the pin is not a pin | | ||
| | **D-CV3-1** | Splits A + B as committed artifacts (534 disease groups) | Group-disjointness test: no disease appears in both sides of B. Anti-vacuity: held-out share is 15–25%, not ~0 | | ||
| | **D-CV3-2** | Level-0 scorer: Recall@K + MRR + abstention. Structural only | Must produce a NON-trivial number on both arms; a scorer that abstains always, or never, fails its own can-fire/can-stay-silent pair | | ||
| | **D-CV3-3** | `HoleV3` as `ValueTenant = 16` (`BoardAggregates` already reserves 15), `awareness_state` ⟂ `unknown_kind`. **Not in CE64 — it has zero free bits** | Field-isolation matrix per I-LEGACY-API-FEATURE-GATED; `ENVELOPE_LAYOUT_VERSION` unchanged (292 B headroom); a round-trip that proves the two axes are independent | |
There was a problem hiding this comment.
BoardAggregates is only reserved in a comment: the current ValueTenant enum and VALUE_TENANTS table end at CausalWitness = 14, and the compile-time contract requires every descriptor's ordinal to equal its contiguous table index. Consequently, D-CV3-3 cannot independently append HoleV3 = 16; it must first land tenant 15 or add it in the same change, despite neither dependency appearing in this sequence. Gate this step on the BoardAggregates deliverable or explicitly include materializing the reserved slot in its scope.
Useful? React with 👍 / 👎.
…e preferred one Operator: "Obo HHTL ist meines Wissens mit zipper bereits indirekt hydriert." Verified — and the correction compounds the entry's own lesson. rails::HhtlMode::of_row PREFERS the RailHead reading and falls back to Cascade only when the rail register is empty. The report counted cascade tiers (bytes 4..10), i.e. the fallback path. Measured on the four Zipper rail registers (rails.rs:130-147): MONDO 32,094/32,095, HPO 19,835/19,836, UBERON 14,973/14,975 plus 8,525 part_of (the only lane carrying mereology, matching graph_feed.rs:730's "UBERON only"), PATO 1,886/1,887 — median logical-DN depths 6/7/8/5, and 264 rows exceeding 12 levels so the continuation slab is load-bearing rather than hypothetical. obo-core.soa and spine.soa are zero on BOTH readings, so the original finding holds for those two artifacts; it was simply not the whole hydration story. New, and not visible from the cascade census: cascade and rail are INDEPENDENT. Orphanet (14,063 cascade rows) and OMIM (18,712) carry zero Zipper DN, so a consumer expecting prefix containment on a RailPath gets depth 0 there, silently, while a HhtlMode consumer gets the cascade arm. Consequence for the ladder: the HHTL rung is available at ~100% for MONDO/HPO/UBERON/PATO via RailHead — precisely the namespaces DisMech grounds against — and a ladder level must now declare its READING, not only its artifact. The two-reading design is operator-ruled: RAIL_OFFENE_POSTEN Posten 1, ENTSCHIEDEN 2026-08-12, "Register als Zeuge", re-bake unblocked.
Withdrawn — repository-boundary violation.
This pull request's original title, body and commits mixed content belonging to a private repository into this public one, contrary to the separation-of-concerns rule in
CLAUDE.md. The branch has been deleted, the pull request closed, and the title and body scrubbed.Nothing from it reached
main.Note for anyone auditing this: scrubbing is not erasure. GitHub retains pull-request edit history, the original commits remain reachable by SHA, and the automated review comments on this pull request quote the withdrawn material. Only a purge by GitHub Support removes those.
The work itself is not lost; it belongs in the private repository and is being re-homed there.