Lacesse Shield output restructure.
Lacesse Shield replaced the earlier in-browser proof-of-work with an interactive verification surface. Signals that scripts can fake removed from the decision path.
- Interactive verification. Client renders a challenge; selection is submitted to Lacesse; Lacesse returns a signed verdict.
- Hidden by default. The "Verify you are human" field appears only after the user tries to submit. Nothing visible for automation to pre-solve against.
- One verification to rule them all. The previous double-verification path in the signup flow removed; one legitimate check now protects all guarded surfaces.
- Self-contained payload integrity. Challenge payloads are encrypted and verified on this service. Replays and stale tokens are rejected server-side.
- Per-environment keying. Shield verification uses an environment-specific secret; no cross-environment leakage.
- Per-route enforcement. The challenge gates every sensitive action we proxy, not just sign-ups.
- False-positive review. Confirmed accounts and devices from challenge-fail patterns are reviewed and re-admitted when appropriate.