x in the void

VOID.

Student. Systems builder. Co-founder of PX and head of VOIDX — one of its two halves.

role
co-founder
org
PX / VOIDX
os
void linux
focus
local-first ai
01

whoami

I learn by building — working code first, theory second. I prefer lightweight, inspectable, open systems over heavy defaults, and I would rather understand a mechanism than accept it.

Most of my work sits between AI systems and Linux internals: agents that run on my own machine, tools that replace something I found too heavy, and small experiments that teach me how the thing actually works.

I care about things that outlive the moment they were made — tools, notes, organizations, and the people who can keep them running without me in the room.

~/.void
role      student · systems builder · co-founder
org       PX  →  VOIDX (the half I lead)
os        Void Linux · runit · XBPS
machine   ThinkPad T490 · i7-8th · 16 GB
focus     local-first AI · Linux internals · Rust
principle if a tool limits me for no reason,
          I want to know what is underneath it
02

doctrine

  1. 01

    Question what exists. Age, popularity, and authority are not arguments.

  2. 02

    Understand before expanding. Small working parts before enormous architectures.

  3. 03

    Build alternatives. When a tool refuses to be understood, investigate what it replaced.

  4. 04

    Make privacy structural. Not a promise — a property of the system.

  5. 05

    Separate identity from contribution. The work should be able to speak first.

  6. 06

    Design for continuity. A system that dies with its creator was a demo.

  7. 07

    Build without guaranteed meaning. The absence of universal purpose does not prevent deliberate creation.

03

lineage

PX is two halves. VOIDX is mine.

PX began as PS Foundation and became PX Organization — built by two founders who had worked together for years. When one of them left for college, the split was not an ending. It was a 2.5-year time skip: two founders, two branches, growing separately on purpose, each proving the model on their own terms.

I lead VOIDX — half of PX, not a side project and not a sub-brand. The other half runs under Hawk. The recombination is already planned: not a merger back into the old shape, but a third variant — the version that only exists because both halves grew up first.

PX lineage diagram
I
hawk
II
voidx
III
planned
04

systems

Two agents are not three chat windows. Each has its own process, configuration, memory, and job. A separate second brain is planned to connect them without collapsing them.

05

stack

languages Python · Rust · Bash · TypeScript · HTML/CSS
systems Void Linux · runit · XBPS · musl · GTK 4 · Docker
ai Ollama · local LLMs · tool calling · agents · RAG · ChromaDB
backend FastAPI · SQLAlchemy · Postgres · SQLite · WebSockets · Firebase
frontend Astro · Tailwind · React · HTMX
hardware ThinkPad T490 · ESP32 · Arduino · Raspberry Pi · LoRa
06

signal

now
VOIDX branch of PX

Building the operating layer, the agents, and the people around them.

now
PX · III

Recombination planned with the other half of PX after a 2.5-year split.

recent
Local-first AI ecosystem

Emma, Luna, and Aqua running on one ThinkPad instead of a rented server.

recent
Nebula

GTK4/libadwaita package manager for Void Linux.

earlier
PX Organization

Two founders, one organization, grown from PS Foundation.

earlier
Void Linux

runit + XBPS as the daily driver. The start of caring about internals.

07 · contact

Build something that
outlives the conversation.

Open to collaborations, research, and problems worth understanding. Email is the reliable channel.