Auditable architecture · Unit 2 of 13
X-ray of the runtime
The real boot starts with a gate: the kernel reflects the manifests and resolves the whole graph through milpa/resolver BEFORE any plugin boots. A blocked graph throws ArchitectureBlockedException with the full ResolutionReport on board — every learnable error, every conflict, every miss — not just a one-line message.
By the end, you'll be able to
- Reconstruct the boot sequence
- Identify the derived registries
Understand
The real boot starts with a gate: the kernel reflects the manifests and resolves the whole graph through milpa/resolver BEFORE any plugin boots. A blocked graph throws ArchitectureBlockedException with the full ResolutionReport on board — every learnable error, every conflict, every miss — not just a one-line message.
A bootable graph boots in the order the report itself carries: loadOrder[]. The same resolution that gated the graph also ordered it, so the boot order is not a separate list that could diverge; the registries and routes are derived afterwards, from a set that has already proven to close.
See
Open the boot gate
Walk the resolver's four scenarios: each renders the real ResolutionReport — the gate, the learnable error and the loadOrder[] boot.
Do
Run the practice in your checkout and keep the output as evidence.
Verify
Show that you can apply the unit. Progress only advances once you pass the assessment.
Criteria assessed
- Tell apart the information available before and after resolving the graph.
- Relate doctor and inspect as complementary views.
Primary sources
Content verified: 2026-07-12