Insights · District offices
When the link drops, the answers keep coming.
Super Intelligence (SI) in a district office cannot depend on the internet. This article describes a server that treats a day without a link as an ordinary day, and a power cut as a planned event.
The sentence we hear
The link drops every afternoon
A district office, a rural branch, an upazila hospital: the documents are the ones head office uses, but the connection is not. The link slows at noon, drops in the afternoon and comes back at night. Power goes two or three times a day. A tool that lives on a server abroad is a tool that works in the morning.
Offline-first turns the order of thinking round. The server that answers sits in the building, on the local network, and needs no internet to run. The internet is used when it is there, for new documents and for support, and nothing stops when it is not. The reference designs for a district hospital, rural bank branches and a district government office are built this way. None is installed yet; they are designs with cited precedents, not delivered projects.
The shape
One server in the building
Staff open a browser on the office network and sign in with the accounts they already have. The server finds the passages they may see, answers in Bangla or English, and shows the circular and the page. The question, the answer and the sources are logged on the server. None of that touches the internet. The server has no inbound or outbound route; its only open door is port 443 on your network.
New documents reach it two ways. Where there is a link at night, head office syncs new circulars when it is up, and the index updates. Where there is no link to speak of, the same bundle arrives on a hardware-encrypted USB drive with a manifest of checksums the server verifies before it installs anything. Software and model updates come the same way, monthly, tested first on a server of ours set to the same versions as yours. Nothing from your office goes out on the drives.
Power
A power cut is a planned event
The server sits behind an online UPS with a network card. A short cut passes unnoticed. If the power stays off, the UPS tells the server to shut down cleanly after a set number of minutes, so the index and the databases are closed properly. When the power returns, the server starts and the services come up in order without anyone touching it. Where a generator exists, the UPS only bridges the seconds until it starts.
The baseline is at least 15 minutes on battery at full load, confirmed at the site survey. A Team server for up to about 50 users is planned behind a 2 kVA UPS; a Department server behind 3 kVA. The sizing arithmetic and the heat figures are in running a language model on one GPU in Dhaka. The point for a district office is simpler: the machine looks after itself, and the morning after a cut it is answering again.
What waits
What works offline and what waits for the link
Everything the staff see works without the link: questions, answers, sources, permissions and the log. Monitoring runs on the server, and alerts go by email inside the office network. Nightly backups go to the office's own backup target, with a weekly copy to offline media.
Four things wait for the link or for the drive: new documents from head office, software and model updates, the monthly report head office wants, and remote support. Remote support is off by default. If you allow it, your IT officer opens a session for a named ticket, it is logged, and it is closed after use. A failed card is the one thing neither the link nor the drive fixes; the supplier's on-site warranty does, and until then the office works the old way.
In short
What works without the link
| Works without the link | Waits for the link or the drive |
|---|---|
| Questions, answers and sources | New circulars from head office |
| Permissions by staff account | Software and model updates |
| The log and nightly backups | Remote support, if you allow it |
| Alerts inside the office network | Reports to head office |
Starting
Start where the link is worst
Prove it where it hurts. A three-week SI proof runs about 200 questions from the district's own circulars and forms, scored by two native Bangla reviewers against a pass mark you approve, on a server of ours in Bangladesh, never on a cloud abroad. The load test tells you whether a Team server will carry the office or whether several offices should share a Department server at the divisional level. The server set-up, six to eight weeks from BDT 14 lakh, includes the UPS design, the offline update routine and training for the person who will own the machine. Government bodies also have the National Data Management Act 2026 to read, which limits how AI tools may be used over data from the national exchange; confirm with counsel.
FAQ
Questions we are asked
Does it ever need the internet?
Not to run. It uses a link when one exists, for new documents and support. A site with no link at all works from the update drives.
Who looks after it in the district?
A named IT officer, trained during the set-up, with written procedures. SI support at BDT 90,000 a month gives that officer a help desk and tested updates; managed SI operations at BDT 1.8 lakh a month has us run it, with a monthly Bangla re-test.
What about a hospital ward at night?
The server answers from SOPs and policies, not patient records, and it is not for diagnosis. A senior nurse or doctor signs off the content before go-live.
Bring the connectivity map
Tell us how often the link drops and how long the power stays off. The design starts from those two numbers.