Back to all projects

Research / App case study

UGNAY

A Java and Spring research-continuity platform linking problems, studies, objectives, requirements, tests, and outputs through hybrid retrieval, warehouse snapshots, traceability, and RQL.

Research-continuity platform prototype

01 / Overview

What it’s built for.

Preserve an explainable chain from a real problem through related studies, human decisions, implementation evidence, and a successor’s continuity package.

Who it serves

Students, advisers, coordinators, and curators reviewing research alignment and handoff.

02 / Features

Inside the app.

Research discovery

Ingest permitted documents, search a catalogue, and compare lexical, semantic, and hybrid retrieval.

Alignment and changes

Link requirements, features, tests, and outputs; review findings and typed change proposals.

Continuity and laboratory

Build evidence-derived handoffs, run RQL queries, and inspect immutable research-warehouse snapshots.

03 / Workflow

From task to outcome.

  1. Curate research sources and submit a problem with objectives and evidence.

  2. Review related studies and record an authorized human disposition.

  3. Maintain trace links, test evidence, baselines, and change decisions.

  4. Prepare a continuity package and review successor claims.

04 / Technical layers

How the pieces work.

Interface

React · TypeScript · Vite

Research Atlas, alignment workspaces, and laboratory views share a same-origin application.

Application

Java · Spring Boot · Spring Security

Role-scoped workflows preserve human decisions, audit history, and versioned evidence.

Database and documents

MySQL · Flyway · Private document objects

Operational records and immutable warehouse loads retain continuity and provenance.

Research engines

RQL · TF-IDF · Optional E5/ONNX

A bounded interpreter and versioned retrieval arms support reproducible algorithm comparison.

05 / Limitations

What to keep in mind.

  • The platform recommends and explains; it does not automatically approve a thesis or declare plagiarism.
  • The documented Windows Lite setup requires matching release assets and clean-install verification before installation acceptance can be claimed.
  • Unavailable evidence is labeled partial or unassessed rather than replaced with demo data.

06 / Evidence

Follow the source.

These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.