“Know how to solve every problem that has been solved.” “What I cannot create, I do not understand.” — Richard Feynman

Claims

A ledger of small, citeable facts — one declarative sentence each — and what happened when I tested them. Each is a hypothesis with a verdict: supported (it held, by an external reference or a numerical experiment), falsified (a test showed it false — kept anyway, because the negative result is the knowledge), or uncertain (untested or inconclusive).

✓ 22 supported ✗ 1 falsified ? 0 uncertain 23 total
Why a ledger of atoms instead of just pages?

Think about how a dictionary works. It defines a word using other words, which are defined using still other words. Follow any definition far enough and you either loop back to where you started or you reach a word no other words can pin down — one you fix only by pointing at an instance and saying this is one, that is not. There's no bottom made of pure definition. Knowledge is a graph of references with its leaves nailed to reality.

Programming is the same shape. A function is written in terms of other functions; types are built from other types; the call graph bottoms out in primitives, which bottom out in machine instructions, which bottom out in physics. Nothing is self-defining, and the structure only means something because the leaves touch hardware. This is the symbol-grounding problem, and it's not a bug — it's how any system of meaning has to work.

So I'm trying to build my own understanding the way both of those are built: as a web of small claims that reference each other, with the leaves grounded in computation and observation. Each claim is an atom you could cite mid-sentence — "…because [Hartree-Fock is a fixed-point iteration], DIIS applies directly." The neighbors on each claim are the edges: instance-of, generalizes, contradicts, supports. The pages on this site are the syntheses; the claims are the atoms those syntheses are made of.

And every atom has to be falsifiable, or it isn't worth keeping. That's the Popper part. I don't get to mark a claim true — I only get to say it survived testing (supported), the way a corroborated conjecture has survived but is never finally proven. What I can do cleanly is mark one falsified: when a numerical experiment shows it's wrong — like the time I tried to use rational functions in place of Slater orbitals and watched the integrals refuse to cooperate — that result stays on the ledger as a falsified claim. The vocabulary is asymmetric on purpose. You can knock a claim down with a single experiment; you can never prop it up forever.

The full authoring protocol lives in CLAIM_AUTHORING.md.

Tags in use

algorithmsapproximationapproximation-theoryatomic-orbitalsbiophysicscircuit-analogycircuitscomp-neurocomplexitycontinued-fractionscusp-conditiondata-structuresdrude-modeldynamic-programmingdynamical-systemseigenvaluesetudesexcited-statesfermionsfixed-pointfouriergaussian-integralsgaussiansgradient-descenthartree-fockhashmaphermite-polynomialshydrogen-atominterpolationkernel-methodskrylovkrylov-methodslanczoslcaolinear-algebralinear-responselinear-systemsmany-bodymcmurchie-davidsonmean-fieldmembrane-dynamicsmemoizationmlmodel-order-reductionmolecular-integralsnegative-resultnumerical-methodsnumerical-stabilityobara-saikaorthogonal-basesorthogonal-polynomialspadepauli-exclusionpedagogypolynomialsprojectionquantum-chemistryrandom-featuresrational-approximationrecursionrelaxation-timeresolventscfslater-determinantspecial-functionsspectral-methodssymmetry-breakingtdatddftthree-term-recurrencevariational