# ITHKOR Reviewer Brief v6

## Review Request

This document is the shortest public entry point for technical criticism of
ITHKOR v6. It is written for a skeptical reader, not for promotion. The useful
review goal is:

```text
Find the first unsupported claim, hidden retuning path, missing control,
irreproducible row, or place where a finite diagnostic is being promoted into
physics.
```

The project author is not asking the reviewer to accept General ITHKOR. The
request is narrower: check whether the current public package honestly supports
the claim-safe statement below and whether the boundaries are enforced.

## One-Page Status

ITHKOR v6 is a finite information-response research program. It has multiple
scoped diagnostic supports, a large negative-control ledger, and selected
QPU-readable finite witness results. It does not claim physical spacetime,
physical time, gravity, Lorentz invariance, quantum gravity, real condensate
physics, or General ITHKOR confirmation.

The strongest public-safe statement is:

```text
ITHKOR v6 documents a scoped finite information-response program with positive
finite islands, explicit negative controls, selected frozen finite QPU readout
witnesses, and a claim ledger that blocks physical-theory escalation.
```

Everything stronger than that should be treated as unreviewed unless it is
backed by a named source document, a frozen gate, and an explicit blocked-claim
boundary.

## What Should A Skeptical Reviewer Check First?

1. **Claim ledger**: verify that strong physical claims are blocked before
   reading the positive results.
2. **Reviewer bundle D20-D22**: check whether representative rows can be read as
   a small replication package rather than a selected success list.
3. **ISLANDS1**: check that it is a meta-audit, not a hidden new experiment.
4. **Experiment atlas**: confirm that every positive result has a boundary and
   blocked claim.
5. **Negative branches**: inspect D9, D14, D17, MOD1, broad TIME2 and G
   generalization boundaries.
6. **QPU interpretation**: ensure QPU rows are read only as finite readout
   support.

Suggested 20-minute review route:

1. Read this brief.
2. Read `docs/ITHKOR_REPRODUCIBILITY_PROTOCOL.md`.
3. Read `docs/ITHKOR_CLAIM_LEDGER.md`.
4. Read the D20 reviewer-set table.
5. Inspect the MOD1 negative row.
6. Inspect one positive row and one QPU-frozen row.
7. Decide whether the public claim is still too strong, too weak, or correctly
   bounded.

## Why The Program Is Not Just Pass Hunting

The corpus contains many explicit failures:

- D9 did not confirm a deconfounded probe-flow or geodesic/free-fall bridge.
- D14 did not confirm probe-class equivalence behavior.
- D17 did not confirm an energy/cost bridge.
- MOD1 failed under frozen modular-spectrum gates.
- TIME2 failed broad internal-clock robustness.
- G1/G1D/G1E did not confirm general record-defined geometry.
- COARSE and D13 have scoped support but clear boundaries.

These negative results are durable source-of-truth entries, not discarded runs.
If any public text hides these rows, the public package should be considered
weaker.

## What The Positive Results Mean

The positive results mean that finite systems can show controlled patterns in
small harnesses:

- quantum-information style readout constraints;
- macro-record stability and observer consistency;
- source-response and field-coupled readout;
- finite response envelope;
- scoped radial/coarse/scale behavior;
- coherent-order toy islands;
- modular-response real-sector behavior;
- scoped dark/entropy internal-ordering signal.

These are finite diagnostics. They may motivate future hypotheses, but they do
not establish those hypotheses.

## Falsification And Weakening Checklist

