Road RiskR.I.S.K. research platform

Authorship and contribution

AuthorshipHelp receivedSource boundary

What I Built and What Help I Used

This page explains what the Road Risk submission contains, what tools and data sources are involved, and what attribution details should be checked before final judging.

Back to Judge RouteRead Project

Page Purpose

Contribution and source boundaries

Use this page as the contribution and acknowledgement checkpoint for public review.

What to verify
Which project surfaces were built, which tools were used, and which source acknowledgements are required.
Help boundary
Assistance tools and external feedback are support inputs; final interpretation and claims remain the project owner's responsibility.
Source boundary
Data and service acknowledgements do not imply endorsement of Road Risk outputs.
Private data
This page does not expose account identifiers, credentials, dashboard ownership records, or session details.

Contribution

What I personally built and assembled

These items are visible in the current repository and public site. They describe submitted project surfaces rather than claiming that every line was written without tool support.

Public research site

Project, Method, Results, References, Assumptions, Validation, Glossary, Licensing, Judge Route, and Authorship pages.

Live App V2 workspace

Selected-road analysis, scenario controls, graphing, Maths traces, RSA context, imports, exports, and evidence packages.

Private workspace

Account, Dashboard, projects, imports, datasets, Evidence & Reports, and profile settings.

Audit and QA system

Audit Library categories, route checks, copy checks, public evidence checks, and command-gate scripts.

Tools and services

Libraries, platforms, and support tools

Framework

Next.js, React, TypeScript, Tailwind-style utility classes, and server-side route handling.

Maps and data

Leaflet, OpenStreetMap-derived geometry, MapTiler map rendering, and OpenRouteService where configured.

Authentication

Firebase Authentication, Firebase Admin verified sessions, Firestore user profiles, and Firebase Storage profile images.

Assistance tools

AI-assisted coding and debugging tools were used as support tools. Final project interpretation and competition claims remain the project owner's responsibility.

Help received

Attribution that should be checked before final submission

Teacher or school guidance

Add named guidance here before final judging if competition rules require personal attribution.

External feedback

Record any engineering, road-safety, coding, or presentation feedback received outside normal project supervision.

Data providers

Acknowledge OpenStreetMap contributors, MapTiler, OpenRouteService, and the Road Safety Authority where their data or services are used.

Source date discipline

RSA-derived outputs require source acknowledgement and a data-current date before publication.

Boundaries

What this page does not claim

No private account details

Authorship information does not expose Firebase identifiers, session data, provider credentials, account tokens, service-account data, or private dashboard ownership records.

No scientific overclaim

Authorship transparency does not change the scientific boundary: Road Risk is a comparative research model and evidence workspace, not an official safety rating or observed crash predictor.

Review links

Where to inspect the project

Judge Route

Use the five-minute review route.

Open

Project

Read the research question, variables, controls, and next work.

Open

Method

Inspect formulas, assumptions, and data boundaries.

Open

Results

Review Phase 1 public model-behaviour evidence.

Open

References

Check source and service acknowledgements.

Open

Submission note

Before final judging