The nine new emerging branches
2026-27 introduced nine "emerging" branches (codes 43–51): AI & ML, Automation & Robotics, Mechatronics, Communication & Computer Networking, Construction Automation, Cyber Forensics & Information Security, Gaming & Animation, Cloud Computing & Big Data, and Civil & Environmental Engineering.
How to read the confidence labels
Verified — subject, credits and hours taken directly from an official evaluation-scheme or detailed syllabus PDF. Partial — the signature subject(s) for that semester are confirmed, but the full per-semester list was not exhaustively extractable (some scanned IV–VI files resisted extraction).
The full course structure
Every captured subject across all branches: code, theory/practical hours per week, credits, course type, the confidence label and which syllabus version it comes from. Filter by branch, semester or confidence; sort any column; or search within the table.
| Branch | Sem | Code | Course Title | Th | Pr | Cr | Type | Confidence | Version |
|---|
Unit-level topics, labs & textbooks
For the subjects captured in depth, the unit-level topic breakdown, lab/practical outcomes and prescribed textbooks. Pick a branch to expand its subjects.
Every branch, at a glance
Coverage map across all engineering branches: which syllabus version applies, how many semesters and subjects were captured, the capture depth, and the collection status with notes.
| Branch | Version | Capture status | Notes |
|---|
The 70 government polytechnics
Directory of all government polytechnics with district, type, principal/coordinator, website and location. Contact phone numbers are not included. The interactive map with click-to-load profiles is on the Overview tab.
| # | Polytechnic | District | Type | Principal / Coordinator | Website | Pincode |
|---|
Which branches run where
Two views of the same relationship. First, a reverse index — for each branch, every polytechnic that offers it, with a count. Then the per-polytechnic listing of the engineering branches each campus actually runs. Source: Technical Education Department, Uttarakhand.
| # | Polytechnic | Engineering branches running |
|---|
Anomalies worth reporting upstream
Issues found in the source portal — empty branches, duplicate or blank entries — that are worth flagging to UBTER / IRDT. Listed verbatim from the workbook.
| Code | Branch | Issue type | Detail |
|---|
Acronyms & abbreviations
Every acronym and abbreviation that appears across the syllabus, branch names, detailed content and source documents — expanded in plain English. Grouped by kind; use the search box to jump to one.
Where every figure comes from
The portal pages and direct PDF links behind this compilation. Everything traces back to the official UBTER / IRDT Uttarakhand portal.
| Branch / Document | Sem | Syllabus set | Link |
|---|
How this dashboard refreshes — and how it was built
Two halves to this tab. First, the live mechanism — one click triggers the refresh pipeline and you can watch counters update in place. Then, the journey behind it: the phases of conversation between a human stakeholder and an AI build agent that shaped the artifact. For the technology stack itself, see the Tech tab.
The dataset embedded in this page can in principle be refreshed by an automated agent — the same kind of agent that built this site. The button simulates that pipeline end-to-end and applies an illustrative diff to the in-memory data, then re-renders the counters at the top. The network calls are simulated (a static HTML file cannot reach the UBTER portal); the change is in-memory only — reload to restore the baseline.
How this dashboard came to be
Built in an iterative dialogue between a human stakeholder and an AI build agent capable of running tools — file reading, code execution, web search — inside a single conversation. The agent's loop and tool use are below.
The journey · phases at a glance
Each phase moved the artifact forward by one bounded request — it grew incrementally rather than being rebuilt.
The stack underneath
Two layers of technology. What's used today: a small set of mapping, charting, export and typography choices that produced the file you're reading. What it could become: a full open-source agentic pipeline that re-fetches the UBTER data, validates it, regenerates the HTML and deploys — on infrastructure you own, with zero SaaS dependencies and no commercial-LLM API keys leaving your network.
A · Productionising — a FOSS agentic stack
An autonomous, scheduled pipeline of free and open-source software can re-fetch the portal data, validate it, generate the HTML and deploy the site — self-hosted, no SaaS dependencies.
B · The tools used to ship the current artifact
Plots the 70 polytechnics from their lat/long. Loaded from jsDelivr CDN with an SRI hash. OpenStreetMap tiles, no API key.
leafletjs.com ↗Course-type mix, per-semester credits and branch-reach bars on the Overview and Mapping tabs. Loaded from jsDelivr CDN.
chartjs.org ↗Powers the "Excel" download button — rebuilds the full multi-sheet workbook client-side from the embedded data, with phone numbers already masked.
sheetjs.com ↗The whole type system. Serif for headings, sans for body, mono for codes and metadata. Served from Google Fonts.
ibm.com/plex ↗All HTML, CSS and JavaScript live in one document. The only external runtime requests are the three CDN assets and the map tiles. Opens in any modern browser; can be saved offline.
zero-buildUsed at build time to read all 10 sheets of the UBTER workbook and emit the structured JSON embedded in this page — including the phone-number masking step.
openpyxl ↗FOSS pipeline tool catalogue
Each role in a future self-maintaining pipeline has open options — pick what matches your infrastructure.
Visual node-based workflow builder; HTTP, Postgres, cron and Ollama nodes. Single Docker container.
Self-hostExplicit state machines for agentic flows; best fit for the validation + critic stages. Any OpenAI-compatible endpoint.
MITOne-binary local LLM runner — Llama 3.3, Mistral, Qwen, Gemma. OpenAI-compatible API, no keys leave your network.
Local LLMFetch portal pages and pull tables/text from the evaluation-scheme PDFs in stage 4.
ScrapeRegenerated HTML committed and served by a single static web server with automatic HTTPS. No CDN lock-in.
Static