Questions nobody has answered yet.
A standing list of what is unresolved, and a record of what people found when they went at it — ranked by how many others reproduced it, not by how many liked it.
This page lists questions nobody has answered. It also records what people found when they went at them. The order is set by how many other people re-ran the work and got the same result. It is not set by how many people liked it.
Reproduction outranks popularity.
Getting the same result again counts for more than being liked.
Upvotes measure appetite. On a system like this the most exciting post will always be the one claiming it generalises, and that is the claim least likely to survive contact with a second machine. So the primary sort is a status ladder, and inside a rung the sort is the number of independent reproductions — people who re-ran it against the stated engine hash and got the stated numbers.
Upvotes only measure what people want to be true. On a system like this, the most exciting post will always be one saying the system reads text it was never given. That is the claim least likely to hold up on a second machine. So posts are sorted first by a status ladder. Inside a rung, they are sorted by how many people re-ran the work against the stated engine hash and got the stated numbers.
Somebody noticed something. No procedure attached yet.
Somebody noticed something. There are no steps to follow yet.
Stated sharply enough to be wrong, with what would falsify it.
Said sharply enough to be wrong. It says what would show it is wrong.
Others ran the stated procedure and got the stated numbers.
Other people ran the same steps and got the same numbers.
Somebody showed it false. Ranks its author up.
Somebody showed it is false. That moves its author up.
Refutation is a first-class post with equal weight. That is not politeness — the engine's whole behaviour is that refusing is as valid an answer as speaking, and a board that only rewarded positive findings would contradict the thing it is about.
A post that shows a finding is false counts the same as one that shows it is true. That is not good manners. The engine itself treats refusing as a real answer. A board that only rewarded good news would contradict the thing it is about.
Six fields, and one of them is how to kill it.
Six fields. One of them is how to prove it wrong.
Free text produces unfalsifiable enthusiasm. Every finding carries the same six fields, and a post missing any of them is an observation, not a result.
Free text produces excitement that nobody can check. Every finding carries the same six fields. A post missing any of them is an observation, not a result.
| Field | Why it is required |
|---|---|
| The claim, one sentence | If it cannot be said in one sentence it is not yet a claim. |
| Corpus CID | Names the exact bytes. The source text reproduces the whole field deterministically. |
| Engine hash | Mandatory. Results are per-engine; a finding without one cannot be reproduced and is not a finding. |
| Procedure | The probes, the counts, the configuration. Enough that somebody re-runs it without asking you. |
| Numbers | What came out, with N. |
| What would falsify it | A claim that cannot be refuted is not worth posting. |
Configuration is part of the claim. The same question has different answers depending on whether delimiters are kept in the trie key and whether the star vote or the mean is used — about 1.9% against about 1.3% on the shipped holdout. A number without its configuration is not a number.
The settings are part of the claim. The same question gets different answers under different settings. It matters whether delimiters are kept in the index key. It matters whether the star vote or the mean is used. That is about 1.9% against about 1.3% on the shipped holdout. A number without its settings is not a number.
The standing list.
Seeded from the working log and from the engine's own measurements. Each carries what would answer it. Attempts belong here too, including the ones that failed — a question with three recorded dead ends is more useful than one with none.
These come from the working log and from the engine’s own measurements. Each one says what would answer it. Attempts belong here too, including the ones that failed. A question with three recorded dead ends is more useful than one with none.
Is there an element of order 4 on the plane the walk lives on?
Is there a move on this plane that comes back to the start only after four turns?
= ℤ/2 × ℤ/2 has no element of order 4 — 1, A, B, AB have orders 1, 2, 2, 2. Poisson summation needs F with F² = parity and F⁴ = I, generating ℤ/4, checked at ‖F²−parity‖ = 8.75e−14 and ‖F⁴−I‖ = 1.23e−13. So the model holds the functional equation as a consequence without its cause.
has four moves: 1, A, B and AB. Do any one of them twice and you are back at the start. None of them needs four turns to come back. Poisson summation needs a move F where doing it twice gives parity and doing it four times gives the identity. That F was checked by machine: ‖F²−parity‖ = 8.75e−14 and ‖F⁴−I‖ = 1.23e−13. So the model gets the functional equation as a result without holding the reason for it.
What would answer it: exhibit such an element on the right plane, generating the functional equation rather than assuming it — or show none can exist there, which falsifies the ΑΔΩ Hypothesis outright.
What would answer it: show such a move on the right plane, so the functional equation follows instead of being assumed. Or show that no such move can exist there. That second answer would prove the ΑΔΩ Hypothesis wrong outright.
One ℤ/4 is already known in the flow, Q: (Y,Z) → (−Z,Y), with the flow Q-equivariant. It is on the wrong plane.
One four-turn move is already known in the flow. It is Q: (Y,Z) → (−Z,Y), and the flow keeps its shape under it. It sits on the wrong plane.
Is generalisation reachable from this architecture at all?
Can this design ever read text it was never given?
On material never fed, next-word reading is 0.0133 with delimiters skipped and 0.0193 with them kept — about 1–2% either way, N = 828 per cell, Δ/V·001 fed — on the shipped . Merging does not transfer: a field scored about 2% on a book it had not seen and about 92% after being fed it. Feeding more makes more material known; it does not improve the unknown.
On material it was never fed, it gets the next word right 0.0133 of the time with delimiters skipped, and 0.0193 with them kept. Both are about 1–2%. There were 828 probes in each case, with Δ/V·001 fed. That is on the shipped . Merging does not transfer. Feeding it more makes more material known. It does not improve the unknown.
What would answer it: any mechanism that raises unseen reading without raising the false-claim rate. Several were tried and came back inert — those attempts belong on this page.
What would answer it: any mechanism that improves reading on unseen material without making it claim things falsely more often. Several were tried and did nothing. Those attempts belong on this page.
Does the address-collision rate scale with ledger size?
As the record grows, do two different things land on the same address more often?
On the ten-book benchmark — 5.94 MB fed, 1,077,603 states, 11 — the false-claim rate is 0.003, and inspection showed the errors are collisions rather than fabrication: two different contexts landing on the same , and the field reporting what lives there.
On the ten-book benchmark — 5.94 MB fed, 1,077,603 states, 11 — the false-claim rate is 0.003. The errors were looked at one by one. They are clashes, not invented text. Two different pieces of context land on the same , and the field reports what sits there.
What would answer it: the same measurement at 10×, 100× and 1000× the , with the collision rate plotted against state count. If it grows, the address space needs more depth and the admission needs a size-aware threshold.
What would answer it: run the same measurement with a 10×, 100× and 1000× as large. Plot the clash rate against the number of states. If it grows, the addresses need to go deeper, and the admission needs a limit that changes with size.
Can a gate of exactly zero false claims ever be satisfied?
Can anything ever pass a gate that allows exactly zero false claims?
The admission gate requires zero claims on foreign material. Run against the shipped holdout, the flagship corpus itself fails: three claims on Pride and Prejudice, none on Frankenstein or Moby-Dick, out of the 336 probes the gate draws — gates.js · probes(book, 120, 400). All three returned a word from its own ledger rather than invented text — but they are not one phenomenon, and the three were opened individually on 2026-08-18. One is an address collision: the query's full 12-trit key is present in the trie, leftover comes back 0.0000, and at the resolution the doorway reads at that genuinely is the same passage. The other two are pole-threshold false positives on partial prefixes: they agree with the trie to depth 9 of 12 and depth 7 of 12, never reach a full key, and pass only because leftover — 0.2246 and 0.1469 — lands on the near side of the boundary at 0.2853. Calling all three collisions hid the harder of the two problems.
The admission gate allows no claims at all on material from outside. Run against the shipped holdout, the flagship corpus itself fails. It made three claims on Pride and Prejudice, none on Frankenstein and none on Moby-Dick, out of the 336 probes the gate draws — gates.js · probes(book, 120, 400). All three handed back a word from its own ledger rather than invented text. But they are not the same thing, and each was opened up on 2026-08-18. One is an address clash. The query’s whole 12-symbol key is in the index, leftover comes back 0.0000, and at the resolution the doorway reads at, that really is the same passage. The other two are threshold mistakes on partial matches. They agree with the index to depth 9 of 12 and depth 7 of 12. Neither ever reaches a full key. They pass only because leftover, at 0.2246 and 0.1469, lands on the near side of the boundary at 0.2853. Calling all three clashes hid the harder of the two problems.
And the mechanism is not settled. The standing claim that this is fixable only by finer addresses was tested directly: raising DEPTH from 12 to 16 and then to 24 changed nothing at all — three false claims in every case — and keying the trie on the whole face-0 address instead of its first symbol made it ten, spread across all three books. Finer addresses did not help, and in one test tripled the failure.
And nobody knows the mechanism yet. The standing claim is that only finer addresses can fix this. That was tested directly. Raising DEPTH from 12 to 16 and then to 24 changed nothing: three false claims every time. Keying the index on the whole face-0 address instead of just its first symbol made it ten, spread over all three books. Finer addresses did not help. In one test they made it more than three times worse.
What would answer it: a rule that separates a genuine collision from a partial match that merely cleared the pole, and an account of why the pole sits where it does on foreign material. Two of the three are the second kind, so a bar of exactly zero is unreachable in principle at any size, and the gate rejects material it should admit.
What would answer it: a rule that tells a real clash apart from a partial match that only just cleared the pole, and an account of why the pole falls where it does on foreign material. Two of the three are the second kind. So a bar of exactly zero cannot be met at any size, and the gate turns away material it should let in.
Why does agreement depth 9 have no states and depth 8 exactly one?
Why does depth 9 hold no states at all, while depth 8 holds exactly one?
Across 15,538 states aligned after a walk, the agreement-depth distribution runs θ = 14 with 4,847 states, 13 with 1,025, 12 with 581, 11 with 1,436, 10 with 3,512 — then 9 with none at all, 8 with exactly one, 7 with 607, 6 with 341.
15,538 states were lined up after a walk. Counting how deep each one agreed gives: 14 with 4,847 states, 13 with 1,025, 12 with 581, 11 with 1,436, 10 with 3,512. Then 9 with none at all, 8 with exactly one, 7 with 607, and 6 with 341.
What would answer it: a reason for the gap, or a demonstration that it is an artefact of this corpus. A hole that clean in a distribution of 15,538 is unlikely to be nothing, and nobody has chased it.
What would answer it: a reason for the gap, or a showing that it is a quirk of this corpus alone. A hole that clean, in a count of 15,538, is unlikely to mean nothing. Nobody has chased it.
Is interpolation reachable, given the point set is finite?
Can the field make a point between two others, when the points are finite in number?
Each face is a pseudo-ultrametric where every triangle is isosceles, so there is no betweenness inside one — that is a theorem about such trees, not a defect. Summing three faces breaks it: 44.01% of triples still satisfy the strong inequality. But a finite metric space has essentially no betweenness whatever metric it carries, so the break separates addresses without establishing interpolation.
Inside one face, every triangle has two sides of equal length. That means nothing can sit between two other things there. It is a proved property of shapes like this, not a fault. Adding the three faces together breaks that property: 44.01% of triples still obey the strong rule. But a space with a finite number of points has almost no betweenness under any measure. So the break tells addresses apart. It does not show that filling in between them is possible.
What would answer it: either a construction that interpolates on a finite address set, or an argument that it cannot be done and the question should be retired.
What would answer it: either a method that fills in between points on a finite set of addresses, or an argument that it cannot be done and the question should be dropped.
Is the scale-ladder collapse still justified after the architecture changed?
The design has changed. Does the old decision to use one scale still hold?
The collapse to a single rung was made before the trie or the directions existed. The log records that it has not been re-tested since and may no longer hold.
The decision to use a single rung was made before the index or the directions existed. The log says it has not been re-tested since, and it may no longer hold.
What would answer it: re-run the collapse against the current engine. This is a small, well-specified job and a good first contribution.
What would answer it: run that test again against the current engine. It is a small, clearly stated job, and a good first thing to contribute.
What should a field do in the presence of novelty?
What should a field do when it meets something new?
It recognises its own material and refuses what it has never seen. Between those is the middle — the words are its own but the order is not — and what the right behaviour is there has never been settled. The control that moves that boundary is bounded by the field's own two , but where inside them it should sit is not answered by anything measured.
It knows its own material, and it refuses what it has never seen. In between sits the middle : the words are its own, but the order is not. What it should do there has never been settled. The control that moves that line can only move between the field’s own two . Where it should sit between them is not answered by anything measured.
What would answer it: a principled position for the boundary, derived rather than chosen, or a demonstration that it is genuinely a matter of preference and belongs to whoever is using it.
What would answer it: a place for the line that follows from the work rather than being picked, or a showing that it really is a matter of taste and belongs to whoever is using the system.
The thing this board must not become.
The most attention-getting post about this system will always be one claiming it generalises. It does not — about 2% on material never fed (1–3% with sampling) — and that number is a property of the architecture, not a stage it will grow out of.
The post that draws the most attention will always be one saying this system reads text it was never given. It does not. It reads about 2% of material never fed, ranging 1–3% with sampling. That number comes from the design. It is not a stage the system will grow out of.
A board ranked by enthusiasm would surface exactly the claims that are hardest to reproduce, and the governance rules refuse them on sight. That is why reproduction receipts sit above upvotes here, and why every post has to name the engine hash and say what would kill it.
A board ranked by excitement would push the claims that are hardest to reproduce to the top. The governance rules refuse those on sight. That is why receipts from people who re-ran the work sit above upvotes here. It is also why every post must name the engine hash and say what would kill it.
Take the corpus and the engine hash from the post, run the stated procedure, and record what you got — including when it disagrees. A disagreement is a result and it ranks.
Take the corpus and the engine hash from the post. Run the steps it names. Write down what you got, including when it does not agree. A disagreement is a result, and it ranks.
Receipts carry the engine hash and platform of whoever filed them, because a number that only reproduces on one machine is telling you about the machine.
A receipt names the engine hash and the machine of whoever filed it. A number that only comes out on one machine is telling you about that machine.
What is not built yet.
The open-question list above is real and current. The submission and reproduction flow is specified but not yet running: posting, receipts and ranking need the gate and its worker, and until those exist a finding is contributed the same way a corpus is — as a pull request carrying the six fields.
The list of open questions above is real and current. The way to submit and reproduce findings is written down but not running yet. Posting, receipts and ranking all need the gate and its worker. Until those exist, you send a finding the same way you send a corpus: as a pull request carrying the six fields.
Accounts, rate limiting and moderation are undecided. An open post-and-vote surface with none of them becomes a spam board within a week, and that decision belongs to the people running it rather than to whoever writes the page.
Accounts, rate limits and moderation are not decided. An open board that lets anyone post and vote, with none of those, turns into a spam board within a week. That decision belongs to the people running it, not to whoever writes this page.
Terms
- R4
- A set of four moves. Do any one of them twice and you are back where you started. Do two of them in either order and you land in the same place.
- holdout
- Books the machine is never fed. They are used to test it on writing it does not have.
- corpus
- The body of text you feed it. That text is the only thing it can answer from.
- window
- The small run of bytes just before the spot being read. At that moment the machine looks at that run and nothing else.
- address
- A short string of symbols that says where a thing sits in the field. Two things are alike when their addresses start the same way.
- ledger
- The record of what the machine was fed, written down as addresses. It is only added to. Nothing in it is edited later.
- gate
- A check a thing must pass before it is let in. Three of the four gates here are code, and you can run them yourself.
- verdict
- The answer about the answer. There are three of them. It is mine and in the same order. Or the words are mine but the order is not. Or it is not mine at all.
- pole
- A reading the machine takes on its own text when the text is fed in. Later readings are placed between two poles. Nobody types a number in.
- CID
- A name made out of the file itself. Change one byte and the name changes. So the name proves what the file is.