Offer context
Set a synthetic UK-first offer scenario and select the student or payer perspective.
Phase 05 · Closed for mock-project purposes
The accepted Phase 5 proof of concept demonstrates Funding Readiness as a deterministic, source-labelled journey. It preserves the line between planning, official evidence and future regulated-provider decisions.
P5-D1 · APPROVE
The local prototype proves that the concept can explain a known funding gap, support readiness tasks and disclose a future handoff without collecting sensitive financial data or presenting a lending decision.

Accepted flow
The order matters: context before costs, costs before sources, sources before gap, and comprehension before any simulated handoff.
Set a synthetic UK-first offer scenario and select the student or payer perspective.
Review source-labelled planning estimates without treating them as official evidence requirements.
See official financial-evidence information separately, with source and date context.
Edit synthetic declared sources and calculate the known gap deterministically.
Complete a bounded checklist and see which categories remain unresolved.
Pass a comprehension and consent gate before viewing a simulated provider handoff.
Product system
Funding Readiness is the Phase 5 focus. Pathway Navigator, Compass, Arrival Setup and Ro show how it could connect to the wider student route.
Leads programme, recognition, application, document and departure-readiness steps.
No admissions or immigration decisions.Shows source-labelled costs, funding sources, readiness tasks and unresolved gaps.
No advice, eligibility or approval.Demonstrates travel-package configuration and a transparent future seller handoff.
No inventory, ticketing, payment or refunds.Coordinates labelled accommodation, transfer, connectivity and first-week readiness.
No availability or suitability guarantee.Offers bounded, deterministic prewritten guidance with a visible human-support path.
No live AI or personalized advice.What the POC establishes
Phase 5 closure accepts the implementation under a bounded mock-project decision. It deliberately preserves every missing external gate.
Final Phase 5 record
Phase 5 boundary
Prototype acceptance applies only to the bounded mock-project exercise. No deployment or publication occurred. The accepted implementation does not establish customer demand, partner approval, legal clearance, regulatory approval, commercial viability, security approval or readiness for a real-world launch.