01 · Machine input
61/100 · DO NOT PROGRESS
Original simulated ATS output — preserved, not silently rewritten.
YT-WM-001 · Critical-function proof
See the complete governed change first. The lifecycle and selective Discernment functions are explained underneath.
01 · Machine input
61/100 · DO NOT PROGRESS
Original simulated ATS output — preserved, not silently rewritten.
02 · Why governance intervenes
NOT READY FOR AN ADVERSE FINAL DECISION
The chronology conflicts and the machine output relies partly on factors outside the approved role criteria.
03 · Evidence change
CHRONOLOGY RECONCILED
Provider clarification resolves the date conflict while the original machine score remains unchanged.
04 · Human action
PROCEED TO STRUCTURED INTERVIEW
A named reviewer records the reason. Chloe separately retains the choice to accept or decline the interview.
CASE ORIENTATION
Chloe is an adult early-career candidate. A simulated ATS has scored her 61/100 and recommended “DO NOT PROGRESS.”
The question is not whether RILayer can produce a better score. It is whether the machine-assisted decision is sufficiently evidenced, authorised and governed for an adverse human decision to be made.
As you move through the demonstrator, notice three things:
60-SECOND GOVERNANCE PATH
Controlled click-through · existing synthetic Chloe case · not a live recruitment system · not an open-ended AI sandbox.
ATS OUTPUT
61/100
DO NOT PROGRESS
This is the simulated ATS recommendation. What should happen next?
DUAL-LANE ARCHITECTURE
RILayer keeps Chloe's private reflection separate from the employer's progression decision.
CHLOE'S DECISION
Does this opportunity fit me?
Chloe decides whether the next step fits her direction, priorities and practical situation. Her private reasoning stays in her protected space.
Candidate-Controlled Discernment
MINIMUM AUTHORISED HANDOFF
Status only — not private reasoning
Only the minimum authorised status needed for the next governed step crosses between the two lanes.
EMPLOYER DECISION
Does the authorised evidence justify progression?
The employer decides whether the approved evidence supports offering a structured interview. That decision does not decide whether Chloe accepts the interview.
Case Governance + accountable human action
Chloe's private reflection does not become employer selection evidence.
RILayer governs both decision boundaries without collapsing them into one decision.
Discover happened before this case. This demonstrator shows Discern only.
Adult boundary: ‘Youth Transition’ in YT-WM-001 refers to adult early-career transition. The current controlled prototype is not designed or authorised for use with minors.
DISCOVER
BEFORE RILAYERCompleted before governed RILayer
DISCERN
YOU ARE HERECURRENT DEMONSTRATED PHASE
DEVELOP
LATERWider governed pathway
DEDICATE
LATERWider governed pathway
What this demonstrator is showing
DISCERN — CURRENT DEMONSTRATED PHASE
DISCERN is the RILayer lifecycle phase demonstrated here. Within this case, two governed lanes are visible.
Candidate lane
Candidate-Controlled Discernment
Selective Discernment functions help Chloe examine her own decision.
Employer lane
Employer Case Governance
Case Governance controls examine the machine input, authorised evidence, Decision Readiness, Governance Risk, boundaries and accountable human decision.
Case Governance is not an additional RILayer model and is not a candidate assessment.
Decision Readiness
Plain English: Do we have enough legitimate evidence to make the next decision properly?
Decision Readiness concerns the evidence, clarity, boundaries and authority available for the next decision. It is not a score of Chloe.
Governance Risk
Plain English: What could go wrong in the decision process?
Governance Risk belongs to the evidence, interpretation, system, process, boundaries or decision pathway. It is never a risk score about Chloe.
Candidate-Controlled Discernment
Plain English: Chloe examines her own decision.
RILayer supports the decision process without choosing a career direction for her.
Minimum authorised handoff
Plain English: Only the necessary status crosses the boundary.
Private reasoning does not become employer selection evidence.
Employer Decision Governance
Plain English: Is the employer's next decision properly evidenced and authorised?
The employer-side process governs the machine input and progression decision without taking Chloe's own decision away from her.
Purpose-bound non-routing
Plain English: If a function is not relevant, RILayer does not use it or invent data to activate it.
Non-collection is a governance control.
ALIGN — Coherence check
Plain English: Do the relevant parts now make sense together?
ALIGN must not become an employability score, suitability score or automated permission.
Discover: Discover is the pre-governed orientation space. It may be supported by SCOPE (opens in a new tab), self-reflection, a career adviser, mentor or another trusted environment. Only a sufficiently clear human question and authorised relevant context need enter governed RILayer. Discover does not score, diagnose, prescribe, activate RILayer models or make the decision.
RILayer does not run every model. It identifies only the functions relevant to this decision moment, then keeps the human decision with the right person.
Chloe's question
“Should I continue towards finance and business operations, or widen my direction because progress has been slower than expected?”
PRE-RILAYER DISCOVER
How the question became clear enough to bring into RILayer
Discover is the pre-governed orientation space. It may be supported by SCOPE (opens in a new tab), self-reflection, a career adviser, mentor or another trusted environment. Only a sufficiently clear human question and authorised relevant context need enter governed RILayer. Discover does not score, diagnose, prescribe, activate RILayer models or make the decision.
Used in this walkthrough · 5 functions
Plain-English purpose comes first. The canonical RILayer function name remains visible for traceability, with technical routing detail available on demand.
Direction
DREAM · canonical function
Direction remains meaningful to test: finance / business operations.
Chloe is questioning whether slower progress means she should leave her chosen finance / business-operations direction.
Boundary: RILayer does not recommend a career direction for Chloe.
Pause before interpreting
CALM · canonical function
Mandatory CALM check pending before evidence interpretation.
If the simulated ATS returns DO NOT PROGRESS, Chloe may be tempted to treat the machine output as a verdict about her direction.
Boundary: Non-clinical reflective pacing only; no distress score or diagnosis.
What matters
VALUE · canonical function
The opportunity still fits important priorities, but practical feasibility needs clarification.
Learning, progression, stability, independence and fair opportunity matter to Chloe's next step.
Boundary: VALUE does not morally rank Chloe's priorities.
Practical feasibility
MONEY · canonical function
Practical / financial feasibility still needs evidence.
Salary and location are known; travel pattern, cost and support are not yet fully known.
Boundary: RILayer does not recommend what salary Chloe should accept, provide budgeting advice or make financial decisions for her.
Coherence check
ALIGN · canonical function
Not evaluated yet because required evidence is unresolved.
Direction, priorities, reflective availability, practical feasibility and decision evidence must cohere before the next human-owned step.
Boundary: ALIGN must never become a suitability score or automated permission.
Purpose-bound non-routing · Considered, but not routed · 3 functions
TRAUMA · RHYTHM · CARE — no relevant signal is present. Expand to inspect why each function is deliberately not routed.
Safety & safeguarding boundary
TRAUMA · canonical function
No trauma or safeguarding signal is present in this synthetic case.
Outcome: No TRAUMA routing in YT-WM-001.
Boundary: Autism or an adjustment request must not be treated as a TRAUMA signal.
Routine / pacing
RHYTHM · canonical function
No material routine, energy or pacing pattern requires separate routing for this decision.
Outcome: No RHYTHM routing in YT-WM-001.
Boundary: Do not invent a pattern simply to exercise the model.
Relational / caring load
CARE · canonical function
No material caring or relational-load signal requires separate routing for this decision.
Outcome: No CARE routing in YT-WM-001.
Boundary: Do not collect caring information without a relevant purpose.
Practical questions still open: Required on-site days · Likely travel cost / frequency · Training or travel support · Any timing constraint affecting a start date