Project

Turing Digital Intelligence Validation Platform

A three-role workflow platform for applications, expert review, admission, and incubation, grounded in permissions, attachments, and audit logs.

Vue 3 · Element Plus · ECharts · Spring Boot · MyBatis · MySQL · JWT/BCrypt

2025.09-2026.01

Product Snapshot

Role: Full-stack developer, database course team project
Users: Project applicants, expert reviewers, and platform administrators.
Stage: Relational model, three-role permissions, core workflow, dashboard, and demo completed in 2025.09-2026.01.
Focus: Workflow modeling, RBAC, attachments and audit logs, and front-end/back-end integration.
Validation: Implemented the full application-to-incubation lifecycle across about 103 Java, 20 Vue, and 15 SQL files.
Public Proof: Runnable system, ER model, source structure, database scripts, and course presentation materials.

Next Step

Portfolio PDF About the Founder Email

The problem

Concept-validation programs move through multiple roles and states. When that workflow lives in spreadsheets and chat threads, permissions, versions, and accountability become difficult to control.

What I built

I helped translate the process into a relational model and an executable platform for Applicant, Expert, and Admin roles. It covered submission, document handling, review, admission, and incubation.

The backend used Spring Boot, MyBatis, and MySQL; the interface used Vue 3, Element Plus, and ECharts. JWT/BCrypt authentication, attachments, audit logs, and an administrative dashboard completed the workflow.

Result and evidence

The system implemented three-role permissions and the full lifecycle. The codebase contains roughly 103 Java files, 20 Vue files, and 15 SQL files, corroborated by the ER model, database scripts, runnable application, and presentation materials.

What I learned

Database design is not drawing tables first and adding screens later. Stable models emerge from understanding roles, state transitions, history, and failure paths together.