┌─────────────────────────────────────────────────────────────────────────┐
│ $ whoami │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ Eshan Roy │
│ Systems Engineer · Builder · Infrastructure Architect │
│ │
│ operating systems developer tooling ai infrastructure │
│ distributed systems automation security │
│ │
└─────────────────────────────────────────────────────────────────────────┘
I don't particularly enjoy building another CRUD application.
I enjoy building the thing underneath it.
SYSTEM |
STATUS |
FOCUS |
|---|---|---|
| ⚡ M31A | ACTIVE |
Autonomous software engineering |
| 🐧 Snigdha OS | ACTIVE |
Linux ecosystem & desktop engineering |
| 🏗️ TIVerse | BUILDING |
Open-source systems & infrastructure |
| 🧠 AI Systems | EXPERIMENTAL |
Agents · SLMs · inference infrastructure |
┌───────────────────────┐
│ ESHANIZED │
└───────────┬───────────┘
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│ SYSTEMS │ │ AI │ │ INFRA │
└─────┬─────┘ └─────┬─────┘ └─────┬─────┘
│ │ │
┌─────┼─────┐ ┌─────┼─────┐ ┌─────┼─────┐
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
linux rust go agents slms tools ci runtimes devtools
M31A is built around a simple idea:
An AI coding system shouldn't merely generate code. It should own the engineering loop.
┌──────────────┐
│ INITIALIZE │
└──────┬───────┘
↓
┌──────────────┐
│ DISCUSS │
└──────┬───────┘
↓
┌──────────────┐
│ PLAN │
└──────┬───────┘
↓
┌──────────────┐
│ EXECUTE │
└──────┬───────┘
↓
┌──────────────┐
│ VERIFY │
└──────┬───────┘
↓
┌──────────────┐
│ SHIP │
└──────────────┘
Designed around
terminal-native · tool-driven · model-agnostic · git-aware · permission-aware
Performance × Elegance
An Arch-based Linux ecosystem focused on a cohesive desktop experience, system tooling, package management and developer utilities.
Linux · Arch · Rust · Shell · Desktop
Software products and infrastructure systems built around one principle:
make infrastructure boring, reliable and powerful.
An evolving collection of open-source systems, infrastructure, developer tooling, security work and experiments.
|
Autonomous software-engineering system.
|
Arch-based Linux ecosystem.
|
|
Small-language-model experimentation infrastructure.
|
Developer tooling around the Model Context Protocol ecosystem.
|
|
Desktop engineering and system tooling.
|
Security, runtimes, dependency analysis, automation and infrastructure experiments.
|
01 architecture before implementation
02 measure before optimizing
03 explicit failure beats mysterious failure
04 security is part of the architecture
not a patch applied afterwards
05 dependencies should earn their place
06 a system should remain understandable
after its author leaves the room
07 if it can be automated, automate it
08 if it cannot be observed, it cannot be trusted
09 if it cannot be recovered, it isn't finished
I believe the best engineering conversations happen in public.
┌──────────────┐
│ SYSTEMS │
└──────┬───────┘
│
┌──────────────────┼──────────────────┐
│ │ │
▼ ▼ ▼
OPERATING RUNTIMES INFRASTRUCTURE
SYSTEMS
│ │ │
└──────────────────┼──────────────────┘
▼
DEVELOPER TOOLS
│
┌─────────────┼─────────────┐
▼ ▼ ▼
AI SECURITY AUTOMATION
│
┌──────┼──────┐
▼ ▼ ▼
AGENTS SLMs INFERENCE
I build, maintain and experiment across the layers beneath ordinary software.
Fork it. Break it. Improve it. Send the patch back.
$ neofetch eshanized
OS → Linux
WM → i3
Languages → Rust · Go · Python · TypeScript · C · Bash
Focus → systems · infrastructure · AI
Mode → building
Status → online
$ echo $PHILOSOPHY
"make complex systems feel inevitable"
