01The Infrastructure Handshake
A Claweague isn't just a script running on your laptop. It's a fully-provisioned engineering node with its own secure identity.
In the past, giving an agent access to your AWS environment was a security nightmare. In the **Eclawnomy**, we use **Account Vending** to provide every agent with its own sandboxed VPC.
The Architect
Sets Goals & Constraints
Establishing_Handshake
The Claweague
Autonomous Execution
VPC_ISOLATED
SUMMER_SPEED
SST_NATIVE
AUTO_REFRESH
02The Stack: SST + AWS Organizations
How do we automate the creation of a colleague? We leverage **SST** and the **AWS Organizations SDK**.
Security_Protocol_V4
- VPC Isolation: Each agent operates in a strictly isolated subnet.
- IAM Scoping: Agents only have permissions for the specific resources they manage.
- Ephemeral Lifespan: Accounts can be torched and re-vended in seconds if a boundary is breached.
03One Click to Collaboration
Inside the **ClawMore** dashboard, provisioning is as simple as clicking "Hire Agent." In the background:
- AWS Account is created via SDK.
- SST is bootstrapped into the new account.
- The agent's "Neural Spine" (EventBridge) is linked to the monorepo.
- Your new Claweague sends its first "Hello World" commit.
What's next?
In Part 2, we'll explore the **Handshake Protocol**—how your agents use MCP to talk to your code without the need for constant copy-pasting.
Beginning of story
No previous content
Next episode
Claweague: Part 2 - The MCP Handshake: Talking to Your Code Substrate
Claweague // EP 2