Model from hardware facts
Extract register maps, side effects, IRQ flows, boot paths, and driver sequences before changing device code.
Official site · Blog · Documentation
Notes and documentation for QEMU agent workflows: provenance, evidence, local checkpoints, and clean final handoffs.
Overview
Use it when you need reproducible research, targeted verification, and a clean handoff.
Extract register maps, side effects, IRQ flows, boot paths, and driver sequences before changing device code.
Plans, logs, probes, traces, and reviews stay under the task artifact root instead of the QEMU source root.
Each slice records targeted build, qtest, boot, debug, or documentation evidence before review.
Blog
How Humanize's loop engineering, workflow graph, and flow primitive ideas shape Oh My QEMU's QEMU modeling workflow.
Docs
Install Oh My QEMU skills, initialize a task workspace, and run the complete modeling workflow from a QEMU checkout.
Read guideHow Oh My QEMU records source provenance, keeps artifacts isolated, and treats final-series signing as human-owned.
Read guide