EdTech Enterprise Architecture
restricted · internal review copy
© 2026–27 · VLabsDev, IIT Bombay
VLabs Enterprise Architecture
EdTech Architecture · 12+ / UG / PG / ITIs & skilling · school: future provision
CORE INFRASTRUCTURE — registries · records · value
Learner RegistryAPAAR1
Instructor RegistryVIDWAN1
Institute RegistryAISHE · DGT/NCVT1
Ed-Tech Product Registryvia certification1
Record Lockeron DigiLocker2
Certification Managerissue · verify · revoke2
Credit BankABC · NCrF4
Scholarship ExchangeNSP · DBT5
Policy Analyticsanonymised5
INTEROPERABILITY — runtime rails, no storage, DPDP-compliant
Auth & ID Resolution3
Consent Manageraudit-logged · guardian consent3
Exchange Gateway3
Credential Standardnational Record Standard · NSQF/NCrF2
Learning Services Networkcourses · events · FDPs · ratings5
Interoperability Layer
Open APIs — identity · registry · consent · record exchange · credits & verification · network protocol
APPLICATIONS — network participants
Learning & content SWAYAM · NPTEL · SWAYAM Prabha · Virtual Labs · Spoken Tutorial · FOSSEE · e-Yantra · eGyanKosh · e-PG Pathshala · NDLI · Skill India Digital
Research & institution NTA (CUET/JEE/NEET) · Boards — XII via DigiLocker (school: future) · e-ShodhSindhu · Shodh Shuddhi · Shodhganga · Samarth (ERP) · NATS/NAPS · + private EdTech
Learner Record App (LRA)view records · manage consent3
Employer / HEI Verifyrecord consumer · QR verify5
Platform capabilitiesoutreach · course registration · grading · course building · certificate generation · analytics
POINTS OF SERVICE — delivery channels
Mobile
Web
LMS
Classroom
Chatbot / IVR
Assisted Accessschool / CSC desk
Foundational DPI — Aadhaar · e-Sign · DigiLocker · UPI · Baadal · Bhashini
Governance — MoE / MSDE · standards & trust · sandbox & certification · DPDP · grievance · closed-institution custodian · GIGW · legacy digitisation
n build phase 1–5 n consent flow: request → discover → consent → exchange records stay with the issuer dotted = participants, not core click any box: gold lines show its connections · dashed = access, solid = records via rails
EdTech Interoperability Flow · how a record moves: consent → discovery → exchange → verification
Requestercertified app · authenticated on every call
Exchange Gatewayasync callbacks · queues for offline issuers · no storage
Consent Managercoded purposes · time-bound · revocable · guardian (DPDP)
Learner — LRAapprove · deny · revoke · assisted mode, no smartphone
Issuersource of truth · keys in registries · locker serves consented copies
1
consent request — purpose · record types · validity (routed via Gateway)
2
notify learner — guardian if minor (DPDP)
3
approve / deny → signed consent artefact · audit-logged
4
consent granted — artefact reference returned · deny → request closed
5
fetch request + consent artefact
6
verify artefact & revocation · resolve Learner ID · discover issuer · route — nothing stored
7
record returned — signed per the national Record Standard, encrypted, via Gateway callback
verify signatureCertification Manager · registry keys → use record
8
revocable anytime → future fetches fail
Underpins every hop — Auth & ID Resolution (each call authenticated) · Open APIs: identity · registry · consent · record exchange · verification · audit log on all steps
Design guarantees — gateway holds no records · issuer remains source of truth · scoped tokens: Learner ID never propagates · consent revocable network-wide · records verifiable offline via QR signature
National deployment — one protocol, state on-ramps (Concurrent List) · federation by issuer, not geography · sized for 8–9 cr learners (NEP 50% GER, 2035; 4.33 cr today) · peaks: admissions · result days · placements
● green chip = flow step 1–8 · green lanes = interoperability rails · blue lane = learner · click a participant or step chip · ○ = routed via Gateway
EdTech Tech Layout · decided national topology · D1–D4 = settled design decisions
PARTICIPANT EDGE
State on-rampsnodal agencies · onboarding · helpdesks · legacy digitisation drives
Issuer adaptersreference implementations · shared via affiliating university · Samarth-class ERP integration
Consumer apps · LRAcertified per role · scoped tokens only
Auth & ID Resolutionstateless · horizontal scale-out · tightest latency budget
National Exchange Gateway — one logical gatewayD3
Regional replica — North
Regional replica — South
Regional replica — East
Regional replica — West
async queue & callback fabricretries bounded by consent-artefact validity · offline-issuer tolerant
routing metadata + audit events onlyno record payloads ever stored
Licensed Consent Managers — common signed artefact spec · substitutable (AA pattern)D1
CM — A
CM — B
+ licensed …
CORE STATE
INTEROPERABILITY RAILS
Registries — Learner · Instructor · Institute · Productissuer & product signing keys anchored here · rotation without re-issue · envelope DID-ready, DIDs not adoptedD2
DigiLocker — primary Record Lockeralready carries Class XII marksheets · owner access directD4
certified third-party lockersopen Locker API · later phase · no redesign required
Certification Managerrevocation lists · key-rotation registry · offline QR verification root
Audit plane — immutable, append-only · every grant, fetch, denial, revocation · learner-visible via LRA
Promotion path — sandbox → conformance suites per API family → production · certification writes the Product Registry entry
DPDP boundary — scoped tokens (Learner ID never propagates) · coded purposes · guardian consent · breach protocol
● gold chip = settled decision · D1 multiple licensed consent managers · D2 registry-anchored keys · D3 one logical gateway, regional replicas · D4 DigiLocker-first behind an open Locker API · green ①–④ = same macro flow as other tabs · click a box or a D-chip
EdTech Tools & Tech · build stack for the team · mirrors the Technical Layout box-for-box
PARTICIPANT EDGE
Onboarding & support toolingportal + docs (Docusaurus) · helpdesk (Zammad-class) · training kitscandidate
Issuer SDKs & pluginsOpenAPI-generated SDKs (Java · Node · PHP) · Inji Certify (OpenID4VCI issuance) · Samarth plugin · LMS via LTI 1.3candidate
App stack — LRA & consumersInji Wallet stack (MOSIP) — OpenID4VP · BLE · offline QR & paper · Bhashini APIs · alt: CREDEBL/ADEYAstandard
IAMOIDC / OAuth 2.1 provider (Keycloak — bundled by Sunbird RC) · scoped short-lived JWTstandard
INTEROPERABILITY RAILS
Gateway stack
API gatewayKong / APISIXcandidate
K8s multi-regionMeghRaj · Baadalstandard
REST/JSON + webhooksOpenAPI 3standard
mTLS between participantsstandard
Apache Kafkaqueues · retries · dead-letter · callback fabriccandidate
Audit logappend-only, hash-chained · Kafka → object storecandidate
Consent stack
signed JWS artefactsstandard
reference CMopen-sourcedcandidate
CM certification suitecandidate
CORE STATE
Sunbird RC — registries + VC issuanceexisting Indian open-source registry & credentials stack · PostgreSQL · search indexstandard
DigiLocker integrationexisting issuer & requester APIs — XII marksheets already flow herestandard
Locker API specOpenAPI 3 · published now, third parties latercandidate
Revocation & statusW3C Bitstring Status List · Inji Verify (QR) · key registry · HSM-rooted signingstandard
Observability — OpenTelemetry · Prometheus · Grafana · SLO dashboards per rail · admission-season load tests (k6)
Delivery — GitLab CI · Terraform · containerised conformance suites per API family — sandbox runs the same containers as production
Security — HSM signing roots · Vault-class key management · DPDP data-map · VAPT gate before every promotion
green tag = standard / existing precedent · gold tag = candidate, team to evaluate · same map as Technical Layout — this tab answers "with what" · click any box
VLabs Enterprise Architecture · with SWAYAM · NPTEL · FOSSEE as peers · only linked components shown
CORE INFRASTRUCTURE — what these four touch
Learner Registrylearner identity for enrolment & certificates
Instructor Registrycourse faculty identity
Institute RegistryIITs & host institutions · platform keys anchor here
Record Lockertheir certificates land here
Certification Manageranchors & revokes their certificates
Credit BankSWAYAM / NPTEL credits via ABC
Policy Analyticsplatform usage aggregates
INTEROPERABILITY — all rails in use
Auth & ID Resolutionauthenticates platforms · resolves learners
Consent Managergoverns any fetch of learner records
Exchange Gatewayall four issue through here
Credential Standardtheir certificate format · NSQF/NCrF
Learning Services Networkwhere their courses are discovered · ratings
THE FOUR PLATFORMS + linked apps
Virtual Labsexperiments · lab completion certificates · credit-ready (target state)
SWAYAMcredit-bearing MOOCs
NPTELcourses · proctored certification
FOSSEEFOSS tools · workshops & honour certificates
Learner Record App (LRA)view earned certificates · credits · consents
Employer / HEI Verifyverifies these certificates daily
Platform capabilitieseach runs: delivery · assessment · certificate generation
POINTS OF SERVICE — channels these four actually use
Mobile
Web
LMSSWAYAM-NPTEL local chapters · college systems
ClassroomVirtual Labs' natural habitat
click any box: gold lines show its connections · dashed = access, solid = records via rails scoped view — Product Registry & Scholarship Exchange omitted by design; platform keys anchor at host institutions here
VLabs LMS Architecture · Moodle + CodeRunner/Jobe + analytics + outreach · recreated from the original diagram, flows preserved
VLabs technical architecture
Planned components Security (DPDP)consent · scoped tokens · audit Single Sign-On (SSO)one identity across Moodle · OutReach · labs — seeds from Auth Plugin (IdP) Certification Servicelab completions → Certification Manager Template Serviceexperiment & course templates Chatbotlearner support Course Registrationenrolment flows Eventsworkshops · outreach Coursework Ratingsfeedback → services network
Upgrade path → national rails — Auth Plugin (IdP) → Learner ID (APAAR) via Auth & ID rail · lab completions → Certification Manager & Credit Bank via Exchange Gateway · Logstore → Analytics feed → Policy Analytics (anonymised)
original diagram · hover a component to light its flows — the gold strokes are traced from the artwork itself · click to lock, click canvas to release
VLabs Outreach → Architecture Map · Outreach flow summarised to five stages, mapped to the technical (current + planned) and enterprise (target) views
OUTREACH FLOW — summary
TECH ARCHITECTURE — current · dotted = planned build
ENTERPRISE ARCHITECTURE — target state
1
Onboard & EOIAdmin creates HoI account → sign-up → EOI (Form 1 new / Form 2 existing nodal centre) → Admin review & approval → coordinator accounts
OutReach PlatformSecurity (DPDP)Single Sign-On (SSO)
Institute RegistryInstructor RegistryAuth & ID railConsent Manager (guardian)Exchange Gateway
2
Annual planningdepartment planners → nodal consolidation & signatures → upload → Admin validation
OutReach PlatformTemplate ServiceEvents
Learning Services Network
3
Conduct workshopsstudents register / login → select branch · semester · discipline · lab · experiment → run labs
Anonymous Auth ServiceLMS Core (Moodle)CodeRunner → JobeContent Repository (CDN)ChatbotCourse RegistrationSingle Sign-On (SSO)
Learner RegistryAuth & ID railConsent Manager (guardian)
4
Report & validateattendance (≥10 students rule) · report + notice + group photo → pending → Admin approval
Analytics ServiceCertification ServiceTemplate Service
Certification ManagerRecord LockerCredit Bank (credit-ready)Credential Standard (Record Standard)Exchange Gateway
5
Measure & feedbackusage stats · COP stats · student feedback → coordinator & Admin dashboards
Analytics ServiceData StoreOutReach PlatformCoursework Ratings
Exchange GatewayPolicy Analytics
click a stage → its components light · click a component → every stage it serves lights · solid = running today · dotted gold = planned build · dashed navy = national target state
EdTech Record Standard · PROPOSAL · the payload spec behind the rails — what a record looks like on the wire
1 · designIndian base specification — an India-owned signed-record format, published and versioned domesticallysovereign spec in the DPI tradition (Aadhaar · UPI · DEPA) · ELM / 1EdTech studied as prior art, not adopted · international mapping offered only as an export profile
2 · profileNational record profiles — six artefacts, mandatory elements, SHALL-bind vocabularieseach record = one signed artefact · keys anchored in registries (D2) · lands in DigiLocker (D4) · verifiable offline via QR / paper (Inji)
3 · bindIndian terminology — shared code systems every profile draws fromcode systems below · APAAR-class learner ID + multilingual field maps (22 scheduled languages) bound in every profile
ProfileCarriesSHALL-bind vocabulariesIssued by
EnrollmentRecordadmission · registration
learner ↔ institute ↔ programme link · start/leave dates · feeds discovery, never payload-stored at Gateway
UDISE+ / AISHENCF taxonomy
institute
AssessmentRecordsingle result event
exam / practical / viva outcome · grading scheme declared, not assumed · atomic — transcripts bundle these
NCF taxonomyNSQF level
institute · board · assessment agency
TranscriptRecordconsolidated statement
semester / annual composition bundling AssessmentRecords · one attested statement over many atomic results
NCrF creditsNCF taxonomy
board · university
CertificateRecorddegree · diploma · micro-credential
the award itself · revocation via Certification Manager lists · ISCED-F attached only on the export profile
NSQF levelNOS / QP (NCVET)ISCED-F (export)
awarding body
CreditRecordNCrF credit entry
credit points + level → Academic Bank of Credits · formal, vocational and informal learning all credit-bearing under NCrF
NCrF creditsNSQF level
certified issuer → ABC
ParticipationRecordnon-formal · informalVLabs experiment completion = first candidate artefact
workshop · outreach · virtual-lab experiment completion · lowest issuance bar, same verification rigour
NOS / QP (NCVET)NCF taxonomy
any registered provider
Code systems NCrF credit points · levels NSQF skill levels NOS / QP NCVET UDISE+ · AISHE institution IDs NCF taxonomy subjects · activities ISCED-F export-only map APAAR-class learner ID all profiles Language maps all profiles · 22 scheduled
Payload spec only — sits behind the Credential Standard rail · solid-line record flows · consent, Gateway, mediation rule untouched
Steward — a national education-standards body owns the versioned implementation guide · its conformance suite writes the Product Registry certification entry
Local-first — offline QR & paper verification (Inji) · federated registries, no central DB · NCrF credits for informal learning · DigiLocker wallet by default
PROPOSAL · India-owned specification — global models (ELM · 1EdTech) reviewed for lessons only · click a profile row or a code-system chip
Record Standard — Codes, IDs & Envelope · PROPOSAL v0.1 · layer 3 expanded · code tables verified against published national frameworks · green = published · gold dotted = proposed here
Identifier scheme — who and what every record points at
IdentifierFormatAnchored inRule
Learner IDpublished 12-digit lifelong number Learner Registry consent-based issuance via school data system · never leaves Auth — downstream sees scoped tokens only (DPDP)
School IDpublished 11-digit · SS·DD·BB + 5-digit school Institute Registry geography-encoded (state·district·block) · permanent for the school’s life · school records: future-provision scope, code cited now
Higher-ed institution IDpublished U-nnnn · C-nnnnn · S-nnnnn Institute Registry category-prefixed — university / affiliated college / standalone · affiliation lifecycle tracked at source
Skilling qualification codepublished SSC/Qnnnn · SSC/Nnnnn e.g. ELE/Q4605 national qualification register (external source) Q = qualification pack, N = occupational standard · whole-number versions · approval → revision → deactivation lifecycle
Issuer key IDproposed registry key reference + version all four registries (D2) keys rotate without re-issuing records · verification always resolves the key via the registry, never trusts the record alone
Record URIproposed rec://{issuer}/{profile}/{uuid} assigned at issuance globally unique · resolvable only through a consented fetch — the URI alone reveals nothing about the learner
Signed record envelope — cross-section of one signed artefact
1 · headerspec version · profile name (one of the six) · record URI · issue date
2 · subjectlearner reference — scoped token, never the raw Learner ID
3 · payloadthe profile’s fields (layer 2) · institution IDs · multilingual field maps — 22 scheduled languages
4 · terminologyevery coded field carries code system + code + version — tables below
5 · signatureissuer key ID resolved via registry (D2) · tamper-evident over 1–4
6 · statusrevocation pointer → Certification Manager lists · checked on every verification
7 · offline packcompact QR / printable paper form of 1–6 · verifiable with no connectivity · same signature root
Code tables — verified national vocabularies (layer 3)
NCrF level ladderpublished
one ladder across school · higher · vocational — levels are years-of-assessed-learning, not streams
0pre–Class 5 (800–1000 hrs/yr band) 1–4Class 5 → 1 · Class 8 → 2 · Class 10 → 3 · Class 12 → 4 (160 school credits cumulative) 4.5UG certificate (year 1) 5.0UG diploma (year 2) 5.53-year bachelor’s 6.04-year bachelor’s (hons / research) 6.5–7master’s band — entry level depends on UG duration 8PhD · 320 credits cumulative
30 notional hrs = 1 credit1200 hrs/yr = 40 credits20 / semestercredit only after assessmentdeposits → credit bank → record lockervocational & informal learning creditable (RPL)
NSQF · skilling qualificationspublished
levels 1–8 · outcome-defined, independent of how learning was acquired
QPcarries NSQF level + credit value + national occupation-code alignment NOSone key workplace function each · a QP = a set of NOS for a job role lifecouncil-approved → versioned revisions → deactivated on the register — records cite code + version
Mapping & languageproposed bindings
export & access layers — never the base
expinternational field-of-education mapping attached only on an export profile for cross-border reading langevery human-readable field repeatable across the 22 scheduled languages · script-safe rendering on QR / paper
Code-system registry — proposed · published · pending
Every coded field = system + code + version — a record remains verifiable even after a vocabulary revision, because it names the version it was issued against
Learner ID is the privacy boundary — it exists only inside Auth & the Learner Registry · envelopes carry scoped tokens · offline packs carry no resolvable ID (DPDP)
PROPOSAL v0.1 · green = published national code system, cited as-is · gold dotted = proposed in this standard · click an identifier, envelope row, or code card to trace the links · element-level tables live on the Element Spec view
EdTech Record Elements · PROPOSAL v0.1 · element-level spec per profile · rendered from the embedded data block · blue rows = common spine
ElementCard.TypeBindingNotes / conditional rules
Conditional MUSTs are normative — e.g. scheme.max MUST appear when scale = marks; guardianConsentRef MUST appear for a minor; a CreditRecord without assessmentRef is invalid
Reference chain by design — Assessment → Enrollment · Transcript → Assessments · Credit → Assessment · Certificate → basis records · identity lives in none of them
PROPOSAL v0.1 · all element tables and code lists live in the #et-data JSON block — edit data, not markup · pick a profile above · exported view re-renders from the same data
EdTech Record Examples · PROPOSAL v0.1 · one learner’s Virtual Labs chain across all six profiles · all values illustrative
The chain is walkable — Certificate → Transcript → Assessment → Enrollment, and Credit → Assessment · a verifier can follow every claim to its atomic source
The same scoped token appears in every record of the chain — yet no record, and no chain of records, contains the Learner ID
PROPOSAL v0.1 · flagship: the VLabs experiment completion (ParticipationRecord) — a lab completion verifies exactly like a degree · pick a profile above · instances live in #et-data
EdTech Conformance & Exchange · PROPOSAL v0.1 · validator assertions · rail bindings · settled standard decisions S1–S2
Envelope assertions — apply to every record
Profile assertions
Exchange binding — how each profile rides the rails
ProfileIssue pathConsume pathNote
Settled standard decisions
Certification path — sandbox → profile conformance suites → production · a pass writes the Product Registry entry (same promotion path as the Tech Layout tab)
ERROR = record rejected · WARN = record accepted, flagged for the issuer · every assertion is machine-checkable from the record + registries alone
PROPOSAL v0.1 · assertions and bindings live in #et-data · S1: one shared ED-SEC table · S2: export = derived overlay record, base never modified
Glossary · every term used across the twelve views · filter by group or type to search
All Architecture Standard Code systems Governance
Terms live in the #et-data block · categories: architecture rails & core · the Record Standard · national code systems · governance & privacy