example.lrs.amtechhq.com / lead-routing-system

proxy — the short link, resolved

Somebody taps a link in a text message. Proxy is what answers: it looks up the token, follows the redirect chain to wherever it really goes, records the click, and sends the person on. It is the one service here that a member of the public interacts with without ever knowing it exists.

Health — live

not asked

This check runs in your browser and has not run yet. With JavaScript off it never runs, and this line stays as it is — which is the honest answer: nothing was asked, so nothing is known.

This route is open to anybody and carries no Access-Control-Allow-Origin header, so a browser on this origin normally cannot read the answer even though the request succeeds. That is deliberate — the route exists for the deploy's health-checked auto-revert and for monitoring — and it is why the badge above usually says answered, unreadable here rather than up. The curl below is not bound by the same-origin policy and shows what it actually returns.

Two health routes, and one of them is not JSON

$ curl -s https://proxy.lrs.amtechhq.com/api/proxy/health
{"service":"proxy","status":"ok"}

$ curl -s https://proxy.lrs.amtechhq.com/healthz
OKAY

Recorded 2026-09-06. /healthz is the load balancer probe the service was born with; /api/proxy/health is the one the platform's roster requires of every service, so that one script can check all seven. Both answer, which is the honest state of a service that was copied in from somewhere else and then made to fit.

Where it came from, and why that is written down

Proxy is the only one of the seven that was not written here. It is a working-tree copy of a production service, brought in as the seventh repo — and its git history was deliberately not carried over, because cloning would have kept the original remote pointing somewhere else. So a note in its README is the only record of where the code came from, and that note names the exact commit, notes that the copy actually reflects a commit seven ahead of the one the plan pinned, and says why.

That is the house style rather than an apology. A provenance note that says "copied from somewhere" is worth nothing; one that names the commit, admits the drift and explains it is a fact somebody can check.

What it does

Deployed, healthy, and routed to nothing. Proxy has been running since 2026-08-30 and no httpd or haproxy rule sends it any real traffic. That is the state, from the roadmap, and it is worth saying plainly: a service answering its health check is not a service doing its job, and this site will not let the green badge above imply otherwise.