Skip to content

Verify large finite JavaScript numbers across Python evidence paths - #359

Merged
aruintelligence merged 1 commit into
mainfrom
codex/full-finite-evidence-20261015
Oct 15, 2026
Merged

aruintelligence merged 1 commit into
mainfrom
codex/full-finite-evidence-20261015

Conversation

@aruintelligence

Copy link
Copy Markdown
Owner

Change

  • Reproduce Python rejection of valid signed JavaScript capsules with 2**53, 1e100, and Number.MAX_VALUE.
  • Parse JSON integer tokens above the safe-integer range as binary64, matching JavaScript JSON.parse, then render tested finite numbers at JavaScript's fixed/exponent boundary. Reject non-finite results.
  • Apply the same parser to saved HTTP exchanges and offline archive/migration verification. Add a signed case where a large attention budget participates in ledger arithmetic.
  • Challenge a changed representable value and a non-finite token. Record the deliberate same-Number decimal alias (9007199254740992 vs 9007199254740993) and document that precision-critical identifiers and amounts need strings.
  • Exercise large values through a real signed loopback HTTP response, archive, migration, and exact-byte recovery.

Local evidence

  • npm test: 797 passed.
  • 32 signed capsule scenarios and 28 cross-runtime HTTP scenarios passed.
  • Archive, migration, shards, drill, repair, placement, API, upgrade, and Markdown link checks passed.
  • Exploratory comparison of 249,885 finite number samples against JavaScript serialization found zero mismatches; this is a sample, not proof of complete equivalence.

Project-authored checks do not establish independent certification or production suitability.

@aruintelligence
aruintelligence merged commit 778a0cb into main Oct 15, 2026
60 checks passed
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.

1 participant