Skip to main content
RILayer

Evidence & validation

Prove what works. Record what does not. Scale only what the evidence supports.

RILayer is currently progressing through controlled proof-of-concept and prototype validation. YT-WM-001 is the current reference case used to test whether the core governance sequence can turn an adverse machine recommendation into a transparent, bounded and human-accountable decision process.
Examine YT-WM-001View validation method

Evidence position

A demonstrator is evidence of a mechanism — not evidence of live outcomes.

The current browser build is a controlled technical artifact. External pilot evidence remains the next validation step, not a claim already made.

Claims bounded
Failures retained
Remediation recorded
Human sign-off

Reference proof-of-concept · YT-WM-001

The Chloe Taylor case is the current flagship evidence artifact.

A fictional adult early-career case begins with a simulated ATS result of 61/100 — DO NOT PROGRESS. The purpose is to test whether RILayer can govern the reasoning between machine recommendation and accountable human action without replacing the original score or making the final decision autonomously.

What the current proof demonstrates

  • The original simulated machine recommendation remains visibly separate from governed human judgement.
  • Evidence is separated from inference, missing information and restricted factors.
  • Decision Readiness is treated as a governance condition rather than a score of Chloe.
  • Governance Risk is surfaced as risk in the decision process, not risk about the person.
  • Professional, system and information boundaries remain explicit.
  • The case is routed rather than automatically decided.
  • Employer and candidate decisions remain separate and attributable.
  • The Decision Evidence Record preserves the machine input, evidence change and human reason.
Launch the demonstratorView canonical reference record

What this does not prove

  • candidate outcome effectiveness
  • organisational performance improvement
  • live employer adoption
  • cross-sector transferability
  • production-scale reliability or security

These exclusions are part of the evidence discipline. They define the boundary between what has been demonstrated, what is under validation and what remains a future hypothesis.

Current maturity objective

Proof-of-concept now. Controlled prototype validation next.

RILayer uses TRL language as a validation objective rather than a self-certification. The current work is to retain evidence that the critical governance mechanism and integrated browser components behave as intended under controlled, repeatable conditions.
  1. 01Current evidence focus

    TRL 3 objective · proof-of-concept

    Demonstrate the critical governance mechanism through bounded synthetic cases and retain evidence that key functions behave as intended.
  2. 02Current technical objective

    TRL 4 objective · controlled prototype validation

    Test the integrated browser components together: evidence classification, Decision Readiness, Governance Risk, boundaries, routing, human action and the Decision Evidence Record.
  3. 03Beyond the current claim

    External relevant-environment validation

    A future external Youth Transition pilot may test defined claims in a relevant organisational environment. Until that happens and evidence is reviewed, RILayer should not claim operational validation or proven cross-sector performance.

Validation discipline

A six-stage route from claim to governed evidence.

A credible validation programme records not only what passed, but also what failed, why it failed, what changed and whether the rerun supports a narrower or wider claim.
  1. 01

    Define the testable claim

    State the specific decision-process change a controlled test is intended to examine.
  2. 02

    Freeze the baseline

    Record the current workflow, evidence, authority, risk pattern and expected outcomes before intervention.
  3. 03

    Run bounded cases

    Apply the controls to representative and stress-test scenarios without treating proposals as authorised decisions.
  4. 04

    Record deviations

    Capture failures, ambiguities, boundary breaches and unsupported outputs rather than hiding them.
  5. 05

    Remediate and rerun

    Correct the relevant logic, evidence or workflow and test failed cases again.
  6. 06

    Decide what the evidence supports

    Approve, limit, adapt, pause or reject wider testing based on retained evidence.

Failure is validation evidence too.

Deviation, remediation and rerun evidence should remain visible rather than being removed from the story because a test did not support the original expectation.

Future validation scenarios

Other contexts are hypotheses for adaptation — not current validation evidence.

The scenarios below show where the same governance architecture may be tested after the flagship Youth Transition pathway produces evidence strong enough to justify transferability work.

Future scenario 01

Human–AI decision governance

AI-assisted workflows, copilots, dashboards, automation and agentic systems.

Validation question

Can human ownership, evidence requirements and escalation remain visible when automated outputs influence action?

Future scenario 02

Operational escalation

Service delivery, incidents, complaints and operational continuity.

Validation question

Can evidence, routing and decision ownership improve consistency without adding unnecessary bureaucracy?

Future scenario 03

Financial risk & underwriting

Credit, underwriting, exceptions and regulated risk decisions.

Validation question

Can override rationale, uncertainty and authority boundaries remain reviewable under pressure?

Future scenario 04

Health, care & people-sensitive judgement

Health, care, wellbeing and safeguarding-adjacent organisational settings.

Validation question

Can governance structure strengthen escalation while preserving professional responsibility?

Evidence before expansion

Scale only what the retained evidence can defend.

The next external conversation should test the mechanism and the validation design — not assume wider rollout is automatically justified.
View YT-WM-001Discuss a Validation Partnership

Validation partnership

Govern the judgement moment before action.

Begin with one defined decision environment, examine the governance mechanism against real stakeholder needs and evidence, then decide what further validation is justified.

Human accountabilityEvidence traceabilityBounded validationDesigned for transferability
Discuss a Validation PartnershipView the Demonstrator