JUNIQ Infrastructure

The operating layer for students, professionals and educators.

A clean internal structure for secure login, files, recordings, saved recordings, summaries, actions, referrals, emails, professional notes and education outputs.

Identity

Login + passwords

Production needs secure authentication, password reset, MFA, role-based permissions and organisation accounts.

Files

Student/client/patient/matter files

Every record should attach to the right file with access permissions and an audit history.

Recording

Consent + recording

Capture audio, transcript, speaker labels, timestamps, consent and device information.

AI outputs

Summaries + notes

JUNI creates student notes, legal notes, health SOAP notes, property notes, business notes and action lists.

Actions

Refer, email, draft

Automatically draft referrals, emails, deeds, contracts, certificates, follow-ups and task lists for approval.

Compliance

Privacy + audit

Production requires encryption, access logs, consent records, retention rules and human approval controls.

Core database objects

ObjectPurposeExamples
UserSecure account and roleStudent, educator, lawyer, doctor, allied health, agent, business user
OrganisationSchool, university, firm, clinic or businessuniversity, law firm, clinic, agency
FileConfidential storage containerStudent subject file, matter file, patient file, property file
RecordingAudio/transcript/metadataForum, tutorial, consultation, meeting
OutputAI-generated draft documentStudy notes, SOAP note, legal note, deed outline, referral
ActionTask or follow-upEmail all parties, refer to professional, print notes, review document
ConsentPermission to record/use dataAccepted before recording, participant list, date/time
Audit LogTrust and accountabilityWho viewed, edited, downloaded, emailed or approved