Pando is named for the aspen grove in Utah that looks like ten thousand trees and is one organism: one root system, stems that die and are replaced. This method works the same way. It takes one plain statement, opens it into every question the statement contains, lets each one live or die on its own record, and hands back the single question worth asking next. Then it starts again with that question. The four drawings below are that process, end to end.
One new word on this page: Pando. Everything else is a word you already know: the map, the field, the signal, the needle. Nothing here is invented. It is assembled, and the seal at the bottom lets you check that claim yourself.
movement one
The blast
A statement goes in whole and comes apart. The pieces find each other, hold, and close.
one statement, opened into every question it contains, and closed back down to one
movement two
The cell
What one of those pieces is made of, and what it stands on.
three parts make a question · five levels keep them running
movement three
How it lives and dies
Five states, and only one of them lets anything out.
it holds everything in until it closes · closing is what lets the answer out
movement four
The signal
How to tell whether any of it is working, where everyone else is looking instead, and where the instrument stops being able to tell you.
one clear line, or many loud ones · only the clear line can be read
the seal
Check it yourself
Every claim above traces to the evidence package linked below: all ten runs including the failures, the declared limits, and the exact commands to reproduce each result. The package is public, its manifest is OpenTimestamps-anchored, and the working chain behind it is disclosed as self-attested until independently crossdated. Nothing on this page asks to be believed; the parts that cannot yet be third-party-verified are named as such.
PANDO EVIDENCE SEAL 2026-08-24 public package:/pando/evidence/ — 14 files + manifest, fetchable, hashable (.py files: fetch via GitHub raw if the origin 403s scripts) opentimestamps: manifest.json.ots + EVIDENCE-2026-08-24.md.ots — anchored via public calendars to Bitcoin; verify with `ots verify` manifest sha256: hash /pando/evidence/manifest.json yourself; the .ots proves WHEN it existed working-repo commits (private by design, internal provenance only): 9d23160… (19:44 CDT), 6c082ee… (21:15 CDT addendum) witness chain: local Lotor chain, 3,894 entries at sealing — a SELF-attestation until crossdated; its head hash is inside the OTS-stamped evidence document (listed in the manifest), which binds it to a public timestamp disclosed: run10-sonnet.log was mid-run at the addendum seal; the package carries the final file and says so in the manifest
To verify: hash the manifest and compare. Check the chain head against the entry count at sealing; the chain keeps growing, and the seal records its state at that moment. Re-run the commands in the package. If your numbers disagree with these, that is a finding, and it is wanted.