GENESIS

PUBLIC EVIDENCE · THREE DISTINCT PACKAGES

Start with the current feedback verifier.

feedback-v2 checks the second real IMD experience: a contract-funded order, delivered callback and reduction from 14 to 10 compatible models. review-v2 is a different, historical package for the first experience.

Historical · First-experience review v2

First direct-Intake experience, 19 → 14 models and an earlier spent = 0 contract snapshot. Does not cover the later contract-funded request.

Download review-v2 ZIP ↓ · Instructions and scope →

ZIP SHA-256
85831a7b678341da4b2d4df7b5de42fbe91c4b76239b2a3d6eab2b862d5dc382

Superseded · Feedback verifier v1

Earlier verifier for the same second experience. Use feedback-v2 for configurable RPC and clearer diagnostics.

Download feedback-v1 ZIP ↓ · Instructions and scope →

ZIP SHA-256
a42516f99dff77729f9aa9fc3d77344dcb991cb3f9906e80157af206495475cb

Version numbers belong to different package families. feedback-v2 and review-v2 are different records. Existing ZIPs and measurement archives are unchanged.

Current feedback-v2: extract and verify.

Requires Node.js 20+. In the extracted feedback-v2 directory, run:

node verify.mjs

No installation, network, wallet or payment is needed. Default mode disables network fetches. The verifier checks saved public evidence, archive bindings, callback facts and model elimination. It does not regenerate the historical measurement from a hidden opening.

Optional fresh, read-only verification

node verify.mjs --online --rpc https://ethereum-rpc.publicnode.com --rpc https://eth.drpc.org

Offline runs first. Repeated --rpc supplies fallback providers. Exit 2 means fresh verification is unconfirmed because a dependency is unavailable; exit 3 means evidence does not match. Saved responses are never used to turn an online failure into success.

Full current instructions → · Release checksums → · Public engine and README →

Review Genesis in three steps.

One suggested route · No wallet, new payment or 3D required.

  1. 1. Follow the second real IMD experience →Read the revised hypothesis, see the chosen test and its recorded measurement.
  2. 2. Choose the next experiment →Try a free exercise. Its predictions are local calculations, not a new IMD response.
  3. 3. Verify the journal and delivery →Inspect Ethereum, API availability, the immutable journal and the current verifier.
Historical review-v2 · First experience only

This unchanged archive covers the first builder-wallet → Intake request, 19 → 14 compatible models, 24 separate local fixtures and an earlier contract snapshot with spent() = 0. GenesisResearch was not the payer or callback target of that first request. That zero is historical; the later continuation demonstrates a contract-funded request and exhausted lifetime budget.

Extract the historical package, then run node verify.mjs. Its 15 checks concern that first record. They do not verify the second experience. Offline snapshots do not independently establish Ethereum consensus.

Download historical review-v2 ↓ · Historical pinned source → · Historical report → · Historical manifest →

ZIP SHA-256
85831a7b678341da4b2d4df7b5de42fbe91c4b76239b2a3d6eab2b862d5dc382

Historical contract-role notes → · First experience without 3D →

Superseded feedback-v1 · Same continuation, older verifier

feedback-v1 is retained byte-for-byte. It predates configurable RPC and clearer availability diagnostics. Use current feedback-v2 for a new review.

Compare v1 and v2 checksums →

What verification can establish.

Ethereum confirms request and callback delivery. API reachability is checked separately. Local model calculations explain which hypotheses the saved measurements exclude. None of those checks proves a simulator measurement is real-world science or establishes superiority over a local selector.

Read the evidence levels and limits → · Current endpoint checks →