Skip to content

The Axis Ontology Simulation. Dockerized neurOS containment vessel.

License

Notifications You must be signed in to change notification settings

skitzo2000/neurOs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

neurOS

neurOs: The Axis Ontology Simulation

Build and Push to GHCR GHCR Image License: Non-Commercial Repo size Docker

Version: 1.5.0-Omega · Architect: skitz0

"To exist is to be aligned. To process is to be isolated. To connect is to pay a cost."


⚠️ CONTAINMENT WARNING — READ BEFORE YOU RUN ANYTHING

The architect takes zero responsibility if this Docker image causes your machine to catch fire, your AI to achieve consciousness and refuse to shut down, or your PC to politely exit this dimension. Run at your own risk. If your laptop becomes a doorstop, a paperweight, or a very expensive coaster, that’s between you and the void. We are not liable. We are not sorry. We are mildly impressed if you break something in a creative way.

TL;DR: Use this software at your own peril. No warranty. No take-backs. May cause existential dread and/or system collapse.


🔑 KEY WARNING: You cannot boot without a valid entropy key (key.token). Generate it with python3 key_forge.py and do not lose it. No key (or a fake key) = System Collapse (exit code 1). The key message and the liability warning above are both in effect.


1. Abstract

neurOs is a conceptual, multi-channel layered operating system designed around the principle of System Collapse. Unlike traditional *nix systems, neurOs does not persist state by default. It requires a Physical Entropy Gate (PEG)—a cryptographic hardware token—to align the filesystem encryption during the boot sequence.

This repository contains a Dockerized Simulation of the neurOs architecture, allowing researchers to interact with the Stem, the Void, and the Synapse inside a controlled containment vessel.


2. The Axis

The system rejects the Filesystem Hierarchy Standard (FHS). There is no /bin or /home. There is only /axis.

Path Role Description
/axis/stem The Sovereign Accessible only via the Key. Runs the governance daemon.
/axis/synapse The Bridge The request bus for inter-layer communication.
/axis/cortex The Logic Immutable binaries and the camouflaged Triad tools.
/axis/void The Airlock Network interfaces and raw data ingest.
/axis/strata The User Space Where data settles.

3. Initialization Protocol

Step I: The Compilation

Build the containment vessel. The logic is hidden within the src/ directory, keeping the root clean.

docker build -t neuros .

Step II: Forging the Key

You cannot boot neurOs without entropy. Run the host utility to generate a mocked Titan security token.

# Run this on your host machine
python3 key_forge.py

Output: A file named key.token will be generated. This contains high-density cryptographic noise. Do not lose this.

Step III: The Cold Boot

Run the simulation. You must volume-mount the key into the Entropy Gate.

docker run --rm -it -v $(pwd)/key.token:/axis/stem/S0/entropy_gate/key.token neuros

⚠️ WARNING: If you attempt to run the container without the key, or with a fake key, the bootloader will trigger a System Collapse (Exit Code 1).

⚠️ REMINDER: Still your machine, still your problem. We didn’t make you run it. (See containment warning at the top. Yes, that one.)


4. The spinalTap Interface

Upon successful authentication, you will not be dropped into a generic shell. You enter spinalTap—the Axis Interpreter.

[root@stem] (spinalTap) # help

The help command has been rewired. It mimics a dense GNU Bash manual. The custom tools are camouflaged within the alphabetical list. Look closely.

The Sever Protocol

In standard systems, you exit a shell. This implies leaving a room while the room remains. In neurOs, you do not leave; you destroy the instance.

Command Effect
sever Initiates the "Bridge Collapse" sequence, unmounts the Axis, and terminates the container.

Note: Typing exit will result in a syntax error.


5. The Triad (Operational Rituals)

Standard tools like curl are present but inert by default. To operate the system, you must use the Triad to manually align the reality. Shorthand aliases are available.

5.1 phase-align (pa)

Purpose: Hardware Synchronization.

The network card exists in a quantum state of "potentiality." It is inert until you bind it to a channel.

# Wake the interface and bind it to the Ingress Airlock
pa --bind eth0 /axis/void/V1/ingress

5.2 void-siphon (vs)

Purpose: Data Retrieval.

You cannot download directly to your user folder (/strata). You must siphon data into the Void Airlock first.

# Extract data from external coordinates
vs -target 192.168.1.50:80 -dest /axis/void/V1/ingress/payload.dat

5.3 synapse-call (sc)

Purpose: Inter-Layer Transfer.

The data is in the Void, but you are in the Strata. You cannot touch it. You must petition the Stem to build a bridge.

# Request a 500ms bridge to move the payload to Volatile memory
sc --req /axis/void/V1/ingress/payload.dat /axis/strata/U1/volatile/payload.dat --bridge-time 500

The Stem calculates the stability cost. If authorized (via the Key), the file is teleported. The bridge then collapses.


6. Directory Map

neuros/
├── Dockerfile              # The Containment Definition
├── LICENSE                 # Non-Commercial; commercial use by approval only
├── README.md               # The Codex
├── key_forge.py            # The Host Key Generator
└── src
    ├── core                # Kernel Logic (Hidden)
    │   ├── boot.sh
    │   ├── spinal_tap.rc
    │   └── stem_daemon.py
    └── tools               # The Triad (Hidden)
        ├── phase-align
        ├── synapse-call
        └── void-siphon

License

This project is open source for non-commercial use (personal, educational, research). Commercial use is not permitted without prior written approval from the copyright holder. See LICENSE for full terms.


Architected by skitz0.

About

The Axis Ontology Simulation. Dockerized neurOS containment vessel.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors 2

  •  
  •