Jack-In Guide
Ready to see how deep the rabbit hole goes? Follow this guide to activate your first Nerve Protocol mission. No leather trench coat required—just your keys, your stack, and a willingness to disappear from the open web.
1. Prime Your Access Keys
Generate hardware-backed keys (YubiKey, Ledger, or TEE-supported TPM).
Register the public portion inside the Nerve onboarding capsule.
Store recovery shrouds offline—paper wallets belong to another matrix.
2. Install the Nerve Console
Download the console launcher for your platform.
Verify the binary with the published attestation hash.
Launch the installer; it creates a local enclave container with no root access required.
Run
nerve jackinto validate the enclave against the attestation service.
3. Enter the Network
On first launch you’ll receive a Jack-In Phrase—a one-time phrase you speak to the Guardian Model.
The Guardian scores your voiceprint against your registered biometric, then hands you the operator deck.
Optional: enable “ghost mode” to mask your presence from collaborators until you invite them.
4. Wire Your Stack
Follow the Integration Matrix for detailed steps. Quick hits:
Uber & Amazon: OAuth via encrypted browser-in-the-enclave. No tokens touch the public browser.
Slack & Notion: Install the Nerve app; scopes default to read-only until you escalate.
Google Workspace: Use domain-wide delegation with restricted service accounts and attested access.
5. Launch Your First Mission
Open the Mission Deck.
Hit
CTRL + REDPILLto open the command palette.Enter an intent like:
“Prep the investor update, schedule a call with the board, and keep all docs locked inside the enclave.”
The console compiles the intent, shows the mission graph, and asks for final approval.
Approve, then watch the Executor Bay light up as agents move through steps.
6. Review & Share
Inspect the Signal Lattice for compiled insights and recommended actions.
Generate a zero-knowledge receipt to prove completion without revealing content.
Share a redacted summary with stakeholders via encrypted channels.
7. Jack Out Cleanly
Hit
JACKOUTor close the console; the enclave wipes itself.Optionally export an encrypted mission template for future runs.
Log your reflections in the Operator Journal—because you’ll forget once you’re back in the matrix.
Troubleshooting
Attestation Failure: Check hardware firmware and ensure the attestation service is reachable through your secure relay.
Integration Timeout: Reconfirm scopes and policy bindings in the Integration Grid.
Agent Stalls: Guardian Models may have throttled an agent. Review the Guardian dashboard for insight.
Want to unleash autonomous executors? Head to the Executor Tactics doc for advanced configuration.
Last updated
