Repository navigation
Native Qualification Components And Trust Boundaries
sergio velderrain edited this page Nov 12, 2026
·
1 revision
| Component | Placement | Authority and boundary |
|---|---|---|
Run planner and LiveRunBroker
|
Trusted host | Creates one expiring host-bound permit for one VM, then seals exact server/tool/argument candidates and one teardown target; model output never creates authority. |
| Artifact cache and NSIS installer | Trusted host, then Windows user profile | Host verifies vendor signatures/digests and the pinned extension; a per-run transient read-only share supplies files to a per-user installer with persistent step logs and nonzero failure propagation. |
| Desktop capture and synthetic UI | Windows guest interactive session | Actor owns capture start/stop and private Global Storage; the independent synthetic view shows only the current seeded task, reading, limit, and two targets. No LabVIEW/VIPM action occurs. |
| Actor MCP stdio server and relay | Windows guest | The relay launches only the pinned Actor entry point, binds reads to its capture root, and permits a closed MCP method set; it is reachable from the host only through a verified loopback NAT mapping. |
| Evidence consumer, scheduler, and action router | Trusted host | Validates the exact Actor contract, VM/capture/frame identity, hashes, ordering, lifecycle, budgets, and active state before one exact broker-granted synthetic action. |
| Local Ollama | Trusted host loopback | Uses only the approved local model digest and CPU-only settings; no remote fallback, tool authority, filesystem access, or retained raw response text. |
| Independent oracle and receipt writer | Test controller | Scores visible-state grounding, selected action, task acceptance, and timing separately; writes only a redacted mode-0600 result and hashes. |