Peios technical reference
Kernel and component TRMs, security specifications, constants and wire formats for implementation and detailed reference.
Topics
Peios Core Specification Anthology (PCSA)
-
Conventions
Conventions for Specifications and TRMs
How the documents of this anthology are written and read — normative language, required structure, citation and addressing, and the style rules for specifications and for technical reference manuals.
-
PCDS
Peios Common Data Structures
The common binary data structures shared across Peios subsystems: the GUID, LUID, and SID identifier types, and the security descriptor family.
-
PGSS
Peios Generic System Standards
The cross-platform standards a system must implement to be Peios — contracts between two roles, either of which a third party may replace.
-
PSPK
Peios System Protocols Kernel
The contracts spoken across the kernel boundary — the protocols a Peios kernel subsystem depends on a userspace process to fulfil, and the formats it exchanges with one.
-
PSPU
Peios System Protocols Userspace
The foundational userspace protocols — public, stable contracts between the components a Peios system is built from, which third parties may implement.
Technical Reference Manuals (TRMs)
-
PKM
Peios Kernel
The Peios kernel as it is built: the KMES event subsystem, the KACS access control system, the stratafs layered filesystem, the LCS registry, and the NTFE packet engine.
-
peinit
peinit
Technical Reference Manual — the init system and service manager: boot, the service model, identity, supervision, jobs and operations, and shutdown.
-
loregd
loregd
Local Registry Daemon — the SQLite-backed RSI source that provides the Machine and Users hives: storage, concurrency, and request handling.
-
eventd
eventd
Technical Reference Manual Proposal — the observability daemon as designed: event, log and metric ingestion, three storage engines, adaptive indexing, and query execution.
-
peipkg
peipkg
Technical Reference Manual — the package manager: repositories and trust, dependency resolution, installation, transactions and rollback, roles and claims, and package production.
-
netd
netd
The network manager as built: how it reads the interface layer and profiles, reconciles links, addresses and routes, runs its DHCPv4, router-discovery and DHCPv6 clients, identifies networks, and publishes readiness and DNS facts.
-
resolvd
resolvd
The stub resolver as built: how resolvd takes its scopes from netd and its fallbacks from the registry, routes, expands, caches and forwards every question, and answers it at the native socket, the 127.0.0.53 stub listener and the NSS shim.