Quiz · Hands
A short knowledge check. Answers are hidden behind callouts so you can self-grade after answering.
1. What distinguishes Mind from Hands?
The Mind determines should I do this?; the Hands determine how do I do this?.
2. Why are Hands provider-neutral (capability-based)?
So the Pico depends on capabilities like email.send rather than a provider’s tool names like GMAIL_SEND_EMAIL. The provider can then be swapped without changing Pico behaviour or rules.
3. What is the fundamental security rule for Hands?
No Hand acts without identity and authorization context. A valid credential does not imply authorization.
4. How are Hands different from MCP?
Hands are the Pico capability abstraction; MCP is an integration mechanism through which tools may be discovered or executed; Composio is a provider/platform. These concerns remain separate.
5. Name the seven concerns of a Hand invocation and who owns each.
- Composer equipment — Composer.
- Pico decision — the Pico Mind.
- Policy authorization — Open Engineering rules.
- Hand selection — the Pico runtime.
- Provider execution — the provider (local, Kubernetes, Composio, …).
- Evidence — Pico memory.
- Action event — the Pico Voice.
6. Why are evidence and the action event kept as separate artefacts?
Evidence is a retainable, verifiable record of what actually happened, stored by the Pico so it can be audited or reasoned about later. The action event is a broadcast on the Pico’s Voice so other participants can subscribe and react. One serves memory and accountability; the other serves distributed communication. Collapsing them removes either auditability or reach.
7. In this wave, is Composio a runnable dependency of the lesson?
No. Composio (and every other external SaaS provider) is illustrative only in this wave. No exercise, lab step, or verification command contacts an external service, and no credentials are required. Every runnable check operates on local YAML using provider-neutral capabilities.
Next
Return to the Part 3 overview or the course home.