I am a Civil Engineer working in public water infrastructure in Assam, India.

My professional work involves pressurised water-supply systems, 24×7 drink-from-tap projects, hydraulic modelling, DPR review, GIS, field data, IoT, and SCADA. Alongside engineering, I build practical software and automation systems for organising technical information, improving workflows, and connecting engineering data with maps, models, documents, and AI.

My focus: converting fragmented engineering data and repetitive processes into connected, reusable, and auditable digital systems.

Some systems are currently local or private while documentation and public-release structures are being prepared.

View my public repositories →

These are tools and platforms I have used in engineering work, personal projects, local development, or active repositories.

I prefer systems that are:

• open source rather than dependent on closed, non-portable platforms
• local first where privacy, technical documents, or official data are involved
• Dockerised for reproducible setup, migration, backup, and deployment
• modular so established tools can be integrated instead of unnecessarily recreated
• human readable through Markdown, documented schemas, and transparent configurations
• automation friendly so repetitive work can be delegated to scripts and agents
• auditable with provenance, version control, validation, and non-destructive workflows

PostgreSQL / PostGIS  →  Structured source of truth
Qdrant                →  Semantic retrieval and memory
Markdown repositories →  Human-readable knowledge
Ollama / local LLMs   →  Private AI processing
AI agents             →  Workflow orchestration
Docker Compose        →  Reproducible services
Maps and dashboards   →  Engineering decisions

These are areas I am actively studying, prototyping, or planning around. They are not presented as claims of mastery.

• Agentic AI and low-intervention development workflows
• Retrieval-augmented generation and engineering document intelligence
• Local language models, private AI, and self-hosted AI services
• Docker-based home servers and self-hosted applications
• Open-source GIS, web maps, spatial databases, and field-data systems
• Hydrology, hydraulic modelling, flood modelling, and engineering digital twins
• IoT and SCADA automation for public water utilities
• Climate resilience, water security, and source sustainability
• Android utilities for engineers and field teams
• Structured repositories, model registries, provenance, and knowledge graphs
• Workflow automation across documents, email, field records, and project data
• Code-first animation, technical visualisation, Blender, and 3D workflows
• Open-source creative and publishing pipelines

flowchart LR
    A[Field Data] --> D[Engineering Data Platform]
    B[Documents and Standards] --> D
    C[Models and GIS] --> D
    D --> E[Search and RAG]
    D --> F[Maps and Dashboards]
    D --> G[Automation Agents]
    E --> H[Better Technical Decisions]
    F --> H
    G --> H

The long-term goal is not a collection of disconnected applications. It is an interoperable ecosystem where engineering data, documents, models, maps, and automation can work together.

I write and build around:

• practical engineering automation
• water, GIS, and digital infrastructure
• open-source and self-hosted software
• AI-assisted development and RAG systems
• technical tutorials and reusable scripts
• The Krittika Odyssey — technology, learning, family, creativity, and building for the future

Technical Blogging · Photography · 3D and Blender · Code-driven Animation · Sci-fi · Strategy Games · Software and Gadgets

I am interested in practical collaboration involving:

• water and environmental engineering
• engineering digital twins
• open-source GIS and hydrology
• public-utility digital systems
• local-first AI and automation
• field applications for infrastructure teams
• reproducible Docker-based engineering platforms