Outer Void is built with a clear ethical foundation.
"Currently Under Full System Integration - Stage 06 of 44."
Independent Software Products · Developer Tooling · AI Systems · Android Engineering · Experimental Systems
Outer Void is an independent software organization founded by Christopher Osburn for building practical software products, developer infrastructure, intelligent systems, and experimental technology that doesn't always fit neatly inside conventional development boxes.
All active Outer Void projects now live under the Outer-Void organization, providing a single home for the products, tools, engines, research, and infrastructure being developed across the ecosystem.
The work ranges from production-oriented applications and Android systems to developer tooling, automation, SaaS products, structured AI research, and experimental engineering.
The common principle is simple:
Build systems that reduce chaos, increase clarity, and solve real problems.
A custom Android launcher built in Kotlin and designed as a polished standalone product rather than simply another Android home screen.
AXIOM combines configurable home surfaces, widgets, application management, system controls, media integration, customization, and its own native supporting projects.
The AXIOM ecosystem includes:
- VOID.SYS — AXIOM's native icon infrastructure and standalone project.
- AXIOM Shooter — a standalone native project that also exists inside AXIOM Launcher as a hidden home-screen Easter egg.
AXIOM Launcher, VOID.SYS, and AXIOM Shooter remain independent proprietary Outer Void projects.
Kotlin · Android · Jetpack Compose
Mobile-first SaaS designed specifically for solo contractors and tradespeople.
Roughin brings clients, jobs, line items, estimates, invoices, photos, payment links, subscriptions, and field-oriented business workflows into one system.
The project is designed around the realities of actually doing the work—not forcing tradespeople into software built primarily for office environments.
FastAPI · PostgreSQL · SQLAlchemy · React · Vite · Tailwind · Stripe · Cloudflare R2 · Docker
Private caregiving and accountability infrastructure designed around continuity rather than simple reminders.
Vigyl is being developed around private care groups, assigned responsibilities, task completion, accountability, communication, and structured follow-through.
The objective is not merely to remind someone that something needs to happen, but to help ensure responsibility survives the gap between intention and completion.
FastAPI · SQLAlchemy · Pydantic · SQLite
Android-to-Android developer and device-service infrastructure designed to turn an Android device into a capable mobile development, diagnostic, recovery, and service workstation.
The project is being developed around workflows including device communication, ADB, Fastboot/Fastbootd, recovery, sideload, terminal operations, Logcat, files and packages, backup and recovery, flashing workflows, and advanced Android tooling.
VoidForge is designed to remain fully functional as a standalone application while also participating in the broader BLUX and Outer Void ecosystem.
VoidForge is currently free and restricted to authorized Outer-Void organization members.
Android · Kotlin · ADB · Fastboot · Termux · Linux
TheResolverBot is a private Telegram moderation and administration platform built around deterministic enforcement, explicit authorization boundaries, administrative tooling, diagnostics, moderation records, subscription infrastructure, automated testing, deployment tooling, and intelligent administrative capabilities.
The project remains actively maintained within Outer-Void but is no longer a public repository.
Python · Telegram · SQLite · AI Integration · Linux
BLUX is the intelligence and integration platform being developed within Outer Void.
What began as a collection of structured AI experiments is evolving into a larger architecture for combining artificial intelligence, deterministic reasoning, construction engines, developer tooling, autonomous workflows, execution evidence, and independently useful software systems.
BLUX is being designed around a simple idea:
Intelligence should enhance a system without requiring the system to surrender control of itself.
The architecture is being developed around independent engines and applications connected through explicit contracts rather than one massive application containing everything.
Areas under active development and research include:
- AI model abstraction and routing
- Structured reasoning
- Deterministic construction
- Tool and capability discovery
- Agent execution
- Developer automation
- Execution receipts and provenance
- Dataset engineering
- Evaluation infrastructure
- AI-assisted software development
- Local and remote model integration
- Android and device integration
BLUX is an important part of Outer Void.
It is not the entirety of Outer Void.
The emerging Outer Void architecture intentionally separates direct intelligence from ecosystem control.
"blux"
The direct interface to BLUX intelligence.
Designed for conversational, piped, scripted, and model-assisted workflows without requiring the user to operate the entire Outer Void ecosystem.
"ax"
The AXIOM command-line control plane.
Designed to provide a unified interface across compatible Outer Void tools, engines, development environments, project systems, and device capabilities.
In simple terms:
"blux" is intelligence. "ax" is orchestration.
Individual Outer Void tools retain their own native interfaces rather than becoming permanently dependent on either one.
The broader BLUX architecture is being developed from a number of independently useful projects and research systems.
Structured reasoning and analysis engine.
Structured construction, transformation, and repair engine.
Repository, artifact, quality, security, and release-analysis tooling.
Deterministic repository construction, scaffolding, and project-generation tooling.
Tool, command, project, and capability discovery infrastructure.
Execution evidence, receipts, provenance, operation relationships, and reproducibility infrastructure.
Dedicated datasets and evaluation infrastructure for CogA, cA, and future BLUX-native intelligence.
These systems are being developed toward interoperability while retaining clear boundaries and independent responsibilities.
Outer Void includes a growing collection of developer infrastructure built around mobile development, Linux, Android, Termux, command-line workflows, repository engineering, automation, and developer productivity.
Projects include infrastructure such as:
- AXIOM / "ax"
- DAT
- LRC
- GOD
- BLUX tooling
- Termux Background
- blux10k
- jadis.toolbox
- Android development infrastructure
- repository and release tooling
"jadis.toolbox", now maintained under Outer-Void, is also scheduled for a broader architectural and tooling overhaul as the ecosystem standards mature.
The goal remains straightforward:
Remove unnecessary friction between an idea and a working system.
Outer Void does not treat integration as an excuse to create unnecessary dependencies.
Where a project is intended to stand on its own, it should remain useful without BLUX.
That includes products and tools such as:
- AXIOM Launcher
- Roughin
- Vigyl
- VoidForge
- DAT
- LRC
- GOD
- jadis.toolbox
BLUX integration can provide additional intelligence, automation, reasoning, or orchestration where it creates genuine value.
It should not become a requirement simply because BLUX exists.
VOID.SYS and AXIOM Shooter remain deliberately independent of BLUX intelligence.
AI-Assisted Development
Artificial Intelligence Systems
Python
Android / Kotlin
Backend Systems
REST APIs
Automation
Developer Tooling
SaaS
Rapid Prototyping
System Architecture
Linux / Termux
CI/CD
Dataset Engineering
AI Evaluation
Mobile Systems Engineering
AI-assisted development changes how quickly software can be researched, designed, implemented, tested, and iterated.
It does not eliminate engineering responsibility.
Outer Void uses AI as an accelerator across research, architecture, implementation, debugging, documentation, testing, auditing, and experimentation while retaining human responsibility over system design and final technical decisions.
Generated code still has to integrate.
Architecture still has to hold together.
Security boundaries still have to work.
Tests still have to mean something.
Products still have to function outside the development environment.
AI-generated confidence is not evidence that a system works.
The objective isn't to generate the most code.
The objective is to build systems that work.
Outer Void wasn't founded from a traditional computer science career path.
Its founder spent years working in construction, fabrication, renovation, manufacturing, and other hands-on environments before moving into software development.
That background created a different approach to engineering:
Figure out what needs to exist.
Understand how the pieces interact.
Build it.
Test it.
Find what doesn't work.
Fix it.
Keep moving.
The medium changed.
The builder mentality didn't.
Outer Void serves as the home for the active software projects, products, tools, experiments, and engineering infrastructure developed across the ecosystem.
Projects that once existed under personal development namespaces have been consolidated under the Outer-Void organization so their ownership and relationship to the broader system are explicit.
Some repositories are public.
Some are proprietary.
Some are private research or internal infrastructure.
Some are intentionally restricted.
They do not all have the same distribution model—and they aren't supposed to.
Christopher Osburn - (JADIS)
Self-taught software developer, product builder, systems architect, and hands-on builder.
Currently open to:
Remote Employment · Contract Development · Project Work · Rapid Prototyping · Automation · AI-Assisted Development · Collaborative Product Development
Personal GitHub: "@Justadudeinspace" Organization: "@Outer-Void"
Outer Void
Build the system. Test the system. Understand the system. Improve the system.
