Skip to main content
RILayer

Deployment & validation pathways

Start with Youth Transition. Prove the mechanism before testing transferability.

RILayer's immediate objective is not broad deployment. It is to establish credible evidence that the governance mechanism works as intended within one bounded domain, then decide what the evidence justifies next.

Recommended principle

Do not start everywhere.

Start where the decision environment is bounded, the mechanism can be challenged and retained evidence can determine whether wider testing is justified.

Bounded first phase
Clear ownership
Evidence retained
Review before expansion

Current validation pathway

One evidence ladder from demonstrator to transferability testing.

The sequence separates what the demonstrator proves, what the browser prototype is intended to validate and what a future external pilot would need to test before broader claims can be made.

Current position

YT-WM-001 is demonstrated. Controlled browser validation is current. PAVRA is the intended next external pathway.

  1. 01Demonstrated

    Controlled fictional demonstrator — YT-WM-001

    Demonstrate the governance mechanism, its boundaries and the distinction between machine input and accountable human judgement.
  2. 02Current technical validation

    Browser prototype validation

    Test whether the critical components work together consistently in a controlled environment: evidence, Decision Readiness, Governance Risk, boundaries, route, human action and the Decision Evidence Record.
  3. 03Next external pathway

    PAVRA Youth Transition pilot (opens in a new tab)

    Subject to partner agreement, governance and pilot readiness, test defined claims in a relevant external Youth Transition environment.
  4. 04Evidence-dependent

    Evidence review

    Determine what has actually been supported, what failed, what must change and whether the evidence justifies broader testing.
  5. 05Only if justified

    Transferability testing

    Only after the flagship pathway produces credible evidence should additional organisational or sector contexts be examined.

Demonstrator vs pilot

A demonstrator and a pilot have different jobs.

The demonstrator shows the proposed mechanism in a controlled fictional case. A pilot tests defined claims under agreed conditions and retains evidence about what worked, what failed and what changed. Neither should be presented as proof of wider deployment until the evidence supports that conclusion.

Current artifact

Demonstrated now

The browser prototype can show a controlled machine recommendation, evidence challenge, readiness and risk logic, governed routing, separate human decisions and a reference record.

Current technical work

Under validation

Repeatable checks test whether the critical browser components behave coherently under controlled synthetic conditions.

External evidence

Not yet claimed

Live employer adoption, operational outcomes, relevant-environment pilot results, production-scale reliability and cross-sector performance remain outside the present claim.

Evidence review

Next decision

Evidence should determine whether to proceed to external validation, narrow the claim, remediate the prototype, pause or stop.

Future pathways

What might be tested after the flagship pathway?

These contexts explain the intended transferability hypothesis. They are deliberately subordinate to the current Youth Transition validation pathway.

Human–AI governance

Potential future testing in AI-assisted workflows, copilots, automation and digital decision environments.

Enterprise risk & compliance

Potential future testing where financial, regulatory, legal, operational or people exposure makes judgement consequential.

Health, care & people-sensitive judgement

Potential future testing where professional authority and escalation boundaries must remain explicit.

Operational escalation

Potential future testing of evidence, routing and accountability in incidents, service delivery and complaints.

Employer readiness

Adjacent testing around whether organisations are ready to create and support opportunities responsibly.

Current engagement

Bring a validation question, not an assumption of rollout.

A useful conversation should clarify the decision environment, the testable claim, governance boundaries, evidence requirements and what would justify a next step.

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