┌──────────────────────────────────────────────────────────────────────────────┐
│ │
│ ESHAN ROY │
│ │
│ systems engineer open source builder infrastructure architect│
│ │
│ I work where software meets the operating system. │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ SYSTEMS │ │ AI │ │ INFRA │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │
│ linux • runtimes • developer tooling • agents • automation • security │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
I don't particularly enjoy building another CRUD application.
I enjoy building the thing underneath it.
|
Autonomous software engineering
|
Linux ecosystem engineering
|
Systems & infrastructure
|
M31A is built around one idea:
An AI coding system shouldn't merely generate code. It should own the engineering loop.
┌───────────────────┐
│ USER REQUEST │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ INITIALIZE │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ DISCUSS │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ PLAN │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ EXECUTE │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ VERIFY │
└─────────┬─────────┘
│
▼
┌───────────────────┐
│ SHIP │
└───────────────────┘
terminal-native •
tool-driven •
model-agnostic •
git-aware •
permission-aware
|
Performance × Elegance An Arch-based Linux ecosystem focused on desktop engineering, system tooling, package management and developer utilities.
|
Software products and infrastructure systems built around a simple principle:
|
|
An evolving collection of open-source systems, runtimes, infrastructure, developer tooling, security work and experiments. |
Agents, small language models, inference infrastructure, data pipelines and tooling around the modern AI stack. |
|
Autonomous software-engineering system.
|
Arch-based Linux ecosystem.
|
|
Infrastructure for experimenting with small language models.
|
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 belongs in the architecture
not as a patch 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
┌──────────────────┐
│ ESHANIZED │
└────────┬─────────┘
│
┌─────────────────────┼─────────────────────┐
│ │ │
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ SYSTEMS │ │ AI │ │ INFRA │
└────┬─────┘ └────┬─────┘ └────┬─────┘
│ │ │
┌─────┼─────┐ ┌────┼────┐ ┌─────┼─────┐
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
linux rust go agents slms tools ci runtimes devtools
│ │
└──────────────┐ │
▼ ▼
┌──────────────┐
│ DEVELOPER │
│ WORKFLOW │
└──────────────┘
I believe the best engineering conversations happen in public.
┌──────────────────────┐
│ SYSTEMS │
└──────────┬───────────┘
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
OPERATING RUNTIMES INFRASTRUCTURE
SYSTEMS
│ │ │
└─────────────────┼─────────────────┘
│
▼
DEVELOPER TOOLS
│
┌───────────┼───────────┐
▼ ▼ ▼
AI SECURITY AUTOMATION
│
┌────┼────┐
▼ ▼ ▼
AGENTS SLMs INFERENCE
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"
