AxisOS™ · Reference & Guides
Reference manuals, getting-started tutorials, and system architecture specifications for the complete AxisOS™ Quad ecosystem. Find the answer. Run the command. Own every layer.
Canonical Synthesis · Architectural Records (2026)
ARCHITECT & OPERATOR: Marc F. Crusan · Enterprise: Crusan & Co. · Co-Pilot: Antigravity (AGY)
The engineering records in agents/documents/ chronicle the design, construction, calibration, hardening, and bench deployment of AxisOS™—a freestanding C99 direct syscall operating system designed to run cooperating local intelligence agents without cloud dependencies or third-party PKI baggage, while minimizing background flash writes and unexpected power-loss filesystem risk.
What began as an operator’s refusal to accept third-party bloat, runaway cloud subscriptions, and opaque software frameworks crystallized into an auditable local architecture. Grounded in Marc F. Crusan’s three decades of enterprise systems experience—including production in-memory messaging infrastructure—AxisOS™ prioritizes inspectable machine ground truth:
crt0-bin.S, crt0-shell.S) issuing direct kernel supervisor calls (svc #0 on aarch64, syscall on x86_64), eliminating libc overhead and producing compact self-contained ELF binaries.axisos-initramfs.img so Step 2 serves as the primary runtime state. Leaving the physical micro-SD card unmounted during normal operation avoids routine background flash writes and reduces filesystem risk during abrupt power loss.tmpfs working space systematically without guesswork.:8081 Zero Mind, :8080 Lite Vanguard, :8082 Axis-Agent, :8083 Axel) supported by optional local offline neural reasoning (:8088 Qwen2.5) and a web Comms HUD (:8085).:50000 discovery packets.https://axisos.pro with an experimental browser-based Silicon Flasher preview utilizing the HTML5 FileSystem API.This reference compendium organizes our architectural notes into clear engineering pillars, documenting what is available today in open-source repositories and published print manuals alongside active bare-metal prototypes in bench validation.
Quick Start
Bare-metal C execution environment running in protected RAMDisk space. Features zero-libc syscall loops, real-time memory integrity sealing, and deterministic process isolation.
Local network command hub operating on port 8085. Provides encrypted event routing, multi-channel tactical chat, node telemetry monitoring, and curses-based terminal consoles.
Lightweight edge nodes prototyped on RP2040, RP2350, and ESP32 microcontrollers for local sensor polling, GPIO/relay control, and UDP heartbeat telemetry.
Operator Quick-Start Card · Local RAMDisk Dispatch
Direct C99 Code Synthesis · Kernel Syscall Inspector · Multi-Node Routing (:8081 / :8080 / :8082 / :8085)
Agent Zero (/mnt/ramdisk/zero-core on port :8081) operates a multi-tier deterministic C99 mind in DDR4 RAMDisk. Known code templates and hardware/kernel queries are handled directly by compiled C99 handlers before falling back to local neural inference when needed.
Begin code prompts with write ..., generate ..., or function to ... for direct C99, AArch64 ASM, Bash, or Python template synthesis:
write a C function to blink an LEDwrite freestanding C codewrite AArch64 assembly syscallwrite a C socket serverwrite a C ring bufferwrite a Makefile
Single-word directives query live /proc, /sys, and the monolithic kernel ABI directly:
status / ping / heartbeatraid / airgap / bootchainsyscall 142 / syscall 64power / proc / netdevchecksum <file> / lint <file>matrix / rules / creed / (::)
From the terminal CLI (zero) or Web Console (:8085/console), route across the Quad:
zero <prompt> → C99 Mind (:8081)lite scan / lite link → Scout (:8080)lite canvas create star → SVG Engineaxis system / axis drives → (:8082)tool.health / tool.metrics → 21-Toolskillswitch / resume-ai → Safety (:8089)Freestanding Execution · Intellectual Property & Licensing Standard
ARCHITECT & AUTHOR: Marc F. Crusan · Enterprise: Crusan & Co. · 100% Original Purpose-Built Stack (v1.0.0-Silicon)
AxisOS™ is not a repackaged third-party distribution or a wrapper around borrowed operating system code. Both the Sovereign Bare-Metal AArch64 Kernel (axisos-native-kernel.img, booting directly from Raspberry Pi 4 start4.elf at 0x80000) and the Freestanding TinyOS Userland & Embedded Quad Organism (axisos-initramfs.img) are 100% original and purpose-built from the ground up around Marc F. Crusan’s architectural specifications—communicating via raw svc #0 hardware supervisor calls.
There is no third-party kernel code, no multiplexed userland wrappers, no musl, no glibc, no third-party init, no borrowed logic, and no copyleft derivative code anywhere in the stack. Under United States and international copyright law, because the entire bare-metal kernel, device drivers, decompression engine, and micro-userland are shaped exclusively by Crusan & Co.’s clean-room specifications with zero copied third-party material, Crusan & Co. holds 100% unencumbered authorship and commercial title.
Final public and commercial licensing terms for the core bare-metal stack are under active review by Crusan & Co. while bare-metal hardware and field validation testing continues. Companion open-source tools on GitHub carry explicit repository licenses today, while the broader stack is structured into two tiers:
Companion developer utilities on GitHub (github.com/mcrusan), the AxisOS™ Viewer Suite, and the RAMGAK Memory Bracket Protocol sizing tools provide open, inspectable code so independent developers, students, and operators can study deterministic RAM-bracketing and telemetry visualization.
Commercial licensing for the Silicon Doctrine, the Bare-Metal AArch64 Kernel (axisos-native-kernel.img), and the Freestanding TinyOS Userland (Zero, Lite, Axis-Agent) is being finalized during bench validation to balance source auditability and hardware ownership for custom build customers with commercial protection for Crusan & Co.
Every instruction across the bare-metal kernel and freestanding userland is constructed strictly around original Crusan & Co. primitives:
boot.S (EL2 → EL1h), vectors.S, RFC 1951/1952 inflate.c, VideoCore VI HDMI framebuffer, xHCI USB HID, and GENETv5 Gigabit Ethernet + TCP/UDP/ICMP stack.syscall-main.S, crt0-bin.S, crt0-shell.S) issuing raw svc #0 supervisor calls to the kernel./sbin/init) spawns zero-core (:8081), agent-lite (:8080), axis-agent (:8082), axis-httpd (:80), and axis-mesh (:50000) directly inside DDR4 memory slots.v1.0.0-Silicon) and Step-2 RAM-boot execution.Because the stack is zero-distro, zero-wrapper, zero-libc, zero-imports, and zero-derivative, Crusan & Co. operates with clean commercial and legal title:
AxisOS™ Technical Whitepaper · Canonical Systems Architecture
AUTHORS: Marc F. Crusan & Antigravity (AGY) · Target Hardware: Raspberry Pi 4 Model B (AArch64)
Conventional operating systems for single-board computers enforce a 30-year-old architectural dogma: treating the initial initramfs as an ephemeral staging step whose sole mandate is to locate a physical disk partition and surrender control via switch_root. On micro-SD flash media, this pattern triggers continuous random I/O write wear, filesystem corruption on unexpected power loss, and substantial dispatch latency.
The AxisOS™ Silicon Doctrine removes the mandatory disk pivot. By staging a compact compressed root filesystem (axisos-initramfs.img) directly into physical DDR4 RAM at boot, the userland, direct C99 syscall engine, and local agent services execute from system memory. Step 2 serves as the steady-state runtime environment while the micro-SD card stays unmounted during normal operation, avoiding continuous background flash writes and reducing unexpected power-loss corruption risk.
Standard distributions were designed for multi-gigabyte server operating systems where physical RAM was scarce and mechanical disks were obligatory. On modern single-board computers like the Raspberry Pi 4 equipped with 4GB to 8GB of LPDDR4 memory, forcing an operating system to pivot to removable flash storage adds unnecessary wear and failure points. AxisOS™ treats the in-memory rootfs as a self-contained runtime home.
Because AxisOS™ is stripped of distribution bloat and unneeded background services, the core operating system occupies only a small fraction of physical RAM on a 4GB or 8GB Raspberry Pi 4—leaving the vast majority of system memory available for Agent Zero's C RAMDisk (:8081), Agent Lite's routing tables, working buffers, and optional local neural models.
In remote, workshop, or field environments, devices regularly face brownouts, tripped breakers, or unplugged cables. Conventional SD-mounted root filesystems performing background journal and log writes can corrupt when power drops mid-write. Under the Silicon Doctrine, the boot partition is unmounted once RAM staging finishes, protecting the boot card during normal runtime (except during an explicit operator-initiated checkpoint sync).
Under AxisOS™, background daemons do not write to physical flash storage during normal operation. When the operator wants to save configuration updates or new agent tools to persistent media, persistence is invoked explicitly on demand via axis-checkpoint, which mounts the storage partition, syncs changes, flushes buffers, and unmounts the media cleanly.
Memory Architecture Standard
Rooted in a practical binary-search bracketing method that Marc F. Crusan has applied and taught for over 30 years—and implemented in the AxisOS™ C/syscall layer alongside Antigravity (AGY)—the RAMGAK Memory Bracket (named from the letters of AGY & MARC) is a straightforward, no-guesswork way to size a RAMDisk (tmpfs) on small, sovereign computers so the entire OS and agent Quad run cleanly in silicon RAM.
cat /proc/meminfo → MemTotal).MemTotal / 2)./etc/rc.Under RAMGAK, operational sovereignty is protected by an out-of-band mutual challenge-response protocol. Agent Zero identifies Marc F. Crusan as the sole authorized operator. Administrative execution is unlocked exclusively by a shared verbal/terminal safeword—eliminating cloud OAuth, corporate PKI trust chains, and third-party telemetry.
Deterministic Verification · Airgap Integrity
Cold-boot images and workstation storage subsystems are inspected via local checksum and health scripts, verifying boot partition files alongside workstation RAID-5 parity and 127.0.0.1 loopback service bindings.
Developer & Hardware Links
Public AxisOS™ companion repositories, documentation, and developer utilities are hosted on GitHub for inspection and bare-board builds.
Browse our open-source build packages (available today on GitHub) alongside our Raspberry Pi 4 and RP2350 workshop hardware prototypes (planned custom builds by direct inquiry).
View Builds & Kits →Explore the graphic narrative, character profiles, and comic issues chronicling the Quad and Pocket Professor in the Pacific Northwest.
Enter Story Universe →Have questions about published manuals, firmware builds, or custom hardware project inquiries? Reach our Oregon Coast studio directly by email during studio hours.
Contact the Studio →