Evidence and public references
This is the clean public evidence surface: the flagship paper, supporting materials, public code, archives, and the shortest references that substantiate the core claims.
Papers, code, archives, and the primer in one place.
One place for the core public references.
Use this page for the public references: the flagship paper, supporting materials, public code, archives, and the primer.
Constructive Accessibility from Committed Prefixes in Random 3-SAT
The first resolved benchmark: a measured constructive accessibility boundary, late visible failure, exact-prefix deadness, trap depth, and strong within-instance path dependence.
Constructive Accessibility Instrument
The public reference implementation and release track for the software line. This is the code-side anchor, separate from the website and separate from the service documents.
Supporting materials and large-n diagnostics
Finite-size scaling, hazard diagnostics, bridge and rewind analyses, robustness controls, and the transfer calibration lane sit here as the public understructure for the flagship result.
Builder's View and the adapter lane
The primer gives the plain-language entry point. The graph-coloring lane shows that the deeper process-versus-landscape split is not confined to SAT.
The benchmark figure belongs here.
This is the research-facing benchmark surface. The orange curve is measured A0 constructive success. The teal curve is the existence-side reference. The shaded band is the existence–accessibility gap. Toggle system size to see how the boundary sharpens and drag to measure the separation at matched success levels.
The shortest evidence summary
A process-indexed boundary exists.
The flagship benchmark resolves a constructive accessibility transition well below the classical satisfiability threshold.
Failure has a trajectory-space fingerprint.
Late visible collapse, bridge-verified deadness, rewind depth, and strong path dependence all support the same route-side interpretation.
The measurement contract transfers.
A second oracle-backed combinatorial domain already shows the same deeper process-versus-landscape split with a different surface morphology.
Artifact ledger and file verification
This is the public control surface for versions, mirrors, and checksums. Use it when you need to confirm exactly which public artifact you are looking at.
Where to start
Artifact ledger
Software release version, release link, and SHA-256 hashes are read from /artifacts.json. Deploy this file from GitHub release automation instead of editing version strings by hand.
| Artifact | Version | Status | Primary | Mirror / archive |
|---|---|---|---|---|
| Flagship paper Constructive Accessibility from Committed Prefixes in Random 3-SAT | v1.0 | Public | OSF | Zenodo |
| Public demo Constructive Accessibility Instrument reference implementation | v0.3.2 | Public | GitHub release | GitHub |
| Supplement Extended data, validation runs, coloring adapter | v1.0 | Public | OSF | Zenodo |
| Primer The Builder's View — a plain-language introduction to constructive accessibility | v4.0 | Public | Website | — |
| Primer (audio) The Builder's View — spoken narration (~20 min) | v1.0 | Public | Website | — |
Verify a download (SHA-256)
Pick a file you downloaded. This computes SHA-256 in-browser and checks it against the expected hash. Nothing is uploaded.
Use the tools from here, not from the homepage.
Reachability snapshot
Use the interactive snapshot to watch forfeiture rise and inspect a late-loss morphology on a compact demo surface.
Open snapshotTrajectory atlas
Use the atlas to see same-instance path divergence: successful corridors, shallow traps, and deep traps side by side.
Open trajectory atlasPrimer
Use the primer when you need the shortest plain-language path into the research before the technical pages.
Read The Builder's ViewSoftware release
Use the public repository and release track for the code-side reference implementation and tagged software artifacts.
Open releaseConcept first
If you need the shortest conceptual path before looking at papers, start with the concept pages.
Constructive accessibilityPlain language first
If you want the least technical entry point, start with the primer.
The Builder's ViewService path
If the problem already maps to your process, go straight to the diagnostics path.
DiagnosticsCode path
If you need the public software and release track, use the repository and release pages directly.
GitHub repository