phronesis · laserbrain
laserbrain docs
Your documentation is a set of claims about a running system, true on the day it was written. Nothing errors when they stop agreeing — the page still renders, the tests still pass, the endpoint still answers. It just answers something the docs no longer describe, and the first person to find out is someone following them.
Only claims with a mechanical referent are checked: an endpoint either answers or it does not, a field is either in the response or it is not. Nothing here grades your prose, and a claim it cannot resolve is reported unchecked — never as passing.
A fenced JSON block is the strongest claim on the page — it states the whole shape, nesting and arrays included. The commonest way documentation goes stale is a field renamed underneath it: created_at in the example, createdAt in the API, and nothing anywhere that fails. Shapes are compared, never values: an example showing 42 against a live 7 is data moving, not documentation drifting.
your documentation
the API it describes — optional
nothing probed yet
Everything reads unchecked because nothing has been looked at. That is the honest state, and it is what the numbers would say if this page pretended to check without a target. Give it a base URL to actually probe.
every claim, and what happened to it
it never sends a write
Only GET, HEAD and OPTIONS are ever sent, and there is no flag to change that. A documentation checker that fires writes at a live system to see whether they are documented correctly would, on a good day, create junk records — and on a bad day, delete a customer.
A documented POST is still checked for existence, because OPTIONS is safe to send and a route that has been renamed or deleted stops answering it. That reading is only taken where the server can actually fail it: a control probe asks for a path that cannot exist first, and where the answer is the same as for a real route — one CORS middleware above the router, which is common — nothing is claimed. What no preflight can show is the response body, so the fields a write is documented to return stay unchecked for good.
Public httpshosts only. IP literals, loopback and private names are refused: this reaches a URL you typed from inside Cloudflare’s network, and one that would follow you into private space is a hole rather than a product.
*.workers.devis refused too, for a different reason: a Worker’s request into that zone comes back 404 for every route whatever the route does, so every finding would be drift that is not there. This page found that by probing its own prober, whose /healthanswers 200 to everyone else. Point it at the API’s custom domain.
read from your docs · 5 endpoints (4 probeable) · 0 field claims · 1 JSON example (3 field paths)