platform — where an operator logs in
Everything a person does to this system, they do through platform: it holds the operator accounts, the sessions, the settings, and the console screens for all seven services. It also holds the things the other six repos are built from — the architecture decisions, the shared helper packages, the MySQL bootstrap, the deploy script.
Health — live
not askedThis 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.
What you can point at — live, in your own browser
The console is real and it is served at admin.lrs.amtechhq.com. Open it. You will get a login form, because this site has no account and would not put one in its source if it had.
$ curl -s -o /dev/null -w '%{http_code} -> %{redirect_url}\n' https://admin.lrs.amtechhq.com/fraud
303 -> https://admin.lrs.amtechhq.com/login
$ curl -s -o /dev/null -w '%{http_code}\n' https://admin.lrs.amtechhq.com/login
200
$ curl -s https://platform.lrs.amtechhq.com/api/v1/sessions/current
{"success":false,"errors":["a bearer token is required"],"meta":{"timestamp":"2026-09-06T18:06:13Z"}}
# HTTP 401
Recorded 2026-09-06. That 303 is the entire demonstration platform can
give a public page, and it is worth more than a screenshot of a dashboard, because you can reproduce it.
The console sections — from source: platform/cmd/… route table
Every one of these is behind the login above. Listed so the shape of the console is visible without anybody having to fake a screenshot of it:
| Section | What an operator does there |
|---|---|
| /managers | Buyers and sellers, their offers, endpoints and filters. |
| /configuration | The field dictionary and the routing rules, including a rule evaluator. |
| /compliance | Persons, consents, domain consents, suppression checks, merges, and the audit trail. |
| /fraud | Sessions, rules, settings, and the integration screen that generates a seller's snippet. |
| /leadgate | The per-campaign cutover control described on the routing page. |
What platform holds that is not a screen
- The decisions. Sixteen ADRs, each naming the alternative it rejected. Schema-per-service enforced by GRANT; no soft delete anywhere; one phone normalizer; one template syntax; billing deliberately deferred; absence is not evidence; consent must be provable.
- Canon. Shared helper packages are copied into each repo rather than imported, in two tiers: frozen ones where any difference fails the build, and drifting ones where a difference must be recorded in that repo's own
CANON.md. - The database bootstrap, and a script that proves the isolation rather than asserting it: it must print 20 out of 20 cross-schema queries denied and 5 out of 5 own-schema queries allowed.
- The deploy, which is
git fetchand a checkout on the box, health-checked, with an automatic revert — never a file copy.
A rule this site obeys because platform wrote it down. One of the two design principles in the roadmap is one rule, one home. Before the service list lived in a single roster file it lived in nine places, and adding the seventh service meant editing all nine by hand. Three were missed, silently, because nothing compared the copies: the credential guard stopped scanning the newest repo, the rotation tool could not rotate its credential, and the status page could not say whether it was up.