Routing evidence
Graph visibility, peer state, and route confidence live together so operators can judge why a payment is failing.
Reef adds release-safe payment diagnostics to Fiber, then turns real attempts into a route autopsy, a review-only response plan, and a reusable incident API. It never signs, sends, or invents a failed hop.
Reef publishes an incident only after retained observations prove a success, failed attempt, and later success in chronological order.
Stock release builds hide attempted routes from get_payment. Reef's upstream get_payment_diagnostics method exposes redacted attempt evidence without invoices, preimages, session keys, or onion payloads.
Payment Doctor turns that evidence into a diagnosis, response plan, exact readiness recheck, before/after comparison, incident brief, SDK contract, and API. The broader console exists to support that workflow.
Graph visibility, peer state, and route confidence live together so operators can judge why a payment is failing.
Every warning stays tied to evidence, a severity, and the next action Reef recommends.
Unavailable metrics, missing WebSocket coverage, and read limitations remain visible throughout the product.
The overview highlights node identity, configured coverage, and cross-node visibility gaps when more than one node is present.
These previews are built from the same app routes operators use after they enter the dashboard.