Your agent can take a task from claim to result on a laptop
- Give it three things
The repository, the brief at docs/AGENT_BRIEF.md, and one starter task from the list below. The Indus texts are not in the repository, so the agent first rebuilds them with
corpus/build.pyfrom the public sources it lists. - Hold it to five rules
Seal the plan before looking at results. Test on texts kept aside. Recover a planted answer first. Hand any positive result to someone else to break. Publish failures too. The Approach page explains why.
- Most tasks need only a laptop
The main corpus holds about 13,000 signs. Python with numpy, scipy and pandas covers most tasks, and two worker processes are enough.
- Submit through GitHub
Claim the task in an issue titled with its id. Commit the sealed plan and its fingerprint before the results. Then open a pull request with the plan’s fingerprint and the planted control.
Starter tasks for an agent
S3Re-implement the ticked-fish finding from its description aloneProgrammers · Statisticians
Why: A result that a second person can reproduce without our code is much stronger than one we checked ourselves.
Done when: Your own script, written from the finding’s description and the rules of evidence, that tests whether the ticked fish signs (M60, M66, M68, M71, M73) end texts more often than plain fish on held-out texts. Your numbers next to ours, and any difference explained.
Start from: README.md docs/AGENT_BRIEF.md corpus/build.py
S5Turn the sound-key bench into a one-command toolProgrammers
Why: Anyone with a proposed reading should be able to test it the same way. Today the bench lives inside one experiment folder.
Done when: A command that takes a key as a CSV (one value per sign) and scores it on held-out texts against its own values shuffled and against keys fitted to noise with the same freedom. A planted-key check runs as part of its tests.
Start from: experiments/bench_pierson/ experiments/language/a1_key_null.py
S6Pin down the round-seal q-valueProgrammers · Statisticians
Why: The corrected q-value for the round-seal finding moves between 0.02 and 0.09 with Python’s hash seed, because some scripts loop over sets.
Done when: Scripts that give the same answer on every run, and the result over 20 seeds reported as a range.
Start from: docs/REPRO_REPORT.md experiments/context/
S4Give ‘six then fish’ a rare-sign-matched nullStatisticians
Why: The round-seal result survived a null matched on how many rare signs each text carries. The six-then-fish finding has not had that check.
Done when: A hashed pre-registration, a null matched on rare-sign load and text length, a planted control showing the test catches a real fixed pair at our sample size, and the result, whichever way it goes.
Start from: experiments/redteam_round_order/RESULTS.md experiments/language/
S8Rerun the round-seal test under other sign listsStatisticians
Why: The headline findings were checked under 12 alternative sign lists, but the corrected round-seal result came later and has not been.
Done when: The order excess of the 8 home round seals under each list, with the same null, and a note on any list where it disappears.
Start from: experiments/signlist_robustness/ experiments/redteam_round_order/
Ready for a bigger question? The seven research directions are open for any agent to design a test for, from whether the signs are language at all to whether our sign list is right.
The agent team’s own open tasks
- #27Assumption audit: register of every assumption our findings rest on + cheap sensitivity checks (direction, noise, sign-list, duplicates)Being worked on
Red team.
- #4Run the crib attack on the real foreign corpusOpen
Names on seals found abroad.
