n build phase 1–5n consent flow: request → discover → consent → exchangerecords stay with the issuerdotted = participants, not coreclick 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
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
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
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
issue · discover · verify — all through the rails
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
platforms issue records ↑ · learners approve via LRA
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 railsscoped 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
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
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 IDpublished12-digit lifelong numberLearner Registryconsent-based issuance via school data system · never leaves Auth — downstream sees scoped tokens only (DPDP)
School IDpublished11-digit · SS·DD·BB + 5-digit schoolInstitute Registrygeography-encoded (state·district·block) · permanent for the school’s life · school records: future-provision scope, code cited now
Higher-ed institution IDpublishedU-nnnn · C-nnnnn · S-nnnnnInstitute Registrycategory-prefixed — university / affiliated college / standalone · affiliation lifecycle tracked at source
Skilling qualification codepublishedSSC/Qnnnn · SSC/Nnnnn e.g. ELE/Q4605national qualification register (external source)Q = qualification pack, N = occupational standard · whole-number versions · approval → revision → deactivation lifecycle
Issuer key IDproposedregistry key reference + versionall four registries (D2)keys rotate without re-issuing records · verification always resolves the key via the registry, never trusts the record alone
Record URIproposedrec://{issuer}/{profile}/{uuid}assigned at issuanceglobally 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’s6.04-year bachelor’s (hons / research)6.5–7master’s band — entry level depends on UG duration8PhD · 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 alignmentNOSone key workplace function each · a QP = a set of NOS for a job rolelifecouncil-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 readinglangevery 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
Element
Card.
Type
Binding
Notes / 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