Open hypothesis

Reality as a map of information?

ITHKOR explores a bold question: whether time, space and the stable phenomena around us can be understood as expressions of deeper information rules.

It is not a completed physical theory. It is a research program of small controlled tests, islands of validity and clearly named boundaries.

What it brings

  • Today it does not look for a final answer to the whole universe. It tracks where information patterns appear and where they break.
  • Special ITHKOR is the testable layer of the larger question.
  • Failures, boundaries and controls are part of the map, not something to hide.
Big question open

General ITHKOR asks whether deeper information order may sit beneath what we describe as time, space and stable objects.

Today small models

The supported work lives in controlled small models with explicit boundaries.

Island map validity

The project collects islands of validity, mixed results, stop signs and repeating boundaries.

Claim careful

The honest claim is a map of questions and controls, not proof of completed physics.

How to read ITHKOR

From a large question to a testable layer

The first screens are intentionally plain-language. Technical readers can find stricter boundaries lower on the page and in the reviewer bundle.

01 Question

Maybe space and time are not the primitive language of reality.

02 Records

We track where a small system develops a stable trace.

03 Response

We ask whether a source creates a readable information response.

04 Islands

When a pattern holds only in a bounded scope, it becomes an island of validity.

05 Boundaries

When the pattern breaks, that boundary blocks an inflated claim.

The big question

What if space and time are not the beginning of the story?

The usual view starts by saying that things exist in space and time. ITHKOR asks the question in the opposite direction: could space, time and stable things grow out of deeper ordering of events, records, relations and information constraints?

This is not a claim that the world is a simple simulation or a computer game. It is a careful question about whether visible physics might sit on a deeper information order.

General ITHKOR is that large question. It is not proven today. It is a frame for where to look, and for which boundaries must stay visible.

Testable part

Special ITHKOR: what can be tested today

For ITHKOR to be more than philosophy, it needs a smaller testable layer. That layer is Special ITHKOR: controlled small models where we can observe whether an information pattern holds or breaks.

Such a model may study records, source response, internal event ordering, coherent order or a boundary where controls begin to imitate the signal.

This is the important public caution: we are not testing the whole universe. We are testing small situations that are precise enough to say yes, no, or only a boundary for now.

Island map

Not a continent of completed theory, but an archipelago of validity

An island of validity means that a stable pattern appears in a small controlled model, the test has controls, and we can name exactly what passed. It is just as important to say where the result stops.

ITHKOR today is more like a map of these islands than completed physics. Some islands look promising, some are mixed, and some bridges between them have failed.

That map is the public value: it shows direction while refusing to sell more than the data allows.

Failures

Why negative results are good news

Large hypotheses are tempted to show only successes. ITHKOR records failures too: probe-motion or geodesic-style bridges, energy bridge, MOD1 taxonomy, broad TIME2 robustness and other stop signs.

If something fails, it does not disappear. It becomes a map boundary. That is what separates the project from cheap online theories of everything: it does not claim that everything fits; it also shows where patterns broke.

QPU without hype

Quantum hardware as a check of small tests

Some small readout tests were prepared so they could be read on quantum hardware. That is interesting because real hardware enters the story, not only a local sandbox.

But it means only that a small pre-frozen test behaved as expected in a bounded regime. It does not mean that a quantum computer confirmed a physical theory of reality.

Technical layer

Technical details belong lower on the page and in the bundle

Anyone evaluating the project technically should not stop at the hero. Lower on the page are claim boundaries, an island map and links to documents that separate supported statements from blocked ones more precisely.

This split is intentional: a general visitor can understand the point in a minute, while a specialist has a route to the atlas, claim ledger and reviewer bundle.

Islands of validity

What currently looks interesting in ITHKOR

These cards are a public map, not a complete recipe. Each island has a simple meaning and its own boundary.

Island of validity Quantum readouts and records

Small systems can show when information behaves like a stable record and when the pattern disappears.

Island of validity Information response and small fields

A local source can create a readable response map inside a carefully bounded harness.

Island of validity Coherent order