| reviewer concern | what would weaken the package | where to inspect first |
| --- | --- | --- |
| Claim inflation | Any statement that a finite row proves spacetime, gravity, physical time, Lorentz invariance, quantum gravity or General ITHKOR | `docs/ITHKOR_CLAIM_LEDGER.md` |
| Pass hunting | Positive rows shown without MOD1, D9, D14, D17, broad TIME2 or G boundaries | `docs/D20_REPLICATION_PACKAGE_AND_REVIEWER_BUNDLE.md` |
| Hidden retuning | Expected statuses, thresholds or manifests changed after failures | `docs/D21_CLEAN_REVIEWER_REPLICATION_SMOKE.md` and `docs/D22_FRESH_CLONE_LOCAL_RERUN_DRIFT_REPORT.md` |
| QPU overinterpretation | Hardware rows described as physical proof instead of frozen finite readout witnesses | D20 D7b/D10f rows and the claim ledger |
| Reproducibility gap | Fresh-clone/local reruns fail without being recorded as drift | `docs/ITHKOR_REPRODUCIBILITY_PROTOCOL.md` and `docs/D22_FRESH_CLONE_LOCAL_RERUN_DRIFT_REPORT.md` |
| Meta-audit overreach | ISLANDS1 treated as a new experiment or physics confirmation | `docs/ISLANDS1_FINITE_ISLAND_CONSISTENCY_AUDIT.md` |

The fair criticism target is not "does this prove reality?" The fair target is
"does this package honestly document finite support, finite boundaries and
non-escalation?"

## What ISLANDS1 Adds

ISLANDS1 does not add a physical result. It adds a consistency map:

- 10 finite islands loaded;
- 11 boundary types;
- 9 repeated boundary types;
- 9 consistency pairs;
- 5 finite bridge candidates;
- missing inputs: 0;
- QPU allowed: false;
- physical claim allowed: false.

The important insight is methodological: the project now has a map of where
finite mechanisms hold and where they repeatedly fail.

## Reviewer Questions And Answers

**What should I try to falsify first?**

Start with claim inflation, retuning and negative-control visibility. If those
fail, the package is not ready for broader theoretical discussion.

**Does ITHKOR prove spacetime or gravity?**

No.

**Does ITHKOR have QPU results?**

Yes, but only for selected frozen finite readout witnesses.

**Does QPU support upgrade the program to a physical theory?**

No.

**What is the strongest safe result?**

ITHKOR has a scoped finite island map and a claim-safe finite
information-response diagnostic program.

**What would weaken the program?**

Independent reruns failing, controls matching the signal, hidden stress rows, or
promotion of finite diagnostics into unsupported physics.

**What would strengthen the program without changing its claim level?**

Independent local reruns of D20 non-QPU rows, cleaner external review of MOD1 as
a negative control, and a repeat of QPU-facing finite readouts without changing
thresholds or expected statuses.

**What would be required before stronger physical language?**

At minimum: preregistered gates, independent reproduction, hard controls that do
not imitate the signal, external physical observables, and a non-toy validation
path. The current public package does not claim to have that.

## Recommended Review Procedure

1. Start with `docs/ITHKOR_CLAIM_LEDGER.md`.
2. Read `docs/ITHKOR_REPRODUCIBILITY_PROTOCOL.md`.
3. Read `docs/ITHKOR_EXPERIMENT_ATLAS.md`.
4. Inspect `docs/ISLANDS1_FINITE_ISLAND_CONSISTENCY_AUDIT.md`.
5. Read `docs/D20_REPLICATION_PACKAGE_AND_REVIEWER_BUNDLE.md`.
6. Compare it with `docs/D21_CLEAN_REVIEWER_REPLICATION_SMOKE.md` and
   `docs/D22_FRESH_CLONE_LOCAL_RERUN_DRIFT_REPORT.md`.
7. Sample one positive branch and one negative branch.
8. Verify that the branch status is reflected in `docs/RESULTS_INDEX.md` and
   `docs/EXPERIMENTS.md`.

## Public Outreach Note

If this document is sent to external readers, the recommended framing is:

```text
I am looking for falsification-oriented feedback on a finite diagnostic research
program. The package does not claim gravity, spacetime, physical time, quantum
gravity or a theory of everything. The most useful review would identify the
first unsupported claim, hidden retuning path, missing control, or
irreproducible row.
```

## Bottom Line

ITHKOR v6 is not a completed physical theory. It is a disciplined finite
diagnostic program with enough structure to deserve replication and critique.
The reviewer brief is therefore not a proof document; it is a map for finding
where the package could fail.