diff --git a/CONTEXT.md b/CONTEXT.md
index cd2891ac..ade4c03e 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -38,7 +38,9 @@ Hypervisor-delivered notifications of guest activity (breakpoints, control-regis
 - Both methods provide **VM state access**; only the **VBoxVMI method** is planned to provide **VMI events**
 - Pausing through either method is the ordinary VirtualBox pause, visible to (and undoable by) the VM's user
 - A **VBoxVMI** client that disconnects leaves no trace: intercepts are removed and anything it paused is resumed
+- When the caller selects no **Access method**, the VirtualBox **Driver** uses the **VBoxVMI method** if the VM serves a VBoxVMI socket, and the **MachineDebugger method** only if it does not; an explicitly selected method never falls back
 
 ## Flagged ambiguities
 
 - "VirtualBox driver" was used for both the libmicrovmi Driver and the patched hypervisor — resolved: **Driver** is always the libmicrovmi side; the hypervisor side is "patched VirtualBox".
+- "Mode" in LibVMI (Xen, KVM, VirtualBox, ...) names the hypervisor being monitored — resolved: a **LibVMI mode** corresponds to a libmicrovmi **Driver**, never to an **Access method**; VBoxVMI and MachineDebugger are two access methods of one LibVMI mode.