How I Architected Three Games in One Session Without Writing a Line of Code
Constitutional documents, system contracts, and the discipline of leaving questions open. I spent a single working session building the complete architectural foundation for a multi-game ecosystem. Three games. Four system contracts. A shared mechanics layer. A PR merge gate. A
Constitutional documents, system contracts, and the discipline of leaving questions open. I spent a single working session building the complete architectural foundation for a multi-game ecosystem. Three games. Four system contracts. A shared mechanics layer. A PR merge gate. A design decision brief. An asset licensing contract. An ID@Xbox concept submission draft. A portfolio architecture that turns unemployment into documented
One Gravity Well vs. A Universe With Depth
Posted by Loptr Lab / Urban Alien Adventures There's a well-worn model for growing an open-source organization on GitHub. You build one thing. It gets enormous. Everything else you ever create becomes infrastructure for that one thing. freeCodeCamp is the
Posted by Loptr Lab / Urban Alien Adventures There's a well-worn model for growing an open-source organization on GitHub. You build one thing. It gets enormous. Everything else you ever create becomes infrastructure for that one thing. freeCodeCamp is the clearest example alive right now — 456,000 stars on a single repo, with every other repository in their 242-repo org
PIXIE HAS ANOTHER DOOR.
If you've been following Made Sick, Veiled Dominion, or the wider PIXIE ecosystem, you've probably noticed that these projects don't really behave like separate projects. They connect. They overlap.
If you've been following Made Sick, Veiled Dominion, or the wider PIXIE ecosystem, you've probably noticed that these projects don't really behave like separate projects. They connect. They overlap.
Architectural Note: Building an AT Proto-Native OS with Local-First Privacy
Topic: PIXIE OS v5.0.1 Architecture, Spatial AppViews, and Data Hygiene Status: Canonical Design & Implementation Contract The PIXIE ecosystem is shifting from a standard web layout to a spatial, windowed operating environment. Operating at /os (and serving as the narrative
Topic: PIXIE OS v5.0.1 Architecture, Spatial AppViews, and Data Hygiene Status: Canonical Design & Implementation Contract The PIXIE ecosystem is shifting from a standard web layout to a spatial, windowed operating environment. Operating at /os (and serving as the narrative front door at /), PIXIE OS blends a tactical HUD interface with decentralized identity.
LOG // 001 - The Cost of Unbounded Growth
We measured capacity in output until the stewards started breaking. PIXIE doesn't stop the machinery—it just forces us to look at the receipts before we pull the lever.
We measured capacity in output until the stewards started breaking. PIXIE doesn't stop the machinery—it just forces us to look at the receipts before we pull the lever.
Your File System Is an Accessibility Tool — Apple Just Never Told You That
There is a feature built into every Mac that productivity communities quietly celebrate and neurodivergent users swear by. Most people have never touched it. Apple ships it turned on, tucks it into the sidebar, and moves on without explanation.
There is a feature built into every Mac that productivity communities quietly celebrate and neurodivergent users swear by. Most people have never touched it. Apple ships it turned on, tucks it into the sidebar, and moves on without explanation.