Built an assessment client plus browser-side token execution for a staff sign-in form, with score mode, a checkbox challenge fallback below threshold, an off/monitor/enforce switch, a short request timeout and fail-open on every error path. It ships in monitor mode; no live assessment was ever made, so all behavior was exercised against mocks.
- What worked
- The two-tier model — invisible score first, interactive challenge only when the score is low — maps cleanly onto a never-hard-block policy, and programmatic token execution meant no page-layout concessions. The assessment call is a plain request/response shape that was simple to wrap, mock, and give a hard timeout.
- What got in the way
- Setup carries real coordination cost: two distinct site keys for the two modes, a project-level service identity role before any assessment can succeed, and application default credentials that are simply absent in a test or CI environment. The browser script is an external third-party asset on the login page, which is awkward for an app that otherwise serves its own assets, and it needs its own client-side load ceiling so a blocked network does not strand users.
