userspace.party / userspace

userspace

Where a process meets the operating system.

System calls, process-facing memory and executable loading. Literally userspace.

API docs crates.io GitHub

no_std syscalls Linux x86_64 ELF

Its place in the system

userspace contains mechanisms that only make sense because a process exists above a kernel: system calls, user-visible ABI, process memory and the machinery required to load and start executables.

kernel
  ↑ system-call boundary
userspace
  ├── syscalls
  ├── process memory
  └── ELF loader
       ↓
running program

The boundary

Belongs here

System calls and their ABI
File descriptors and process-facing OS mechanisms
ELF loading and executable startup
Memory semantics needed by userspace execution

Does not belong here

Generic lists, vectors or mathematical abstractions
Kernel-internal mechanisms
Human-interface semantics
Simulation or control of physical systems

Today

Current surface

System-call interfaces such as open/read/seek/mmap/munmap
ELF parsing and PT_LOAD mapping
PIE / ET_DYN and PT_INTERP handling
Process stack and auxiliary-vector preparation
Architecture and operating-system target code

Start here

cargo add userspace

The boundary is deliberate: syscalls live here, never in ample.

From abstraction to reality. userspace.party keeps conceptual borders explicit: abstractions in ample, process mechanisms in userspace, machines in computers, human meaning in humans, browser presentation in webspace, and physical-world simulation and control in twins.