Ankit PrajapatiAcademic governance · Institutional AI

Recruiter access · Interactive systems

Don’t just read the work. Operate it.

Three complete institutional-governance applications in one controlled environment. Enter different roles, move work through approval, inspect evidence and export results. The workflows are preserved; private records are replaced with demonstration data.

3operational applications
20+role and workflow views
100%recruiter-safe data
Oneunified launch point

Working creations

Each application opens inside the same portfolio shell. Use the guide in the top bar for a short, purposeful evaluation path. State persists locally in your browser and can be reset at any time.

Evidence assuranceP

PRAMAAN

Operational demo

Evidence governance, provenance, role accountability and approval history for institutional assurance.

Try these
  • Enter as a different institutional role
  • Inspect the evidence atlas
  • Move a record through review
  • Export a governance view
Continuous qualityनि

NIRANTAR

Operational demo

Continuous quality assurance, metric ownership, annual allocation and multi-role institutional review.

Try these
  • Sign in as an IQAC or academic role
  • Explore criterion and metric ledgers
  • Allocate an AQAR cycle
  • Generate a structured evidence pack
Institutional dataI

KU-IDMS

Operational demo

A governed institutional data layer for NEP returns, assignment, submission, verification, approval and audit.

Try these
  • Enter as central authority or data owner
  • Assign and update a return
  • Submit, verify and approve
  • Inspect audit and export views

A useful ten-minute review

Evaluate the governing logic, not only the surface. Each system exposes the same institutional pattern through a different problem.

01

Choose a role

See how authority and visibility change with responsibility.

02

Move the work

Create, submit, return, verify or approve a controlled record.

03

Inspect evidence

Follow source, ownership, status and correction history.

04

Judge the model

Assess whether the logic could survive institutional scrutiny.

Engineering creation · Working code

KU-RISE timetable engine

The fourth creation is a constraint solver rather than a browser portal. Its working Python engine schedules 381 weekly sessions across six schools and three campuses, then independently validates the result.

381sessions placed
0validation conflicts
3campuses
OPTIMALsolver status

Switch destination

PRAMAANEvidence assuranceNIRANTARContinuous qualityKU-IDMSInstitutional dataProfileReturn to Ankit’s professional profile