Lexsentra
ProcurementBook a pilot
Synthetic demonstration · no real operator assessed

What a Regulatory QA evidence loop looks like.

This sample shows the structure of a bounded Lexsentra evidence report: what the browser observed, what it could not prove, the human review state and how a later run can surface a material regression.

Important: every target, timestamp and observation below is synthetic. This is not a customer case study, regulatory finding, certification or legal determination.
GBJurisdiction
RTS 12BControl family
4 / 5Observable states captured
Approved with notesExample human review

Scope

  • Example target
    https://demo.operator.invalid/limits
  • Execution boundary
    Public/read-only browser observation; no deposits, withdrawals, wagers or live limit mutations.
  • Regulatory context
    UKGC RTS 12B wording effective 30 September 2026.
  • Evidence intent
    Technical observation for human compliance review, not an automated legal verdict.

Review state

Approved with notes · synthetic example

The reviewer accepts the captured browser evidence as a useful baseline for the observable UI controls. Gross-limit mechanics, account-level enforcement and reached-limit blocking remain outside what this public browser run can prove.

Reviewer note: use this baseline for release regression; obtain authorized account/backend evidence for enforcement behaviour before drawing any compliance conclusion.

Evidence observations

RTS12-002 · ENTRY POINTFinancial-limit entry point is directly visible
Observed

The browser can identify a visible direct link into the financial-limit journey on the agreed surface. This is an observable interface fact, not proof that every eligible customer receives the same path.

RTS12-013 · DURATIONS24 hours, 7 days and one month are selectable
Observed

The example financial-limit interface exposes all three fixed duration options in selectable controls.

RTS12-009 · LIMIT VALUEFree-text amount entry is visible in limit context
Observed

A visible numeric/free-text amount control is captured as positive UI evidence. The observation does not prove account-level application or backend validation.

RTS12-014 · LIMIT TYPE“Deposit limit” is presented as a selectable limit
Partial

The label is visible and selectable, but the browser alone cannot prove that the underlying calculation is gross deposits rather than another financial-limit mechanic.

RTS12 ENFORCEMENT · ACCOUNT STATEReached-limit deposit blocking cannot be established
Not observable

Confirming account-level enforcement requires an explicitly authorized controlled journey and potentially backend evidence. The public run stops rather than simulating a deposit.

Example regression signal

A later run is compared with the reviewed baseline rather than interpreted in isolation.

Δ
Previously observed 7-day duration is no longer selectable

Because the same interface was observed in the baseline and the current run is conclusive, Lexsentra can surface this as a material evidence regression for human review.

?
If the journey becomes login-gated or indeterminate

The result becomes not observable / indeterminate, not a false violation alert.

What this report does not claim

  • It does not say the operator is “UKGC compliant”.
  • It does not replace an approved test house where formal third-party assurance is required.
  • It does not prove backend enforcement, account state or legal interpretation from labels alone.
  • It does not bypass CAPTCHA, MFA, geo controls or authentication boundaries.
  • It does not perform deposits, withdrawals, wagers or destructive account actions.

See the same evidence loop on one real surface.

Bring one UK journey. Public first value starts from a URL; authenticated observation is separate, explicitly authorized and read-only.

Run public-page checkPricingBook 30-minute pilot