Reachability Labsresearch-driven diagnostics for hidden process failure
Research hub

Research and core concepts

Use this page to get the idea, the benchmark, and the public proof structure in the right order.

The concept pages explain the object. The evidence page anchors the claims. The primer is the shortest plain-language entry point.

The idea breaks into three pages.

Concept 01

Constructive accessibility

The route-side boundary: when a real process loses access to viable futures before the landscape itself goes dead.

Concept 02

Existence vs reachability

Why endpoint validity and process-side access can separate, and why that separation is measurable rather than philosophical.

Concept 03

Hidden process failure

Why a run can keep moving after the route is already gone, and why late visible failure is often a delayed symptom.

The flagship benchmark is the random 3-SAT calibration.

The benchmark resolves a sharp constructive accessibility boundary well below the classical satisfiability threshold and ties that boundary to a trajectory-space fingerprint: late visible failure, exact-prefix deadness at jam, rewind depth, and strong within-instance path dependence.

This is the anchor point for the broader program. It shows that the measured object is not generic hardness. It is loss of reachable future under forward irreversible commitment.

Use the benchmark for one thing

It tells you what the object is, what the fingerprint looks like, and why the route-side boundary is different from the classical landscape-side picture.

The program is larger than one benchmark.

Transfer calibration

The graph-coloring lane shows that the deeper process-versus-landscape split is not confined to SAT, even when the surface failure morphology changes.

Open transfer lane

Gap-profile theorem line

The theorem line formalizes the existence–reachability gap profile, the walking-dead interval, and related hidden-state objects.

Start with the distinction

Plain-language primer

The primer is the shortest route into the work if you want the conceptual layer before papers or code.

Read primer

Public software line

The public demo and tagged releases are the code-side anchor for the software path, separate from the service documents.

Open repository

Need the proof

Use the evidence hub for the flagship paper, supporting materials, public demo, and archives.

Need the service

Use the diagnostics page if the concepts already map to a process you care about now.

Need the lab context

Use the About page for the lab, founder, and the current service-now / software-later posture.