The COND branch shows a small island where part of the system behaves in a surprisingly ordered way.

Island with boundary Modular response

Some real-sector tests keep a stable response, but physical interpretation remains blocked.

Scoped signal Internal event ordering

A narrow signal helps order certain events, but it is not proof of physical time.

Negative result Boundaries and failures

MOD1, TIME2 and the motion bridge are stop signs that keep the map honest.

Map ISLANDS1

A combined map of what passed, what failed, where boundaries repeat and where claims remain blocked.

Reviewer bundle D20-D22

Representative rows, smoke checks and a fresh-clone drift report for skeptical technical readers.

What does not follow yet

Opening a question is not selling an answer

These boundaries should stay visible. They let ITHKOR be bold without overstating the case.

Topic Status Public wording
Gravity Do not claim This is not proof of gravity.
Spacetime Do not claim This is not proof of spacetime.
Physical time Do not claim This is not proof of physical time.
Theory of everything Do not claim This is not a theory of everything.
QPU results Careful QPU results are hardware checks of small tests, not confirmation of General ITHKOR.
General ITHKOR Open It remains an open hypothesis and a map of questions.
Theory updates

How the public story evolved

The theory page keeps a short public trail. Detailed D-branches belong more naturally on the experiment page and in reviewer bundles.

2026-05-23 From intuition to testable models The story moved from a large question toward small models where passes, failures and boundaries can be named clearly More

The first important shift was not a spectacular success, but a useful tightening. The project began to show openly that local peaks and elegant intuitions are not enough if the result breaks under ordering changes or controls.

That produced a healthier form of the theory: not a claim about all of reality, but a set of small situations where stability, collapse and boundaries of validity can be inspected.

For the public story this matters. ITHKOR can stay bold, but it should not skip the step where a hypothesis has to meet a controlled test.

2026-06-03 Special and General ITHKOR Supported small tests were separated from the larger open hypothesis about an information layer of reality More

Special ITHKOR is the practical and testable part: small finite models, readouts, controls and clearly named boundaries. This is where the language can be more precise because concrete results exist.

General ITHKOR is the larger question: whether stable phenomena around us may arise from deeper information rules. That part is interesting, but publicly it should remain framed as an open research program.

This split makes the page more credible. Visitors see the large idea while also understanding that the supported layer and the wider hypothesis are not the same thing.

2026-06-04 Islands of validity and boundaries Instead of one large proof, the work became a map of islands, mixed results and stop signals More

The D-branches produced different kinds of evidence: some narrow islands of validity, some boundary-only results and some bridges that stopped completely. That is not a communication flaw; it is part of the research.

The current strength of ITHKOR is not the sentence that everything fits. The strength is the map: what holds, what breaks, where the controls are and which claims should remain blocked.

That is why the public language is built around islands of validity. It is interesting for a reader while staying inside what small models can actually support.

2026-06-17 D20-D22 reviewer bundles The public story gained a technical route for skeptical readers: brief, smoke check and drift report More

A bold hypothesis needs more than a pleasant introduction. The reviewer path adds documents that separate supported finite claims from blocked physical claims more strictly.

D20 shows representative rows across branches, D21 checks the cleanliness of the replication package and D22 adds a fresh-clone drift view. Together they create a practical route for someone who wants to inspect the claims.

For the public page this gives a simple rule: the first screens should be understandable, but specialists must always have a route to stricter evidence.

Technical bundle

Download the technical and reviewer bundle

The public page explains ITHKOR in readable language. The technical bundle contains the more precise documents: experiment atlas, claim ledger, reviewer brief, the D20-D23 replication path and the ITHKOR-SIM layer including the SIM2C/SIM3C practical pass.

ithkor-public-reviewer-bundle.zip ZIP, 41 KB, public-safe Markdown documents SHA-256 2506B65A142E7ADA932DFCC4D364CC91452D3DF4C187C4405F40D0B8233D4494
Download full ZIP bundle
Implications

Who this page is for

Next steps from the theory

The theory is the high-level narrative. The practical route is to read the experiment boundary and then inspect the product layers it motivates.