Research diagrams
Home · Architecture · Methods
SVG files render in GitHub Pages; the paired Mermaid sources remain editable text. Solid arrows represent observed packaging or bounded static relationships. Dashed arrows represent an unknown historical/runtime transition. A diagram does not turn a static capability into an observed event.
| Diagram | Subject |
|---|---|
| Installation flow (source) | Apple reference, staging, RAMDisk, brain, ramrod, and firmware paths |
| NVRAM authorization (source) | Name matching, process profile, MAC result, and firmware request boundaries |
| NVRAM request chain (source) | Setter and kernel request boundaries |
| NVRAM driver policy (source) | Driver-level static policy checks |
| EFI path construction (source) | Typed and registry-derived input paths |
| Firmware handoff (source) | Launcher, helper, bless, MultiUpdater, EFI/NVRAM |
| Firmware helper chain (source) | Staging and helper call relationships |
| Restore server request (source) | Restore service request path |
| FDR trust object (source) | Request and trust-object relationships |
| Restore transport and TLS (source) | Configuration and transport boundaries |
| Evidence ladder (source) | Measurement, inference, runtime evidence and unresolved policy |
