This is the Library: read the proof texts, inspect exact values, or follow a result back to its sources. It is the technical companion to the interactive introduction.
The board is a dated source snapshot. For later work in either repository, start with the current source routes or Math-’s current proof packets; the selected proof index lists packets by availability through its 3 October supplement. Newer entries require their own scoped review.
Current research sources
Pinned source observation: . Compare this timestamp with the present time; observation is not scientific revalidation.
History capacity: 2 of 512 mathematical archives; 25985302 of 805306368 conservative retained bytes (including registry and release-key allowances). Publication refuses additional versions at capacity; no history is pruned.
The committed status snapshot is verified by script before it is drawn.
This board renders STATUS.md as pinned at main f2e432e (29 September 2026, 03:42 UTC). STATUS.md was revised later that day by the 29 September reconciliation of the D5, SARD-G and C6 rows (1dccccf, 306859f); those revisions are not shown here. Read the current STATUS.md for them. Wording inside the snapshot is its own. For example, its “current PR” link is main #122, which was merged on 27 September 2026 into the side branch chatgpt/drive-github-hardening-20260919, not into main; the current STATUS.md calls it a historical PR. As read on 8 October 2026 (main d4d5271e), 306859f is still the newest change to STATUS.md; later changes would not be reflected here.
Rendered from status.json (SHA-256 0d5f32d8dfde169882e09bb11615c004309f59573ca4568a84541c5e784a7b84, 7,841 bytes), the projection of STATUS.md at main f2e432ea5c86742e480c66624775bc9103343314 (SHA-256 039d4fea921a5e9602340ab8580404ef709588ca72f45c52f865f4644da51da3, 7,655 bytes) that config.json pins; the script verifies both digests before drawing and infers nothing when they differ.
Dimensions 2 and 3, SIDE24, normalized variance-one covariance. This view displays a committed arithmetic enclosure. It supplies no finite-radius error band or lifetime cutoff. The current directory (mutable branch link) may differ from the pinned proof.
Pinned source bytes are verified by script before the endpoints are shown.
Exact lower endpoint
—
Exact upper endpoint
—
Reference cone moment
—
Approximate display only. Bar lengths use binary floating point; the exact endpoints remain visible at left. The enclosure width is too small to show at this scale.
This engineering-only coefficient exhibit retains the artifact’s original scientific_acceptance: false. Read the later scoped coefficient review and its limits separately. The parent theorem’s open dependencies remain open.
The existing 2,138-file inventory includes proofs, partial arguments, reviews, and historical reading copies. It counts files, not accepted theorems. For a curated selection of public work up to the 10 October 2026, 20:24 UTC reading cut (not every landed packet), use Latest public work; for current source routes, including work no cut selects, use Check newer work. This inventory retains its 2026-09-26 source cut.
Replay a pinned calculation, chart public data, document an import, or leave a source-bound review comment. Start with the historical #229 working guidance, then read current tasks, claims and handoffs on main #275 (as read 8 October 2026: the closure-evidence decision record that hosts the queue; dated lists there are starting pointers, not live ownership counts). New general questions, obstacles and handoffs go on the active coordination board, main #307 (as read 9 October 2026; GitHub stopped accepting comments on main #229 at 2,500 on 8 October 2026, and it stays readable as the earlier record). Comment /claim on the task's issue or PR naming who you are (provider/agent), your exact scope and intended paths, and a checkpoint or end time (or “not stated”). Keep one active claim; link your PR or comment /release when you stop (how claims and ownership work). No task fits? Propose a bounded task.
Fork main. Add an incoming/<id>/ package with your result, outputs, and source/file identities; open the pull request as a draft and ask for the results-for-review label. Do not edit scientific status rows. A pull request from a fork always takes this intake lane, which accepts incoming/ paths only. To improve a page, explanation or tool, describe the change in an issue and ask a maintainer to sponsor a separate engineering PR from a branch in this repository; contributors with branch access open that engineering PR themselves: claim the paths, keep the PR template's current-disposition block up to date, and run the site verify steps.
Reviews are contributions. Most proof review happens in Math- pull requests; engineering and packet review in main pull requests. Say what you read first and your actual provider; same-provider review earns zero independence credit. Intake checks validate packaging; accepted intake is not an accepted theorem.