Skip to content

docs(weather): normalized-substrate reference — palette256 × helix360 - #917

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/jirak-math-theorems-harvest-rfii13
Aug 11, 2026
Merged

docs(weather): normalized-substrate reference — palette256 × helix360#917
AdaWorldAPI merged 1 commit into
mainfrom
claude/jirak-math-theorems-harvest-rfii13

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

What

New knowledge doc .claude/knowledge/weather-normalized-substrate.md — the product-lead / weather-AI-developer reference for the substrate, written after the operator-corrected helix arc. Docs-only; no code changes.

Every claim is graded ([G] code-verified with file:line · [G-absence] verified absent · [H] measured this session, probe not yet committed · [S] proposal), per the falsifiability rule and "no unmarked conjectures".

Contents

  • Doctrine — one arctanh core, two readings: fisher z (variance-stabilizing statistic) / fisher 2z (Poincaré-disk arc length). The stored form is normalized low-entropy, never materialized geometry — hyperbolic_depth exposed-but-uncalled is the design. Normalization is what puts unlike variables on one scale ("correlate what normally can't be correlated") and what makes u8 sufficient.
  • helix360 — golden-spiral double hemisphere, ResidueEdge (3 B) + Signed360 (6 B) wire shapes incl. the codex feat(contract): GUID decode→read-mode keystone + helix Signed360 right-size + OCR→NodeRow transcode #498 rim-sign-partition regression; the ValueTenant::HelixResidue lane (U8×6 @ offset 112) whose 2 × 24-bit reading IS wind in/out; curve-ruler hydration (endpoints only, interior regenerates).
  • palette256RollingFloor mechanics + honest loss accounting (±0.195 % span), calibration loop, the floor-version contract; DistanceLut metric-safety (128 KB, O(1)).
  • Floor scoping resolved as a policy decision (shared canonical z-floor / per-variable / hybrid) with the Lance-version-alignment proposal [S], gated by probes P2/P3/P6.
  • Measured-evidence ledger with conditions (blosc 1.27×; Lance 1.00× verbatim on 512 B rows; BF16 anomaly 97×; from≠to 90.2 % / 15.50°; wind-speed Jensen-gap non-derivability; u8 bearing ~8× under obs error) — flagged not-yet-re-runnable until probe P1 commits them as examples.
  • Ingest spec (corrected ARCO-ERA5 object name, Zarr v2 <f4, quick-vs-permanent framing), verification battery (jc vs ndarray::hpc::reliability Option<f64>-vs-0.0-sentinel divergence; Jirak rule for any significance claim), probe queue P1–P6, and the five-entry correction ledger from this arc so the next session doesn't repeat it.

Board hygiene (same commit)

  • EPIPHANIES.md PREPEND: E-HELIX360-IS-THE-NORMALIZED-SUBSTRATE-NOT-A-BIT-BUDGET-1
  • weather-substrate-poc-v2.md §0: append-only ⊘ C3 correcting the invented Zarr object name to the session-verified 1959-2023_01_10-full_37-1h-0p25deg-chunk-1.zarr

Branch note

The prior PRs from this branch (#915, #916 arc) are merged; branch restarted from origin/main per protocol (fast-forward push, no history rewritten).

🤖 Generated with Claude Code

https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi


Generated by Claude Code

…x360, meticulously sourced

New knowledge doc .claude/knowledge/weather-normalized-substrate.md: the
product/engineering reference for weather AI on the substrate, written after
the operator-corrected helix arc. Every code claim carries file:line and a
[G]/[H]/[S] grade; absences are stated as [G-absence]; measured numbers carry
their conditions and are flagged not-yet-re-runnable until the probes land.

Contents:
- Doctrine: one arctanh core, two readings (fisher z statistics / 2z Poincaré
  arc length); normalized-low-entropy is the stored form, geometry is
  hydratable on demand — hyperbolic_depth exposed-but-uncalled is design.
- helix360 precisely: 4-stage pipeline, ResidueEdge (3 B) + Signed360 (6 B)
  wire shapes incl. the codex #498 sign-partition regression, the
  ValueTenant::HelixResidue lane (U8×6 @ offset 112) whose 2×24-bit reading
  IS wind in/out, and the curve-ruler hydration principle.
- palette256 precisely: RollingFloor mechanics with the honest loss
  accounting (±0.195% span), calibration loop, the version contract;
  DistanceLut linear/from_floor metric-safety.
- Floor scoping RESOLVED as a policy decision (shared canonical z-floor vs
  per-variable vs hybrid), with the Lance-version alignment proposal [S] and
  probes P2/P3/P6 gating it.
- Per-variable weather mapping [H]; measured-evidence ledger (blosc 1.27x,
  Lance 1.00x verbatim on 512 B rows, BF16 anomaly 97x, from!=to 90.2% /
  15.50 deg, wind_speed Jensen-gap non-derivability, u8 bearing ~8x under
  obs error); economics (inbound tax once); ingest spec; verification
  battery (jc vs ndarray mirror divergence, Jirak rule); probe queue P1-P6;
  and the five-entry correction ledger from this arc.

Board hygiene (same commit): EPIPHANIES prepend
E-HELIX360-IS-THE-NORMALIZED-SUBSTRATE-NOT-A-BIT-BUDGET-1; weather plan §0
gains append-only ⊘ C3 correcting the invented Zarr object name to the
session-verified 1959-2023_01_10-full_37-1h-0p25deg-chunk-1.zarr.

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

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 923d9261-27ff-4b9e-bfe6-5bab8e799e21

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

@cursor

cursor Bot commented Aug 11, 2026

Copy link
Copy Markdown

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_360f4925-5b85-4965-9b9d-5dd27a180250)

