Currently building · India

I am CRIXX

Builder. Systems thinker. Experimental technologist.
I learn by creating things that don't exist yet.

CRIXX portrait
India Builder in progress

Not what I am.
How I operate.

I'm a student. That's the official status. But the identity is this: I encounter something interesting and I can't stop until I understand it completely — and then rebuild it differently.

That compulsion pulled me into software, automation, and AI. I don't pick a subject and stay in it. I follow the question.

I build systems. I automate things that shouldn't need to be done twice. I experiment with AI not because it's trending but because it's genuinely one of the most interesting problems alive right now.

I'm early in this. Not pretending otherwise. But early isn't the same as unserious.

"The goal isn't to arrive somewhere impressive. The goal is to never stop finding things worth understanding."
0 Projects started
0 Rabbit holes explored
0 Useful failures
∞ Questions remaining
Builder Systems Thinker AI Explorer Automation Problem Solver Python Experimenter Lifelong Learner

Not a resume.
A running log.

● synced
obsession
Three systems, three different problems
ORION searches. SENTINEL watches the machine. PHOENIX controls and repairs it. They stay useful on their own — integrations come later.
experiment
Jarvis, reliability before spectacle
Planner, executor, observer, memory, live capability health — less “AI demo”, more figuring out what a personal system needs to stay useful when parts fail.
setup
One GPU doing more than it should
Plus a phone that moonlights as a camera R&D bench, and a browser with more tabs open than sense.
fact
Malayalam, first language
Which is also why a suspicious chunk of my week goes to tracking Mollywood release dates I definitely didn't need to know that closely.
七転び八起き
nana korobi ya oki — Japanese
"Fall down seven times, stand up eight."
click for another →

Jarvis.

Actively building
Personal AI
Assistant System

Jarvis is not a chatbot demo. It's a long-running personal AI system built around planning, execution, observation, memory, voice, local tools, and real desktop automation. The point is not to make it talk more — it is to make it understand what it can do, act safely, and get better at doing it.

Current version
MARK VII — Active development
Current generation · iteration ongoing

Primary stack
Python · Multi-model AI
Planner + Executor + Observer
jarvis — session active
# Jarvis AI Assistant — CRIXX build # Initializing... ✓ Core systems online ✓ LLM connection established ✓ Automation modules loaded CRIXX@jarvis:~$ Hey Jarvis, what are we building today? > Analyzing active projects... Running task queue... Ready. What do you need? CRIXX@jarvis:~$
🧠
AI Integration
Multi-model reasoning with routing and fallbacks
⚙️
Automation Engine
Desktop actions with outcome verification
📚
Knowledge System
Persistent memory, preferences, and recall
🔄
Iterative Build
Reliability phases, self-model, and capability awareness

Things I'm building.
Things I'm breaking.

ORION
Independent Search / Retrieval
Built · GitHub

A full-stack search engine with a provider-agnostic retrieval layer, normalized results, ranking, deduplication, multiple search verticals, history, API routes, and a lightweight frontend. Built to understand search as a system instead of hiding behind one provider.

APIRanking4 verticalsV2 intelligence
PythonFastAPI RetrievalSearch
SENTINEL
Windows System Intelligence
Active development

A Windows telemetry, diagnostics, anomaly, and system-intelligence platform. It collects machine state, preserves history, exposes an API, and is being hardened around failure isolation, trustworthy signals, and a quiet local dashboard.

TelemetryDiagnosticsHistoryLocal API
PythonWindows DiagnosticsSystems
PHOENIX
Windows System Toolkit
Release hardening

A manifest-driven .NET Windows toolkit for inspecting, configuring, repairing, and maintaining a PC with risk-aware execution, verification, checkpoints, desired-state tracking, and rollback. P1 → P20 is complete; real-machine acceptance testing is now finding the bugs unit tests can't.

23 tweaks8 controls10 tools5 repairs143 tests
C# / .NET 8Windows ManifestsRollback
Ongoing & exploration
Automation Lab Building

A personal collection of tools and scripts I build to automate the tedious parts of my own life. Each one exists because I got annoyed enough to solve it.

why do manually what a system can learn to do once?
Python Automation Personal tooling
AI Experiments Experiment

Hands-on exploration of AI models, prompting strategies, and real applications. Not theoretical. Built, tested, honestly assessed.

less interested in hype. more interested in where it breaks.
AI / LLMs Experimentation Applied
System Teardowns Research

Documented explorations of how things work under the surface. Software, hardware, business logic — anything complex enough to be worth understanding properly.

documentation is the project. understanding is the output.
Research Writing Systems
Side Quest Queue Coming

A backlog of standalone tools with one rule: they must be useful even if none of my other projects existed. Build the product first. Integrate later.

if it only makes sense as a feature, it does not get its own repo.
Standalone Free-first Useful

What's been on
repeat lately.

← scroll →

What I play
when I'm not building.

← scroll →

How I think
about things.

01
Build to understand, not to show.
The project exists to force comprehension. When I build something, I encounter real problems — not imagined ones. Showing it is secondary. Understanding it is the point.
02
Discomfort is information, not a signal to stop.
The moment I want to quit is usually when I'm about to learn the most useful thing. Friction is a pointer, not a wall.
03
Systems thinking over surface thinking.
Any problem worth solving is a symptom of a system. I'd rather understand the system than patch the symptom repeatedly.
04
Honest over impressive.
I'm not interested in performing competence. I'm interested in developing it. One is for an audience. The other is for the work.
05
Failure is data. Collect it intentionally.
Every broken build taught me something a tutorial never would. I stopped seeing failure as evidence against trying and started seeing it as the actual curriculum.

If something here
made you think,
reach out.

I'm interested in conversations about technology, systems, and what people are building. I don't want to network. I want to talk about something real.

CRIXX_ — terminal v0.2
Welcome to CRIXX_ terminal. — You found the easter egg. That tells me something about you. — Type help for available commands.
crixx@terminal ~ $