Eudaimonia has always called itself an AI operating system. Its kernel has a process table, a scheduler, typed resource pools, and a program loader. Between September 9 and September 15 we closed the gap between "OS-shaped" and an actual OS.
One Namespace: eud://
Every subsystem used to have its own ID scheme. Now one URI grammar addresses all of them: the process table, resource pools, scheduler queues, tool drivers, and locks. A matching /proc endpoint serves the same tree over HTTP.
On top of it sits the eud CLI:
eud ps # programs, state, uptime (ps -a includes exited)
eud top # running requests, pools, preemption waste
eud df # resource pool usage
eud ls/cat # walk and read any eud:// pathPrograms Behave Like Processes
- >Supervision. Program manifests declare restart policies, and a supervisor applies them with backoff, attempt caps, and restart lineage. These are systemd
Restart=semantics. A deliberate exit is never restarted. - >Signals. TERM, KILL, STOP, CONT, and HUP. TERM drains in-flight requests within a timeout and escalates to KILL if the window expires.
- >Exit status. Shell conventions apply: 0 for a clean exit, 70 for a crash, 143 for terminated, 137 for killed. Exited programs stay readable as zombies until they're reaped, which is
waitpid()for agents.
Requests Can Be Stopped
- >Cancellation.
eud cancel <request>stops in-flight work all the way down to the model call. The scheduler now holds a handle to every task it runs. - >Deadlines. A request's deadline is enforced, and expiring is a distinct state from being cancelled.
- >Priority preemption. This half-existed before: a lower-priority request's resources were reclaimed while its work kept running. Now the victim is actually cancelled and requeued. REALTIME work and anything marked non-preemptible, such as a payment or a commit, are never taken.
eud topreports the execution time thrown away, so a future scheduling policy can be tuned against measured waste.
Resource Ceilings That Bind
Manifests have always declared memory and GPU requirements, but nothing read them, so a single program could take an entire pool. Those declarations are now enforced per instance. A program that asks for more than its ceiling is refused with a clear error, while the pool stays free for everyone else.
The Method
Signals, cancellation, preemption, and ceilings were each tested against a live kernel, not just a mock. Measurement also told us what *not* to build: dependency-ordered startup was evaluated on September 15 and deferred, because no program yet depends on another one.
This is the substrate the rest of the stack runs on. Agents are processes, and now they can be named, supervised, signalled, cancelled, preempted, and capped.