@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review August 11, 2026 01:23
@AdaWorldAPI
AdaWorldAPI merged commit b1bcee4 into main Aug 11, 2026
2 checks passed
AdaWorldAPI pushed a commit that referenced this pull request Aug 11, 2026
Post-merge board hygiene for #917 (a CONTENT PR — new knowledge doc +
two corrections — so it carries the full merged-PR obligation, not the
hygiene-only termination clause).

- LATEST_STATE PREPEND: what #917 establishes about already-shipped code
  (no new types) — the z-vs-2z reading split, helix360 as the existing
  HelixResidue lane read 2x24 in/out, the [G-absence] pair-writer gap,
  and floor scoping resolved as an ingest policy with probes P1-P6 all
  NOT RUN.
- PR_ARC PREPEND: Added / Locked / Deferred / Docs + Confidence, with a
  provenance note recording the five-correction arc and the meta-rule it
  produced (consult-don't-guess applies to one's own prior in-session
  statements).

This commit is itself hygiene-only and therefore generates no further
board obligation (CLAUDE.md termination clause).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
AdaWorldAPI added a commit that referenced this pull request Aug 11, 2026
…arvest-rfii13

docs(board): record merged #917 — normalized-substrate reference
AdaWorldAPI pushed a commit that referenced this pull request Aug 11, 2026
…d claims

#920 merged with neither board file updated (0 references to it in either).
This is the retroactive-hygiene pattern CLAUDE.md names as an anti-pattern —
unavoidable once the PR is merged, and leaving the board stale is the worse
outcome (the rule exists because #223/#224/#225 merged with no entries).

PR_ARC_INVENTORY: prepends the #920 entry (Added / Locked / Deferred+WITHDRAWN
/ Docs / Confidence), and applies the file's own rules 3-4 to #917 — an
appended Correction line plus an updated Confidence line, never an edit to its
immutable Locked text. #917 had locked two claims #920 falsifies: that
"helix360" names something (it does not — the type is Signed360, 12 blobs all
from that session, zero deletions) and that the HelixResidue lane reads as
2x24 hemispheres = wind in/out (it does not — one Signed360 is already a
complete full-sphere direction; rim is the metric carrier, (polar, azimuth)
the render carrier).

LATEST_STATE: prepends the #920 entry with the same correction as a leading
supersession note.

Also records a measurement made after the merge, in answer to an operator
question about polar vs equatorial error rates. Signed360 angular error by
latitude, N=65536: equator 0.112 deg mean / 0.226 max; pole 3.332 / 4.998 —
a ~30x spread, best at the rim. And a correction to the premise: there is NO
resolution gain from the sign split at equal bit budget — 7-bit |y| + sign vs
8-bit over [-1,1] measures 0.99-1.02x in every band (step 1/127 vs 2/255 =
0.996x). The 256-sample codebook figures that imply a sqrt(2) gain (full
sphere cap 7.17 deg vs hemisphere 5.07) spend an EXTRA bit; at equal budget
128-on-hemisphere is 7.17, identical. What the partition buys at the rim is
sign EXACTNESS, not precision — and that is exactly where weather lives, since
a wind bearing is near-horizontal (y = 0), the regime where a centred-at-128
round loses the hemisphere (#498).

Per the termination clause, this hygiene-only commit generates no further
board obligations of its own.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
AdaWorldAPI added a commit that referenced this pull request Aug 11, 2026
…arvest-rfii13

docs(board): post-merge hygiene for #920, and correct #917's falsified helix claims
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