Membership lesson · Build Your Jarvis · Module 9 — The plug socket (MCP)

The door policy — pinned labels and second guests

The headline trust lesson of the module — the door policy stops being a ritual and becomes machinery. Pinned labels: every approved tool description gets cached at first connect, compared on every reconnect, and a changed label suspends the tool until the member has read old against new and said yes again — because the rug pull is the attack that defeats one-time vetting, and trust should attach to words you read, not to a name that can quietly change what it means. Keys move into config: a server that needs an API key gets it from the app's gitignored config, pasted by the member's hand, never typed into chat and never readable by the model. Per-tool switches arrive so a server's useful tool can stay while its nosy sibling doesn't. Then the whole policy performed for real: the member's second guest — the candidate from their own 9.1 wishlist — vetted question by question on the record, plugged in, pinned, and put to work through the cards.

This lesson ships with the paid path. Checkout isn't live yet — start with the free projects (Ground Zero + Off the Grid), or join the waitlist.