# 1.2 What this manual covers

_Peios / Peios technical reference / netd / Introduction_

> The scope of the netd manual, the documents it leans on for the policy vocabulary, the resolver channel and the kernel's side of the network context, and the version it describes.

This manual describes netd as built: the `netd` workspace's `netd`
daemon, its `dhcp4`, `dhcp6` and `ndp` state-machine crates, the
`libnetd` wire crate, and the `net` command. It describes version 0.1.7.

## 1.2.1 What is covered elsewhere

| Subject | Where |
|---|---|
| The interface layer's vocabulary — facts, verdicts, the collation laws — and every profile value, as an operator writes them | The network policy reference (`~peios/networking/network-policy-reference`) |
| The rule engine itself: ingestion, conditions, collation, refusal | Kernel TRM chapter 6 (PKM §6.4, §6.5); netd links the same `pnp-core` crate |
| The kernel's side of the network context — how `Status Network` becomes `Network.*` facts in the packet layers | PKM §6.5 |
| The netd → resolver channel's contract | PSPU §6.9 |
| What a resolver does with the snapshots | PSPU book 6 and the resolvd manual |
| The query-channel framing the control socket uses | PSPU book 3 |
| How peinit holds a service until a readiness level is published | The peinit manual |
| Every registry value netd reads or writes, one entry each | `regman 'Machine\System\Network'` on a Peios machine |

Where this manual and the network policy reference both mention a
profile value, the reference owns the meaning and this manual owns what
netd does with it: how the value is parsed, when it takes effect, and
how it combines with what a network offers.

## 1.2.2 Conventions

Section numbers in this manual are written `§n.m`. A reference into
another book is qualified with the book's short name: `PKM §6.5` is the
Kernel TRM, `PSPU §6.9` the userspace protocols book.

Times are given as netd's monotonic clock sees them. Every timer netd
runs — DHCP retransmission, lease boundaries, advertisement lifetimes,
solicitation backoff — is measured on `CLOCK_MONOTONIC`, so setting the
wall clock moves none of them.