A self-hosted, air-gapped AI workbench application for industrial users to perform secure tasks on local GPU servers without internet access.
Mangalore Refinery and Petrochemicals Limited (MRPL) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Local Backend and Routing
A backend that supports multiple open weight models and routes tasks to the correct model based on requirements.
Agentic Task Engine
An engine that plans multi-step work, executes local tools, and iterates on tasks.
Multimodal and OCR Processor
A component using on-device OCR and vision models to process scanned PDFs, drawings, and images.
Local Knowledge Base Connector
A connector that grounds responses in local manuals, SOPs, and past correspondence.
Deliverable Generator and Sandbox
A system to run code in a sandbox and output real files like Word, Excel, and presentations.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check whether the system operates entirely offline using visible network monitors or logs to prove zero external calls. They will test model auto-selection across different tasks, end-to-end agentic workflows, document processing, and sandbox code execution.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Specific hardware models or GPU VRAM limits available at the venue?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact open-weight models preferred by the organization?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for local backend and routing. How would you build that?
Decoded from SIH26117 itself — A backend that supports multiple open weight models and routes tasks to the correct model based on requirements. The brief asks for it by name.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for agentic task engine. How would you build that?
Decoded from SIH26117 itself — An engine that plans multi-step work, executes local tools, and iterates on tasks. The brief asks for it by name.
The brief asks for multimodal and ocr processor. How would you build that?
Decoded from SIH26117 itself — A component using on-device OCR and vision models to process scanned PDFs, drawings, and images. The brief asks for it by name.
The brief asks for local knowledge base connector. How would you build that?
Decoded from SIH26117 itself — A connector that grounds responses in local manuals, SOPs, and past correspondence. The brief asks for it by name.
The brief asks for deliverable generator and sandbox. How would you build that?
Decoded from SIH26117 itself — A system to run code in a sandbox and output real files like Word, Excel, and presentations. The brief asks for it by name.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will check whether the system operates entirely offline using visible network monitors or logs to prove zero external calls.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will test model auto-selection across different tasks, end-to-end agentic workflows, document processing, and sandbox code execution.
This is the evaluator read for your problem statement, decoded from the brief's own wording.