[02 · ENGINEERING PRINCIPLES · 03/12]

What KERN Runs On

1
Bare metal, no exceptions
Every production instance runs directly on raw hardware. Zero hypervisors, zero abstraction overhead between your code and the CPU.
2
One binary per host
Statically linked, scp to target, run. No dependency trees to resolve, no version conflicts — a single file is the deploy artifact.
3
Pipes over message queues
Data flows through Unix pipes, not message brokers with nine-nines SLA theater. Your grep skills are the observability platform.
4
stdout is the log
Every service writes to standard output. No structured logging frameworks, no log aggregator overhead — just streams you can pipe and replay.
This is the Unix Terminal Mono design system, applied by Curio Design — a design-style library for AI agents. Full Unix Terminal Mono guide → designbycurio.com/learn/terminal-monospace-unix-1980